Repository navigation
fix(msgs): prepare 2.1.0 and reject missing release tags - #4
Merged
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
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.
Manual PyPI run 43168818885 failed during checkout because forge-msgs-v2.0.1 did not exist; it never reached package upload. Selecting a tag name in Run workflow does not create one.
Prepare the requested Msgs 2.1.0 family release (forge-msgs-v2.1.0), synchronizing Python/Rust/C++ versions and the two locks. Keep Pillow >=13,<14, the v1 Arrow interface and other package-family versions unchanged. Check that release tags exist and are annotated before checkout, with regression coverage for missing/lightweight/valid tags. Update both README languages and correct the Trusted Publisher owner to PhyAgentOS in the release guide.
Validation:
After CI and review, merge the fix and create an annotated forge-msgs-v2.1.0 tag at that exact merged release commit. No package upload or GitLab synchronization has happened as part of this PR.