Repository navigation
chore(release): prepare v2.0.4 - #27
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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.
Release bbackup 2.0.4 with the completed backup and recovery changes, current documentation, and fixes for the certifi and uv certificate trust advisories. The established tested core scope remains unchanged; the new B2, central retention, bounded remote capture, and reviewed Linux/PostgreSQL workflows ship as experimental. Requests #23–#26 remain open pending their remaining qualification.
Validation: 1,242 local tests passed with one skipped; exact wheel and source-archive installation smoke tests passed, along with lint, syntax, generated documentation, version alignment, and publishing checks. Exact default-branch CI and the signed-tag release workflow will produce and verify the published artifacts. No elapsed 30-day retention, aged reclamation, off-host custody, final remote-server, or complete-machine recovery qualification is claimed.