chore(ci): force Node.js 24 on snapcore actions#80
Merged
Conversation
GitHub Actions deprecated Node.js 20 actions. From 2026-06-16 the runner will force them to Node.js 24 by default, and the Node.js 20 runtime is removed 2026-09-16. snapcore/action-build and snapcore/action-publish still ship a `node20` runner (upstream migration PR opened 2026-04-05 not merged yet). Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true on the snap job so both pinned actions run under Node.js 24 during the transition. SHAs stay pinned per repository security policy; once snapcore publishes a real Node.js 24 release we bump the SHAs and drop the env var. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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
GitHub Actions emitted a deprecation warning on the most recent
publish.ymlrun:Today is 2026-06-05 — 11 days before the forced default.
Investigation
Looked for newer SHAs of both actions that target Node.js 24:
snapcore/action-build: latest tag is v1.3.0 (2024-07-15), stillusing: 'node20'. PR feat: add Convert tool (PDF to PNG/JPG/DOCX/TXT) #1 (Node.js 24 migration) open since 2026-04-05, not merged.snapcore/action-publish: latest tag is v1.2.0 (2023-10-27), stillusing: 'node20'. PR feat: add Convert tool (PDF to PNG/JPG/DOCX/TXT) #1 open since 2026-04-05, not merged.No SHA bump is possible without downgrading or moving off SHA pinning (against repo security policy).
Fix
Adds
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true'to the snap job, which is the workaround GitHub itself recommends in the deprecation notice. Inline comment marks this as TEMP with a TODO to remove once snapcore publishes a Node.js 24 release.Validation
yaml.safe_load).APP_VERSIONbump.Follow-up
Track:
When they merge and publish a tag (likely v2.x), bump the SHAs and remove the
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24env var.Urgency
Should merge before next
publish.ymlrun (i.e., before next release is published). The v1.13.15 build is currently in progress; ideally this lands first so the v1.13.15 publish run is warning-free.