Repository navigation
Conversation
…e-Protocol#823) The overview page opened with ~780 lines of deep normative detail (Quantities and units, Request Constraints, Actions) before the reader reached the architectural introduction, because each of those sections was inserted at the top of the file, immediately after "Schema notes": - Actions (Universal-Commerce-Protocol#582) inserted at line 34 - Quantities and units (Universal-Commerce-Protocol#653) inserted at line 34 - Request Constraints (Universal-Commerce-Protocol#655) inserted at line 175 Each insertion was individually reasonable, since these are foundational cross-cutting primitives, but the sequence stacked them ahead of "Discovery, Governance, and Negotiation", which is the actual entry point for a first-time reader. This is visible on /latest but not on /2026-04-08, which predates all three. Move the three sections to sit alongside Policies after "Standard Capabilities", following the precedent set by Universal-Commerce-Protocol#572, which placed the first of these cross-cutting primitives there. This restores the opening reading order of the 2026-04-08 release and groups all four core primitives together. Pure reorder: no prose edits and no heading level changes, verified by comparing the sorted line multiset against the parent commit. All 142 heading anchors are preserved, so the 20+ pages that deep-link into #quantities-and-units, #request-constraints and #actions are unaffected.
…sal-Commerce-Protocol#814) Upgrades js-yaml to 4.3.2 to resolve CVE-2026-84375 (Denial of Service vulnerability in YAML parsing).
amithanda
approved these changes
Sep 18, 2026
jingyli
approved these changes
Sep 18, 2026
damaz91
merged commit Sep 21, 2026
5f377cf
into
Universal-Commerce-Protocol:release/2026-08-25
14 checks passed
This was referenced Oct 11, 2026
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
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.
Description
Backports PR #823 (
d3ccb55c) to therelease/2026-08-25branch.Restores specification overview section order on the
release/2026-08-25release branch. Moves Actions, Quantities and units, and Request Constraints to sit alongside Policies after "Standard Capabilities", ensuring the architectural introduction ("Discovery, Governance, and Negotiation") remains the primary entry point for readers.Pure reorder: no prose edits and no heading level changes. All heading anchors are preserved.
Also includes commit
ee07e9f0(PR #814) to upgradejs-yamlto4.3.2to resolveCVE-2026-84375(Denial of Service in YAML parsing flagged by Trivy in Super-linter).Category (Required)
Please select one or more categories that apply to this change.
ucp-schematool (resolver, linter, validator). (Requires Maintainer approval)Related Issues
Backports #823
Includes #814
Checklist
!for breaking changes).Screenshots / Logs (if applicable)
d3ccb55cwith zero merge conflicts.js-yamlto 4.3.2 resolving Trivy vulnerability CVE-2026-84375 onrelease/2026-08-25.Validate JSON examples (changed docs),cspell,markdownlint,trim trailing whitespace,fix end of files) — all passed.