Skip to content

chore: backport #823 to release/2026-08-25 - #838

Merged
damaz91 merged 2 commits into
Universal-Commerce-Protocol:release/2026-08-25from
damaz91:chore/backport-overview-order-2026-08-25
Sep 21, 2026
Merged

damaz91 merged 2 commits into
Universal-Commerce-Protocol:release/2026-08-25from
damaz91:chore/backport-overview-order-2026-08-25

Conversation

@damaz91

@damaz91 damaz91 commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

Description

Backports PR #823 (d3ccb55c) to the release/2026-08-25 branch.

Restores specification overview section order on the release/2026-08-25 release 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 upgrade js-yaml to 4.3.2 to resolve CVE-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.

  • Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
  • Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
  • Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
  • Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
  • Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
  • Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
  • SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
  • Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
  • UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
  • Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Related Issues

Backports #823
Includes #814

Checklist

  • I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
  • I have updated the documentation (if applicable).
  • My changes pass all local linting and formatting checks.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • (For Core/Capability) I have included/updated the relevant JSON schemas.
  • I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

Screenshots / Logs (if applicable)

  • Clean cherry-pick of d3ccb55c with zero merge conflicts.
  • Upgraded js-yaml to 4.3.2 resolving Trivy vulnerability CVE-2026-84375 on release/2026-08-25.
  • Ran all pre-commit hooks locally (Validate JSON examples (changed docs), cspell, markdownlint, trim trailing whitespace, fix end of files) — all passed.

…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).
@damaz91
damaz91 merged commit 5f377cf into Universal-Commerce-Protocol:release/2026-08-25 Sep 21, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants