Skip to content

CI: promote from release/26.8 → release/26.9 - #126

Closed
github-actions[bot] wants to merge 1 commit into
release/26.9from
CI/promote-release-26.8-to-release-26.9-32173609725
Closed

github-actions[bot] wants to merge 1 commit into
release/26.9from
CI/promote-release-26.8-to-release-26.9-32173609725

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Forward-integration PR auto-generated after a push to release/26.8.

Carries the promoted changes, already merged, into release/26.9:

  • Any app ZIP(s)
  • The matching commerce-apps-manifest/manifest.json entry/entries (monotonic upsert keyed by app id)
  • The merged catalog.json (union versions, monotonic latest)
  • Any app icons under commerce-apps-manifest/icons/
  • Any commerce-apps-manifest/translations/*.json changes (additive per-key merge, keyed by app id)
  • Any other non-CAP file changes (docs, skills, etc. - excluding .github/workflows/**, which
    GITHUB_TOKEN cannot push), applied as a patch that is skipped rather than forced if it
    conflicts with intentional per-branch divergence

Merging this PR re-triggers the catalog workflow on release/26.9,
which promotes forward to the next branch in the chain. Tags are immutable and shared,
so version-pinned installs stay stable across branches.

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.

1 participant