-
-
Notifications
You must be signed in to change notification settings - Fork 130
👷 ci: unpin nodejs version #571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR removes the pinned Node.js version from CI workflows to allow for more flexible version management. The change aligns with the CI category indicated in the PR description and removes explicit version constraints that may have been causing compatibility or maintenance issues.
- Unpins Node.js version specification from GitHub Actions workflows
- Maintains pnpm caching configuration while removing version constraints
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/vitepress-deploy.yml | Removes pinned Node.js version "22" from VitePress deployment workflow |
| .github/workflows/lint-and-fmt.yml | Removes pinned Node.js version "22" from linting and formatting workflow |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
|
||
| - name: Setup Node.js | ||
| uses: actions/setup-node@v5 | ||
| with: |
Copilot
AI
Sep 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the node-version specification will cause the workflow to use the default Node.js version provided by the runner, which may change unexpectedly and cause build inconsistencies. Consider specifying a version range (e.g., '>=18') or using a .nvmrc file to maintain predictable builds while allowing flexibility.
| with: | |
| with: | |
| node-version: '>=18' |
|
|
||
| - name: Setup Node.js | ||
| uses: actions/setup-node@v5 | ||
| with: |
Copilot
AI
Sep 20, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removing the node-version specification will cause the workflow to use the default Node.js version provided by the runner, which may change unexpectedly and cause build inconsistencies. Consider specifying a version range (e.g., '>=18') or using a .nvmrc file to maintain predictable builds while allowing flexibility.
| with: | |
| with: | |
| node-version: '>=18' |
CodSpeed Performance ReportMerging #571 will not alter performanceComparing Summary
|
动机
解决方案
类型