fix: simplify release to tag from package.json; bump to 0.2.0#16
Merged
Conversation
….json to 0.2.0 The previous release workflow created version-bump PRs using GITHUB_TOKEN. GitHub blocks workflow triggers on GITHUB_TOKEN-created PRs, so the required Ecosystem drift check never ran, keeping the PR permanently blocked. New approach: developers bump package.json as part of their feature/fix PRs. The release workflow reads the version, checks if the tag exists, and if not tags + creates a GitHub Release. No PR creation, no polling, no race conditions. Also bumps package.json to 0.2.0 so v0.2.0 is cut when this merges. Signed-off-by: fOuttaMyPaint <TMhospitalitystrategies@gmail.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
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.
Redesigns release.yml to avoid the GITHUB_TOKEN PR-creation restriction.
Root cause: GITHUB_TOKEN-created PRs do not trigger GitHub Actions workflows, so the required Ecosystem drift check never ran on the version-bump PR, permanently blocking the merge.
Fix: release.yml now reads version from package.json, checks if the tag exists, and tags + releases if not. No PR creation. Developers bump package.json as part of their feature/fix PRs (same PR that lands the work).
Also includes package.json 0.1.0 -> 0.2.0 bump so v0.2.0 is cut on merge.