Repository navigation
ci: keep every pending release in the queue - #64
Merged
Merged
Conversation
Pin the shared npm release workflow to putdotio/.github v2.0.0, whose release job uses queue: max, so a late older release no longer replaces a newer pending one and then skips. Inputs, secrets and permissions are unchanged from aebc5c2. The links and scan actions move to the same tag; on Linux the only change is Zizmor 1.29.0 to 1.30.1.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Contributor
|
🎉 This PR is included in version 3.0.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
A late release run no longer replaces a newer one waiting in the release group, so a releasable push to
maincan't sit unreleased until the next push. The shared npm release workflow fixed this in v2.0.0 withqueue: max; everyputdotio/.githubpin here moves to that tag.putdotio/.githubpinfrontend-release-npm.ymlaebc5c2v2.0.0queue: max; inputs, secrets and permissions unchangedactions/scanv1.2.0v2.0.0actions/linksv1.2.0v2.0.0ci:commit releases nothing, so merging publishes no version.Written by an agent (Claude Code, Claude Opus 5.5)