chore: declare privacy release line#6
Merged
Conversation
abrichr
marked this pull request as ready for review
July 15, 2026 22:09
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.
Summary
openadapt-privacyExperimental and distinguish API versioning from clinical validationContext
The security-fixed release is publicly available as
1.0.0. Python Semantic Release 10 defaultsallow_zero_versionto false, so the previousmajor_on_zero=falseassertion did not preserve a 0.x line. Public package history is retained rather than deleting or rewriting tags.Verification
2 passedintests/test_release_config.pyallow_zero_version=falseandmajor_on_zero=truegit diff --checkpassesThis PR must be squash-merged with its
chore:title so it does not create a package release.