Add release strategy, pinning, and tag-based publishing#10
Merged
Conversation
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
1 participant
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
RELEASING.mdwith SemVer/tag-based release processCHANGELOG.mdscaffold withUnreleasedsectionrelease.ymlworkflow to test, verify tag/version parity, build, publish to PyPI, and create GitHub release onv*tagsmainin addition to PRsWhy
Today users track
mainand cannot reliably pin to known-good versions. This introduces a proper release channel and operational guardrails.Ops follow-ups (outside code)
main(require PR + status checks)Validation
uv run ruff check braintrust_migrate/cli.pyuv run pytest tests/unit/test_cli_dry_run.py -q