Update wisp to v0.5.0 (crash-safe storage)#4
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
WalkthroughBumps the wisp dependency from v0.4.0 to v0.5.0 by updating the Dockerfile build arguments (version tag and pinned commit hash) and the StartOS version constant with new release notes. Documentation in ChangesWisp v0.5.0 Upgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Bumps the packaged wisp to v0.5.0 and refreshes the docs.
Changes
WISP_VERSIONv0.4.0 -> v0.5.0,WISP_COMMIT->fa14e1f259406b6e3560ba2ddca48645098b9525(the commit v0.5.0 points to; the build guard fails if the tag is ever re-pointed).0.4.0:0->0.5.0:0with release notes describing the v0.5.0 change (crash-safe storage by default via a group-commit writer; durability stays configurable).masterbranch (wisp's default ismain).[1,2,9,11,13,16,33,40,42,45,50,65,70,77,86](no 22).metadurability (crash-safe, no corruption), which is the right default for an always-on home server.What v0.5.0 brings
wisp now defaults to durable storage: a crash or power loss can at most roll back the last transaction instead of corrupting the database. Writes are group-committed so durability scales with load.
Validation
Built
wisp_x86_64.s9pk(v0.5.0:0, 29M); the Dockerfile commit guard confirms the image is exactly wisp v0.5.0. Separately drove wisp v0.5.0 as a real client (spider pulled 7,800+ events from live relays into the local relay, plus direct publish/query and NIP-11), all working.Summary by CodeRabbit
Chores
Improvements
Documentation