Level master with develop (CI green) - #2
Merged
Merged
Conversation
The ratchet re-runs the unit suite, so without the siblings the tests that read xchain-documentation skip and measured coverage lands under a floor that was set with them running. The job had never actually run: it needs the gate, and the gate was red for the missing sibling this same roster now supplies.
Both overrides sat one patch short of the fix: js-yaml 4.3.0 carries the quadratic !!omap CPU consumption advisory and brace-expansion 5.0.8 the unbounded-array DoS.
The contributor agreement says the template carries an agreement checkbox; no template existed in any repo, so the sentence described something that was not there.
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.
Levels master with develop, which is green on every job.
Master had fallen behind after the 0.9.0 cut, so its gate was reporting an old
state rather than a real problem. This carries the current work across.
Opened alongside the other levelling PRs and merged with them: several of these
repos share byte-identical twin files, and advancing one half of a pair on its
own is what makes the other half's gate report drift.