CI: promote from release/26.8 → release/26.9 - #139
Merged
jbisaSF merged 1 commit intoAug 20, 2026
Merged
Conversation
jbisaSF
approved these changes
Aug 20, 2026
jbisaSF
deleted the
CI/promote-release-26.8-to-release-26.9-32400278610
branch
August 20, 2026 17:57
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.
Forward-integration PR auto-generated after a push to
release/26.8.Carries the promoted changes, already merged, into
release/26.9:commerce-apps-manifest/manifest.jsonentry/entries (monotonic upsert keyed by app id)catalog.jsononly when promoting a brand-new app (existingapps' catalogs are left to the target branch's catalog CI job)
commerce-apps-manifest/icons/commerce-apps-manifest/translations/*.jsonchanges (additive per-key merge, keyed by app id).github/workflows/**, whichGITHUB_TOKENcannot push), applied as a patch that is skipped rather than forced if itconflicts 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.