Repository navigation
release(3.2.4): lockstep agents at 3.2.4 on guard-core-rs 4.4.0 - #62
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.
Delivers issue: #61
Closes #61
Description
The 3.2.4 version string already landed in #56. This completes the release: the 3.2.4 CHANGELOG section now covers the Python parity fixes merged after it (#58, #60), and the optional
guard-core-rsrequirement moves from 4.3.3 to 4.4.0 with the Cargo.lock entries, the same way the 3.2.3 train moved it to 4.3.3.The CI jobs check out guard-core-rs master as the path dependency, so they stay red until the guard-core-rs 4.4.0 release PR (Guard-Core/guard-core-rs#151) is merged. I verified locally against that branch.
Motivation and Context
Lockstep release of the agents at 3.2.4 next to the 4.4.0 engines. Publishing waits for guard-core-rs 4.4.0 on crates.io.
Type of change
How Has This Been Tested
Local gate against the guard-core-rs 4.4.0 release branch, then CI after the engine PR merges.
Checklist: