You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* ci: bump artifact and QEMU actions to Node 24 versions
GitHub Actions annotations flagged actions/upload-artifact,
actions/download-artifact, and docker/setup-qemu-action as running on
the deprecated Node.js 20 runtime. Node 20 is forced off by default on
2026-06-16 and removed from runners on 2026-09-16.
Bump to the Node 24 releases (SHA-pinned):
- actions/upload-artifact v4.6.2 -> v7.0.1
- actions/download-artifact v4.3.0 -> v8.0.1
- docker/setup-qemu-action v3.7.0 -> v4.1.0
All artifact steps use upload/download by name (not artifact-ids), so
the v5 single-artifact-by-ID path change does not apply. Downloads are
single zipped artifacts, compatible with v8 hash-mismatch and
direct-download defaults.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* ci: bump remaining pinned actions to latest releases
Update the rest of the SHA-pinned actions to their latest releases so
the whole workflow fleet runs on the Node 24 runtime and current
action code.
- actions/checkout v6.0.1/v6.0.2 -> v6.0.3
- actions/setup-python 6.1.0 -> v6.2.0
- crate-ci/typos v1.42.1 -> v1.47.2
- docker/setup-buildx-action v3.12.0 -> v4.1.0
- pypa/gh-action-pypi-publish v1.13.0 -> v1.14.0
- softprops/action-gh-release v2.5.0 -> v3.0.0
- cloudsmith-io/cloudsmith-cli-action v2.0.1 -> v2.0.3
- zizmorcore/zizmor-action v0.3.0 -> v0.5.6
action-gh-release v3 and the artifact actions are Node 24 runtime bumps
with no behavior change for this usage. zizmor-action v0.4/v0.5 only add
opt-in options; defaults are unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* ci: replace action-gh-release with gh CLI release step
zizmor flagged softprops/action-gh-release as redundant: the gh CLI is
preinstalled on GitHub-hosted runners, so a third-party action is not
needed to create the release. Replacing it with a gh release create
script step removes a supply-chain dependency.
Behavior is unchanged: the release is created on the v* tag that
triggered the run (GITHUB_REF_NAME, matching the action's default
tag_name), titled "Release v$VERSION", with the zipapp uploaded as an
asset and empty release notes.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments