Repository navigation
release(3.2.3): parity release, lockstep with the engines at 4.3.3 - #41
Merged
Merged
Conversation
github-actions
Bot
added
documentation
github-actions
Bot
added
the
area: core
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.
Delivers issue: #40
Closes #40
Description
Also: with the guard-core feature, GuardAgent::new fills guard_core_version from guard_core_rs::VERSION when unset; the optional guard-core-rs requirement moves to 4.3.3.
Version bump only (Cargo.toml, Cargo.lock, README, CHANGELOG): a parity release with no functional change.
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?
cargo fmt --check clean, cargo clippy --all-targets --all-features -D warnings clean, cargo test --all-features all pass.
Checklist: