chore: bump version to 0.3.1 - #69
Merged
Merged
Conversation
A patch bump. The only change since v0.3.0 is the alert-email fix (#68), which stops the daemon mailing RESOLVED after every successful reconcile and names the undelivered notification in send-failure logs. Patch rather than minor because nothing an operator configures or scripts against moves: no new or renamed config keys, no relocated paths, no new exit codes, and the alert flag file behaves exactly as before. What changes is email volume, and only in the direction of the bug being fixed -- RESOLVED now arrives once per recovery instead of once per cycle. ALERT is untouched and still fires on every failed sync. Updated in every place the project version appears: pyproject.toml project.version uv.lock regenerated by uv lock docs/conf.py release deploy/rpi-image-gen/config/door-sync-ab.yaml artefact.version plus the copy-pasteable command lines in the packaging and image READMEs, and VERSION in the docs/usage.rst install snippet. The three remaining 0.2.0 references stay put, for the reasons given in the 0.3.0 bump: two are historical partition measurements that would become false if bumped, and X-Env-Layer-Version versions the layer definition rather than the payload it carries. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
|
Warning Review limit reachedNext included review available in 53 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
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 |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No unresolved review issues were identified.
Pull request overview
Updates project and deployment metadata for the 0.3.1 patch release.
Changes:
- Bumps package and lockfile versions.
- Updates documentation and build examples.
- Aligns the appliance artifact version.
File summaries
| File | Summary |
|---|---|
uv.lock |
Synchronizes locked package metadata. |
pyproject.toml |
Updates project version. |
packaging/deb/README.md |
Updates Debian build example. |
docs/usage.rst |
Updates installation version. |
docs/conf.py |
Updates documentation release version. |
deploy/rpi-image-gen/README.md |
Updates appliance build example. |
deploy/rpi-image-gen/config/door-sync-ab.yaml |
Updates appliance artifact version and build example. |
Review details
- Files reviewed: 6/7 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Patch release covering the alert-email fix from #68.
Why patch, not minor
Nothing an operator configures or scripts against moves: no new or renamed config keys, no relocated paths, no new exit codes, and the alert flag file behaves exactly as before. The only observable change is email volume, and only in the direction of the bug being fixed —
RESOLVEDnow arrives once per recovery instead of once per successful cycle.ALERTis untouched and still fires on every failed sync.That makes this a safe drop-in upgrade, which is what a patch bump promises. (Contrast v0.3.0, which was minor because the alert flag moved to
/var/libandvalidate-configgained a new way to exit 1.)Changed
pyproject.tomlproject.versionuv.lockuv lockdocs/conf.pyreleasedeploy/rpi-image-gen/config/door-sync-ab.yamlartefact.version+ the build example in the header commentdeploy/rpi-image-gen/README.md,packaging/deb/README.mddocs/usage.rstVERSION=in the install snippetNo
0.3.0references remain outsidedocs/_build.Deliberately left alone
The three
0.2.0references stay, for the reasons given in the 0.3.0 bump:deploy/rpi-image-gen/README.mdanddoor-sync-ab.yamlcite partition measurements taken from the v0.2.0 build — bumping them would make the numbers false.X-Env-Layer-Versioninlayer/door-sync.yamlversions the layer definition, not the payload it carries.Testing
uv run pytest— 421 passed.uv run ruff check .,uv run ruff format --check ., anduv run pyrefly checkare clean.🤖 Generated with Claude Code