Repository navigation
release(3.2.3): version reporting fix, lockstep with the engines at 4.3.3 - #75
Merged
Merged
Conversation
… tamper is never a no-op
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.
Delivers issue: #74
Closes #74
Description
Also: release.yml fails before publishing unless the release tag, pyproject.toml and guard_agent/_version.py versions agree.
Bumps every version location (pyproject.toml, guard_agent/_version.py, .mike.yml, docs/versions/versions.json, CHANGELOG, release notes) via bump_version.py. tests/test_version_consistency.py already asserts pyproject and _version agree.
Motivation and Context
Lockstep patch release 3.2.3 across the Guard-Core families (cores 4.3.3, agents 3.2.3).
Type of change
How Has This Been Tested?
make local-test: 529 passed, 2 skipped; ruff, ruff format, mypy clean.
Checklist: