fix: dispatch Pages after a release tag - #191
Merged
Merged
Conversation
The version bump push carries [skip ci] and is made with GITHUB_TOKEN, so Pages never sees the new plugin.json. Dispatch the existing workflow once the tag exists. Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
Owner
Author
|
Reopening to retrigger Actions; the pull_request event did not start Validate or smoke. |
The open event did not start Validate or smoke. Signed-off-by: TMHSDigital <154358121+TMHSDigital@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
The release bump already writes
.cursor-plugin/plugin.jsonandCHANGELOG.md, which are on the Pages path list. That push never starts Pages: the commit message is[skip ci], and aGITHUB_TOKENpush does not trigger other workflows.workflow_dispatchdoes.After the tag and GitHub release are created,
release.ymlnow runsgh workflow run pages.yml --ref main. Path filters and the[skip ci]bump message are unchanged.inspection-only: the step is the same command that already deployed v0.78.17 by hand. This merge is the live test: the release log must show
Dispatch Pages, then aworkflow_dispatchPages run must succeed, and the landing badge must match the new tag.Test plan
needs-5.1)Dispatch Pagesworkflow_dispatchsucceeds and the live landing badge matches the new tag