ci: rebuild release-creator without a third-party action#1379
Conversation
changesets/action has been silently failing (startup_failure) since 2026-07-15 - it's a third-party GitHub Action, blocked by this org's Actions allowlist (allowed_actions: "selected", GitHub-owned only). This meant no "Version Packages" PR could be opened for any pending changeset since then - one shipped by hand as a one-off (see #1378) to unblock a pending security fix while this was rebuilt properly. Replaces the action with plain run: steps + the gh CLI, replicating its core behavior: detect pending changesets (any .changeset/*.md besides README.md), reset the changeset-release/master branch to current master, run the existing yarn update-versions-and-changelogs script, commit as "Version Packages", force-push, and create the PR if one isn't already open (or close it if no changesets remain, e.g. after a manual release). No third-party `uses:` action anywhere in the file.
|
✅ TVS Validation PassedShow detailsAll validation checks have successfully completed. |
Codecov Report✅ All modified and coverable lines are covered by tests. Please upload reports for the commit 50e4870 to get more accurate results. Additional details and impacted files@@ Coverage Diff @@
## master #1379 +/- ##
=======================================
Coverage 91.59% 91.59%
=======================================
Files 127 127
Lines 4142 4142
Branches 1033 1033
=======================================
Hits 3794 3794
Misses 348 348
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Adds workflow_dispatch so the release PR can be created/refreshed on demand instead of only on a push touching .changeset/** or packages/** - useful for re-checking pending changesets without waiting for a matching push, and for validating the workflow itself.
Summary
release-creator.yml(opens the "Version Packages" PR whenever changesets are pending) has been failing withstartup_failuresince 2026-07-15 -changesets/actionis a third-party GitHub Action, blocked by this org's Actions allowlist (allowed_actions: "selected", GitHub-owned only - same root cause as thecodecov/codecov-actionfix in #1377).This went unnoticed because the workflow doesn't block anything directly - it just silently never opened a PR. There was a real pending changeset (the js-cookie security fix) stuck with no way to ship; that shipped by hand as a one-off PR (#1378) to unblock it while this fix was built properly.
What changed
Replaced the action with plain
run:steps + theghCLI:.changeset/*.mdbesidesREADME.md)changeset-release/masterbranch to currentmaster, run the existingyarn update-versions-and-changelogsscript (unchanged - this is the same command the action was already calling), commit as"Version Packages", force-pushNo third-party
uses:action anywhere in the file - onlyactions/checkoutandactions/setup-node(both GitHub-owned).Test plan
yarn scripts lintpasses