Skip to content

Bump GitHub Action versions to drop Node.js 20#201

Merged
lesnik512 merged 1 commit into
mainfrom
bump-action-versions
Jun 9, 2026
Merged

Bump GitHub Action versions to drop Node.js 20#201
lesnik512 merged 1 commit into
mainfrom
bump-action-versions

Conversation

@lesnik512

Copy link
Copy Markdown
Member

Summary

Bumps the three actions used across _checks.yml, scheduled.yml, docs.yml, and publish.yml to versions that run on Node.js 24:

  • actions/checkout@v4@v6
  • extractions/setup-just@v2@v4
  • astral-sh/setup-uv@v3@v8.2.0 (pinned; see note below)

GitHub removes Node.js 20 from runners on 2026-09-16 and emits deprecation warnings until then. Every CI run on main currently logs the warning.

Why setup-uv is pinned to a minor instead of @v8

From v8.0.0 onward astral-sh stopped publishing major and minor tags (release notes) — citing supply-chain hardening after the tj-actions incident. @v8 would no longer resolve. Verified that the two inputs we use (enable-cache, cache-dependency-glob) still exist in v8.2.0 with compatible semantics.

Test plan

  • YAML parses cleanly across all four files.
  • ci.yml runs green on this PR (proves _checks.yml still works with bumped pins).
  • After merge, the next scheduled-dep-check dispatch (or the Monday cron) runs without Node.js deprecation annotations.

GitHub's runner deprecation timeline removes Node.js 20 from runners
on 2026-09-16; the prior pins emitted deprecation warnings on every
run. Bumps:

- actions/checkout@v4 -> @v6
- extractions/setup-just@v2 -> @v4
- astral-sh/setup-uv@v3 -> @v8.2.0

setup-uv is pinned to a specific minor rather than @v8 because the
maintainers stopped publishing major/minor tags from v8.0.0 onward
for supply-chain reasons (see the v8.0.0 release notes). The two
inputs we use (enable-cache, cache-dependency-glob) still exist in
v8 with compatible semantics.
@lesnik512 lesnik512 merged commit eaa7c25 into main Jun 9, 2026
6 checks passed
@lesnik512 lesnik512 deleted the bump-action-versions branch June 9, 2026 05:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant