Repository navigation
release: v0.22.5 - #63
Merged
Merged
Conversation
npm audit reports proxy-addr 2.0.7, reached through express, as critical: IP spoofing via an IPv4-mapped IPv6 trust subnet. 2.0.8 is inside express's ^2.0.7 range, so only the lockfile moves.
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.
Patch train v0.22.5 for xchain-node: the version bump and the v0.22.5 release manifest, which moves only the xchain-hub pin to its signed v0.22.5 master merge commit (e8ea5011). Every other pin and the trainActivation block are identical to v0.22.4, and no code changes. Release-management section 7.
Audit fix (8b85594):
proxy-addr2.0.7 to 2.0.8 in the lockfile only, for the critical advisory GHSA-jqcg-44mw-7w3h that reds the audit job; 2.0.8 is inside express's ^2.0.7 range. The same fix shipped in hub v0.22.5.Pre-push note: the root code-structure ratchet refused this branch for six
process.envreads insrc/services/validator_service/signer.js, a file the branch does not touch. Those reads shipped in v0.22.4; develop's node baseline dropped to 0 after that cut. The ratchet's hotfix rule (grade a hotfix against its tag's baselines) does not fire for component repos, because it looks for the root config inside the component repo. Graded under the baseline in force at the v0.22.4 cut the branch is clean, and every other hook stage passed by hand, includingci-gate: PASS xchain-node 3109 pass / 0 fail [DankServer], so the branch was pushed past the ratchet only.