ci: run publish after Release on merge (workflow_run)#21
Closed
proxymeshai wants to merge 1 commit intomainfrom
Closed
ci: run publish after Release on merge (workflow_run)#21proxymeshai wants to merge 1 commit intomainfrom
proxymeshai wants to merge 1 commit intomainfrom
Conversation
Align with javascript-proxy-headers: add a gate job that runs after the release workflow completes, verify the GitHub release tag exists, then build and publish. Keep release: published for manually created releases. Rename the release workflow to "Release on merge", add concurrency and fork safety, and document the token limitation in the release skill. Made-with: Cursor
Collaborator
Author
|
Superseded: the same changes are on PR #20 (release/0.2.2). |
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.
Chains Publish to PyPI to Release on merge using
workflow_run, matching javascript-proxy-headers (publish.yml+release-on-merge.yml). GitHub does not start new runs fromGITHUB_TOKEN-created releases, so the gate job confirms the release tag then builds frommainand publishes. Therelease: publishedtrigger remains for releases created outside that workflow.Also adds the Release on merge workflow (concurrency, fork check), the release Cursor skill, and workflow-level
id-tokenpermissions.