chore: force GitHub actions to Node 24 runtime to silence deprecations#85
chore: force GitHub actions to Node 24 runtime to silence deprecations#85neverinfamous merged 1 commit intomainfrom
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
do-manager | a9cc352 | Apr 06 2026, 01:21 PM |
There was a problem hiding this comment.
Pull request overview
This PR updates GitHub Actions workflows to force JavaScript-based actions to run under a Node 24 runtime in order to suppress runtime deprecation warnings during CI.
Changes:
- Add
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=trueat the workflow level for multiple workflows. - Update
actions/checkoutin the auto-release workflow to use@v4.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
.github/workflows/secrets-scanning.yml |
Adds workflow-level env forcing Node 24 for JS actions. |
.github/workflows/docker-publish.yml |
Adds workflow-level env forcing Node 24 for JS actions. |
.github/workflows/auto-release.yml |
Adds workflow-level env forcing Node 24 and updates checkout action version. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| env: | ||
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true | ||
|
|
There was a problem hiding this comment.
env values in GitHub Actions are treated as strings; using an unquoted YAML boolean here can be ambiguous/inconsistent with other env entries. Consider quoting the value (e.g., "true") and adding a short comment/link explaining why forcing Node 24 is needed, since this setting applies to all JavaScript-based actions in the workflow and could affect third-party actions unexpectedly.
| env: | ||
| REGISTRY: docker.io | ||
| IMAGE_NAME: writenotenow/do-manager | ||
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true |
There was a problem hiding this comment.
env values in GitHub Actions are treated as strings; using an unquoted YAML boolean here can be ambiguous/inconsistent with other env entries. Consider quoting the value (e.g., "true") and adding a short comment/link explaining why forcing Node 24 is needed, since this setting applies to all JavaScript-based actions in the workflow and could affect third-party actions unexpectedly.
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true | |
| # Force JavaScript-based GitHub Actions in this workflow to run on Node 24. | |
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true" |
| branches: [main] | ||
|
|
||
| env: | ||
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true |
There was a problem hiding this comment.
env values in GitHub Actions are treated as strings; using an unquoted YAML boolean here can be ambiguous/inconsistent with other env entries. Consider quoting the value (e.g., "true") and adding a short comment/link explaining why forcing Node 24 is needed, since this setting applies to all JavaScript-based actions in the workflow and could affect third-party actions unexpectedly.
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true | |
| # Force JavaScript-based actions in this workflow to run on Node 24. | |
| FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true" |
Sets FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true globally