Repository navigation
ci: create a release in each output repo after syncing - #46
Draft
steve-calvert-glean wants to merge 1 commit into
Draft
steve-calvert-glean wants to merge 1 commit into
steve-calvert-glean wants to merge 1 commit into
Conversation
The publish workflow updated claude-plugins, cursor-plugins and codex-plugins but never created a GitHub Release in them, so their Releases pages stopped at the last release someone made by hand (v3.5.0). After the sync PR merges, tag the merged commit in the output repo and create a release with the same version and notes as the source release. Skip a tag that already has a release, so re-running a sync is safe, and mark it latest only when it is the source repo's latest release.
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
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.
Problem
Releasing from this repo updates
claude-plugins,cursor-pluginsandcodex-plugins, but it never creates a GitHub Release in them. Their Releases pages show only the releases someone made by hand. After v3.6.1 shipped,claude-pluginsandcursor-pluginsstill listed v3.5.0 as the latest release, andcodex-pluginshad none.Users weren't affected. All three marketplaces install from the plugin repo's default branch, which had 3.6.1.
Change
publish.ymlgets a "Release " step after "Merge sync PR". In sync mode on av*tag, it:gleanwork/agent-pluginsvX.Y.Z" link.Release X.Y.Zon that commit in the output repo.If the output repo already has a release for the tag, the step does nothing, so re-running a release's sync is safe. It marks the release latest only when the tag is this repo's latest release, so re-running an older tag doesn't take the latest label from a newer release.
If the merge step fails, the job stops before this step.
RELEASE.mdnow says to merge the PR by hand and then re-run the release's sync, which creates the release.Testing
create-github-app-tokenstep, which come from actionlint's outdated metadata for that action; the step works in CI.gh release createreplaced byecho:--latest=false.The first release after this merges is the first end-to-end run.