Upgrade GitHub Actions to latest versions#3775
Upgrade GitHub Actions to latest versions#3775salmanmkc wants to merge 1 commit intonvm-sh:masterfrom
Conversation
Signed-off-by: Salman Muin Kayser Chishti <[email protected]>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
|
thanks - but please don't use LLMs for open source contributions, or for comment prose. |
ljharb
left a comment
There was a problem hiding this comment.
what are the differences between setup-wsl v3 and v6?
| - run: npm run doctoc | ||
| - name: commit changes | ||
| uses: ljharb/actions-js-build/commit@v3+amendpush | ||
| uses: ljharb/actions-js-build/commit@v3 |
There was a problem hiding this comment.
this isn't an upgrade, this is a downgrade
Summary
Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.
Changes
Vampire/setup-wslv3v6ljharb/actions-js-build/commitv3+amendpushv3Why upgrade?
Keeping GitHub Actions up to date ensures:
Security Note
Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.
Testing
These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.