chore(release): forward-merge 3.1.15 into main - #6640
Merged
Conversation
) * docs(request-signing): drop stale conformance vector counts The Testing section said the spec ships 39 test vectors (12 positive + 27 negative). The set is 40 — 12 positive + 28 negative — since vector 028-unsigned-protocol-method-required was added in 3.1.0. Refer to the positive/ and negative/ directories instead of stating counts, matching universal/signed-requests.yaml, whose pass_criteria deliberately grades "all vectors in positive/ ... and all vectors in negative/" rather than a total, and so cannot drift as vectors are added. Refs #6071 * fix(compliance): drop stale vector count from signed-requests-runner header The header said the storyboard grades a verifier against 28 conformance vectors. The set is 40 - 12 positive + 28 negative. 28 is the size of negative/ alone, so the count omitted the positive set entirely. It was never accurate: at 3.0.x the set was 39 (12 + 27), matching neither the total nor the negative count. Vector 028-unsigned-protocol-method-required landed in 3.1.0, which is what made 28 coincide with len(negative/). Refer to the positive/ and negative/ directories instead of a count, matching universal/signed-requests.yaml, whose pass_criteria grades "all vectors in positive/ ... and all vectors in negative/" and therefore cannot drift. Refs #6071 * chore: add changeset for request-signing vector count fixes --------- Co-authored-by: Constantine Mirin <konstantin.mirin@gmail.com> Co-authored-by: Constantine.mirin <konstantin.mirin@postindustria.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Backport the canonical rate-limit exhaustion not-applicable grading contract and regression coverage to the 3.1 maintenance line while preserving the branch-specific reason enum.
Publish the 3.1.x rate-limit exhaustion clarification and immutable release artifacts.
![aao-secretariat[bot]](https://avatars.githubusercontent.com/u/221690821?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Ladon verdict: Approve
Approve — clean forward-merge of released 3.1.15 into main.
What I checked:
- Released-artifact immutability: The 1053 high-risk hits are all
(added)new files underdist/compliance/3.1.15/**,dist/schemas/3.1.15/**, anddist/protocol/3.1.15.*— brand-new append-only release records for a version that did not previously exist. No modification/deletion of any file inside an existing semver artifact. The only(modified)files aredist/schemas/index.jsonanddist/schemas/latest.json, which are mutable discovery pointers (latestis explicitly mutable dev output); reviewer confirms they advance 3.1.14 → 3.1.15 with 3.2.0-beta.0 preserved. Nothingcritical. - Source/schema surface: No edits to
static/schemas/source/**, so schema↔docs coherence, oneOf discriminator audit, and 3.1.x patch-eligibility gates do not apply. Nopackage.jsonversion hand-edit. - Changeset scope: Chronological 3.1.15 CHANGELOG entry present; no untracked wire change.
- Breaking-class hard gate: This is a release-artifact publish, not a protocol policy/wire-shape decision — no Breaking-class change to ratify.
Gate posture: gated_paths is false, so row 2 does not fire despite review_decision: REVIEW_REQUIRED. high_risk is true but every reason is (added) (new-file scaffolding — not escalation-worthy per the high-risk-flag reading) except two mutable-pointer modifications with no medium-or-higher finding. No author team gate. Reviewer surfaced zero findings.
Rows 1–8 do not fire; falls through to row 9 → approve.
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.
Summary
main3.2.0-beta.0remains listed whilelatest_stable,v3, andv3.1point to 3.1.15Root cause
The automated 3.1.x → main merge failed on genuine content conflicts after the 3.1.15 release. That stranded stable artifacts and left
/schemas/index.jsonreporting 3.1.14 even though the stable aliases already served 3.1.15.Conflict decisions
Validation
npm run test:dist-schema-version-idsnpm run test:storyboard-test-kitsnode --test --test-force-exit --test-timeout=30000 tests/sdk-runner-capability-gates.test.cjsnode --test --test-force-exit --test-timeout=30000 tests/lint-universal-storyboard-doc-parity.test.cjsgit diff --check