Repository navigation
release(3.2.1): the family lockstep artifact - #17
Merged
Merged
Conversation
Empty lockstep release for the Guard agent family 3.2.1 wave: no shipped change, src/ has a zero diff since 3.2.0 apart from the version constant. The tag keeps the family version-aligned while guard-agent-ts 3.2.1 ships the wave's only runtime fix (the js/polynomial-redos endpoint normalization hardening). Version::VERSION reports 3.2.1; composer.json carries no version field, Packagist derives it from the tag.
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: #
Description
Release train 3.2.1 for the Guard agent family wave: an empty lockstep release. Version bump to 3.2.1 and a changelog section in the baseline release-notes format.
No shipped change:
src/has a zero diff since 3.2.0 apart from the version constant. The tag keeps the family version-aligned while guard-agent-ts 3.2.1 ships the wave's only runtime fix (the js/polynomial-redos endpoint normalization hardening).The reported agent version moves to 3.2.1 (
RenzoFranceschini\GuardAgent\Version::VERSION); composer.json carries no version field, Packagist derives it from the tag. Still no composer dependency on guard-core-php, so no engine floor applies.Release mechanics (matching v3.2.0)
php -l src/Version.php,make test-unit(614 passed, 0 failed).v3.2.1on main, push tag, verify the GitHub tag and Packagist.