Skip to content

ci: bump actions to node24-ready majors ahead of forced migration - #200

Merged
doughknee merged 1 commit into
mainfrom
ci/node24-actions-bump
Jun 10, 2026
Merged

doughknee merged 1 commit into
mainfrom
ci/node24-actions-bump

Conversation

@doughknee

Copy link
Copy Markdown
Owner

Summary

  • Bump actions/checkout v4 → v6, actions/setup-node v4 → v6, actions/setup-go v5 → v6, and dorny/paths-filter v3 → v4 across backend-tests.yml, frontend-tests.yml, and deploy.yml
  • GitHub retires the node20 action runtime on June 16, 2026; these majors run on node24
  • desktop-release.yml was already on checkout@v6/setup-node@v6; auto-close-osticket.yml uses no marketplace actions
  • paths-filter v4.0.0 is a pure node24 runtime bump (feat: update action runtime to node24 dorny/paths-filter#294) — no API/output changes, so the deploy change-detection job is unaffected
  • digitalocean/action-doctl@v2, Swatinem/rust-cache@v2, tauri-apps/tauri-action@v0 are major-pinned at their current latest majors and need no change

Test plan

  • backend-tests and frontend-tests workflows pass on this PR
  • After merge, confirm the next deploy run's changes job (paths-filter v4) produces the same service-selection outputs

🤖 Generated with Claude Code

checkout v4->v6, setup-node v4->v6, setup-go v5->v6, paths-filter
v3->v4 across backend-tests, frontend-tests, and deploy workflows.
desktop-release was already on v6; auto-close-osticket uses no
marketplace actions. paths-filter v4 is a pure node24 runtime bump
with no API changes. doctl, rust-cache, and tauri-action stay on
their current latest majors.

GitHub retires the node20 runtime on June 16, 2026.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@doughknee
doughknee merged commit d9c0e62 into main Jun 10, 2026
@doughknee
doughknee deleted the ci/node24-actions-bump branch June 10, 2026 18:15
doughknee added a commit that referenced this pull request Jun 10, 2026
…205)

setup-go@v6 (bumped in #200) defaults GOTOOLCHAIN=local, which turned
the stale go-version: "1.21" pin into a hard failure across all five
Go jobs ("go.mod requires go >= 1.25.0") — v5 silently auto-downloaded
the right toolchain. Switch to go-version-file pointed at each
module''s go.mod so the pin can never drift again, and fix
cache-dependency-path to the module root (api/core/go.sum never
existed; the cache restore had been warning about it).

The breakage shipped unnoticed because workflow-only changes don''t
trigger this workflow; add it to its own path filters.

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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