Skip to content

Use package.json Node version in deploy action - #24

Closed
mattt wants to merge 1 commit into
mainfrom
mattt/action-node-version
Closed

mattt wants to merge 1 commit into
mainfrom
mattt/action-node-version

Conversation

@mattt

@mattt mattt commented Sep 8, 2026

Copy link
Copy Markdown
Member

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Using node-version-file with an unbounded engines.node range can cause future major Node upgrades in deploy runs, reducing reproducibility and risking breakages.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR updates the deploy GitHub Actions workflow to select the Node.js version from the checked-out project’s package.json rather than hard-coding a Node version in the workflow, aiming to keep deploy behavior aligned with the application’s declared runtime requirements.

Changes:

  • Switch actions/setup-node to use node-version-file: package.json instead of node-version: 22.
File summaries
File Description
.github/workflows/deploy.yml Uses package.json to determine the Node.js version during deploy runs.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

uses: actions/setup-node@v7
with:
node-version: 22
node-version-file: package.json
@mattt mattt closed this Sep 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants