ci: bump actions/github-script v7 → v9 (fix release auto-publish)#36
Merged
Conversation
Every release run since 1.16.0 (2026-04-28) has failed with: An action could not be found at the URI 'https://codeload.github.com/actions/github-script/tar.gz/<sha>' actions/github-script latest is v9.0.0 (published 2026-04-09); GHA's resolution of @v7 has been intermittently broken for our workflow since around then. Our usage (core.info / core.setFailed / core.setOutput, github.paginate, github.rest.repos.listTags) is backwards-compatible across v7 / v8 / v9, so the bump is safe. The first PR to merge after this lands will trigger the (now-working) release workflow and produce v1.17.0 with auto-generated notes covering every PR since 1.16.0: - Ed25519 op-envelope signing (KLA-411) - Touch ID step-up (KLA-412) - Self-describing step-up errors (KLA-417) - device_view MCP App (KLA-404) - compliance_view MCP App (KLA-405) - recipe_runner_view + recipe_run execute path (KLA-406) - Webhook out-of-band approval (KLA-413, closes KLA-408 trilogy) - Recipe edit via $EDITOR (KLA-399) - CI label-check workflow Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
jrennichjc
approved these changes
May 26, 2026
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
3 participants
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.
Summary
Every release run since
1.16.0(2026-04-28) has failed with:actions/github-scriptlatest is v9.0.0 (published 2026-04-09); GHA's resolution of@v7has been intermittently broken for our workflow since around then. Our usage (core.info/core.setFailed/core.setOutput,github.paginate,github.rest.repos.listTags) is backwards-compatible across v7 → v9, so the bump is safe.What ships after this merges
This PR is labeled
minorso the (now-working) release workflow producesv1.17.0with auto-generated notes covering every PR merged since1.16.0:\$EDITORTest plan
actions/github-script@v9exists and is the current latestscript:blocks only usecore.*,github.paginate, andgithub.rest.repos.listTags— all backwards-compatiblev1.17.0🤖 Generated with Claude Code
Note
Low Risk
CI-only dependency pin change with no application or auth logic touched; release behavior should match prior scripts.
Overview
Updates the release workflow so both inline
actions/github-scriptsteps (PR label parsing and semver bump) use@v9instead of@v7, addressing failed release runs where GitHub Actions could not resolve the older action tarball. The embeddedscript:logic is unchanged—same label rules,core.*outputs, tag pagination, andsemverbump behavior.After merge, the existing label-driven release path should be able to publish again (e.g.
v1.17.0for aminorPR).Reviewed by Cursor Bugbot for commit 9be338c. Bugbot is set up for automated code reviews on this repo. Configure here.