Upgrade GitHub Actions to latest versions#18570
Closed
salmanmkc wants to merge 1 commit intogithub:mainfrom
Closed
Upgrade GitHub Actions to latest versions#18570salmanmkc wants to merge 1 commit intogithub:mainfrom
salmanmkc wants to merge 1 commit intogithub:mainfrom
Conversation
Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR upgrades multiple GitHub Actions to their latest versions by pinning them to specific commit SHAs for enhanced supply-chain security. The upgrades include security-related actions (CodeQL, Trivy, Gosec scanners), Docker build tools, SBOM generation, documentation deployment, and code quality tools.
Changes:
- Upgraded CodeQL actions from v3 to v4 across multiple workflow files (breaking change)
- Updated Docker build/push/login/metadata actions to latest v6/v3/v5 commit SHAs
- Upgraded security scanning tools (Trivy, vet-action) to latest versions
- Updated documentation deployment and SBOM generation actions
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/vet.yml | Updated safedep/vet-action and codeql-action/upload-sarif to latest versions |
| .github/workflows/super-linter.md | Updated super-linter to latest v8 commit SHA |
| .github/workflows/stale-repo-identifier.md | Updated github/stale-repos from v3.0.2 to v8.0.4 |
| .github/workflows/security-scan.yml | Updated CodeQL upload-sarif actions to v4 and Trivy to 0.34.1 |
| .github/workflows/release.md | Updated Docker build tools and anchore/sbom-action to latest versions |
| .github/workflows/docs.yml | Updated actions/upload-pages-artifact from v3 to v4 |
| .github/workflows/codeql.yml | Updated CodeQL init and analyze actions from v3 to v4 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrade GitHub Actions to their latest versions for improved features, bug fixes, and security updates.
Changes
actions/upload-pages-artifact56afc607b1f4a7anchore/sbom-actionv017ae174aquasecurity/trivy-actionb6643a2e368e32docker/build-push-actionv610e90e3docker/login-actionv3c94ce9fdocker/metadata-actionv5c299e40docker/setup-buildx-actionv38d2750cgithub/codeql-action/analyze4248455bb471cdgithub/codeql-action/init4248455bb471cdgithub/codeql-action/upload-sarif4248455,v3bb471cdgithub/stale-reposv3.0.26084a41safedep/vet-actionv1e2a7885super-linter/super-linterv8.5.061abc07Why upgrade?
Keeping GitHub Actions up to date ensures:
Security Note
🔒 All actions are pinned to commit SHAs for maximum supply-chain security. Each reference includes a version comment (e.g.,
actions/checkout@abc123 # v6) for easy identification.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.