Skip to content

docs: update fulfillment extension fields to target checkout#592

Open
damaz91 wants to merge 1 commit into
Universal-Commerce-Protocol:mainfrom
damaz91:fix-fulfillment-extension-fields
Open

docs: update fulfillment extension fields to target checkout#592
damaz91 wants to merge 1 commit into
Universal-Commerce-Protocol:mainfrom
damaz91:fix-fulfillment-extension-fields

Conversation

@damaz91

@damaz91 damaz91 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Description

Originated from #588

Update the extension_fields macro call in fulfillment.md to use 'checkout' as the second argument (spec file name) instead of 'fulfillment'. This ensures that references in the rendered properties table correctly target the checkout specification context where these extension fields are applied.

Category (Required)

  • 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

None.

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.

@damaz91 damaz91 added bug Something isn't working documentation Improvements or additions to documentation labels Jul 16, 2026
@damaz91
damaz91 force-pushed the fix-fulfillment-extension-fields branch from ca3499d to f84a2ca Compare July 16, 2026 10:41
@damaz91
damaz91 force-pushed the fix-fulfillment-extension-fields branch from f84a2ca to 2aac18c Compare July 16, 2026 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants