build: update all github actions#3640
Conversation
See associated pull request for more information.
There was a problem hiding this comment.
Code Review
This pull request updates the actions/setup-node version to v6.4.0 in the checkout-and-setup-node GitHub Action. A review comment highlights that the changes are incomplete relative to the PR's stated objectives, as other actions such as astral-sh/setup-uv, actions/checkout, and pnpm/action-setup remain on older versions.
| run_install: false | ||
|
|
||
| - uses: actions/setup-node@53b83947a5a98c8d113130e565377fae1a50d02f # v6.3.0 | ||
| - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0 |
There was a problem hiding this comment.
The pull request title and description indicate that all GitHub Actions should be updated, including astral-sh/setup-uv. However, the current changes only update actions/setup-node. Other actions in this file, such as actions/checkout (line 41) and pnpm/action-setup (line 57), remain on older versions, and the setup-uv update mentioned in the description is missing entirely from the patches.
|
This PR was merged into the repository. The changes were merged into the following branches:
|
This PR contains the following updates:
v6.3.0→v6.4.0v8.0.0→v8.1.0Release Notes
actions/setup-node (actions/setup-node)
v6.4.0Compare Source
What's Changed
Dependency updates:
New Contributors
Full Changelog: actions/setup-node@v6...v6.4.0
astral-sh/setup-uv (astral-sh/setup-uv)
v8.1.0: 🌈 New inputno-projectCompare Source
Changes
This add the a new boolean input
no-project.It only makes sense to use in combination with
activate-environment: trueand will append--no projectto theuv venvcall. This is for example useful if you have a pyproject.toml file with parts unparseable by uv🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates