feat(workflows): notify homepage repo on stable superdoc release#3216
Merged
Conversation
Mirrors the promote-stable-docs.yml pattern: workflow_run on Release superdoc, gated on success + stable, with a tag-diff against the triggering head_sha to filter out semantic-release no-ops. Sends repository_dispatch to superdoc-dev/homepage so a receiver workflow there can open one bump PR per release. Kept out of release-superdoc.yml on purpose: that job sits in the release-stable concurrency group, and a homepage/token failure should not mark a successful npm publish as failed.
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.
Fires a
repository_dispatchtosuperdoc-dev/homepagewhenever a stable SuperDoc release lands, so the homepage'ssuperdocdependency can be auto-bumped via a single PR.promote-stable-docs.yml:workflow_runon📦 Release superdoc, gated onsuccess+head_branch == 'stable', with acomm -23tag-diff against the triggeringhead_shato filter out semantic-release no-ops.package,version,tag, plus the upstream release run id and this notify run id, so the receiver workflow can link back.release-superdoc.ymldeliberately — that job sits in therelease-stableconcurrency group, and a homepage/token failure must not mark a successful npm publish as failed.Receiver workflow lives in superdoc-dev/homepage (separate PR). Requires the existing GitHub App to be installed on
superdoc-dev/homepagewithcontents: write(for the dispatch endpoint and branch push) andpull-requests: write(for the PR open/update).