chore(deps): bump actions/checkout from 6.0.2 to 6.0.3#218
Open
dependabot[bot] wants to merge 5 commits into
Open
chore(deps): bump actions/checkout from 6.0.2 to 6.0.3#218dependabot[bot] wants to merge 5 commits into
dependabot[bot] wants to merge 5 commits into
Conversation
Bumps [actions/checkout](https://github.com/actions/checkout) from 6.0.2 to 6.0.3. - [Release notes](https://github.com/actions/checkout/releases) - [Commits](actions/checkout@v6.0.2...v6.0.3) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
dosubot
Bot
added
the
size:XS
Contributor
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 CI must passWonderful, this rule succeeded.All CI checks must pass. Release-plz PRs are exempt because they only bump versions and changelogs (code was already tested on main), and GITHUB_TOKEN-triggered force-pushes suppress CI.
🟢 Do not merge outdated PRsWonderful, this rule succeeded.Make sure PRs are within 3 commits of the base branch before merging
|
Contributor
|
Related Knowledge 2 documents with suggested updates are ready for review. Gold Digger Automated Release ManagementView Suggested Changes@@ -76,7 +76,7 @@
## Integration with Existing Release Workflows
-Release Please creates release PRs with updated version numbers and changelogs. When a release PR is merged, it creates a git tag for the new version. The existing release workflow (`.github/workflows/release.yml`) is configured to trigger on these tags, handling artifact building, signing, and publishing. The workflow uses cargo-dist v0.31.0 for distribution and pins all GitHub Actions to specific commit SHAs (`actions/checkout@v6.0.2`, `actions/upload-artifact@v7.0.0`, `actions/download-artifact@v8`) for improved security and reproducibility. Build artifacts include attestations generated via `actions/attest-build-provenance@v4`, which provide cryptographically verifiable build provenance for supply chain security. This ensures that the release process is fully automated from commit to published release [source](https://github.com/EvilBit-Labs/gold_digger/issues/57#issuecomment-3203749857).
+Release Please creates release PRs with updated version numbers and changelogs. When a release PR is merged, it creates a git tag for the new version. The existing release workflow (`.github/workflows/release.yml`) is configured to trigger on these tags, handling artifact building, signing, and publishing. The workflow uses cargo-dist v0.31.0 for distribution and pins all GitHub Actions to specific commit SHAs (`actions/checkout@v6.0.3`, `actions/upload-artifact@v7.0.0`, `actions/download-artifact@v8`) for improved security and reproducibility. Build artifacts include attestations generated via `actions/attest-build-provenance@v4`, which provide cryptographically verifiable build provenance for supply chain security. This ensures that the release process is fully automated from commit to published release [source](https://github.com/EvilBit-Labs/gold_digger/issues/57#issuecomment-3203749857).
```yaml
name: ReleaseGold Digger Release ProcessView Suggested Changes@@ -147,7 +147,7 @@
The release workflow follows security best practices:
-- **Pinned Action Commits**: All GitHub Actions are pinned to specific commit SHAs rather than floating version tags, ensuring reproducibility and protecting against supply chain attacks. Examples include `actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd` (v6.0.2), `actions/upload-artifact@v7.0.0`, and `actions/download-artifact@v8`.
+- **Pinned Action Commits**: All GitHub Actions are pinned to specific commit SHAs rather than floating version tags, ensuring reproducibility and protecting against supply chain attacks. Examples include `actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10` (v6.0.3), `actions/upload-artifact@v7.0.0`, and `actions/download-artifact@v8`.
- **Build Provenance**: The `actions/attest-build-provenance@v4` step creates verifiable attestations for all artifacts, providing cryptographic proof of the build environment and process.
How did I do? Any feedback? |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Bumps actions/checkout from 6.0.2 to 6.0.3.
Release notes
Sourced from actions/checkout's releases.
Commits
df4cb1cUpdate changelog for v6.0.3 (#2446)1cce339Fix checkout init for SHA-256 repositories (#2439)900f221fix: expand merge commit SHA regex and add SHA-256 test cases (#2414)0c366fdUpdate changelog (#2357)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)