build(deps): bump action SHAs + resolve 3 supply-chain TODOs#15
Draft
bryanfawcett wants to merge 1 commit into
Draft
build(deps): bump action SHAs + resolve 3 supply-chain TODOs#15bryanfawcett wants to merge 1 commit into
bryanfawcett wants to merge 1 commit into
Conversation
Applies the Dependabot #14 SHA bumps (8 actions across 12 workflow files) and resolves the 3 outstanding TODO(supply-chain) pins that Dependabot does not track: SHA bumps (from Dependabot PR #14): - actions/checkout v6.0.2 → v6.0.3 (df4cb1c) - pnpm/action-setup v6.0.2 → v6.0.8 (0e279bb) - astral-sh/setup-uv v8.1.0 → v8.2.0 (fac544c) - github/codeql-action v4.35.2 → v4.36.2 (8aad20d) - actions/dependency-review-action v4.9.0 → v5.0.0 (a1d282b) - DavidAnson/markdownlint-cli2-action v23.0.0 → v23.2.0 (ded1f94) - actions/stale v10.2.0 → v10.3.0 (eb5cf3a) TODO SHA pins resolved (NA-03 §7.1.1): - ossf/scorecard-action@v2 → v2.4.3 SHA (4eaacf0) - actions/upload-artifact@v4 → v7.0.1 SHA (043fb46) (major-version bump; v7 is the current stable) - foundry-rs/foundry-toolchain@v1 → v1.8.0 SHA (c7450ba) ×4 (all four uses in reusable-ci-solidity.yml) ORG_SETTINGS.md: - Secret scanning non-provider patterns: "Enabled for public repos" → "Enabled org-wide" (correct intended state) Closes #14 (Dependabot PR incorporated directly). https://claude.ai/code/session_01BpyforRsUYR5iVDTrP9YKh
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
2 participants
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
Enterprise supply-chain hardening pass: incorporates the open Dependabot PR #14 SHA bumps and resolves the 3
TODO(supply-chain)pins that were left in the tree because the SHA values weren't yet known at authoring time. Zero floating action tags remain in the org's reusable workflows after this PR.SHA bumps (from Dependabot PR #14 — incorporated directly)
actions/checkoutde0fac2edf4cb1c0pnpm/action-setup71c924740e279bb9astral-sh/setup-uv08807647fac544c0github/codeql-action95e58e9a8aad20d1actions/dependency-review-action2031cfc0a1d282b3DavidAnson/markdownlint-cli2-actionce4853d4ded1f948actions/staleb5d41d4eeb5cf3afTODO SHA pins resolved (NA-03 §7.1.1)
These three pins were left as
TODOstubs in the original PR because SHA resolution required a live GitHub API call. All three are now fully pinned:ossf/scorecard-action@v2→ v2.4.3 (4eaacf05) — inreusable-openssf-scorecard.ymlactions/upload-artifact@v4→ v7.0.1 (043fb46d) — inreusable-openssf-scorecard.yml; also brings forward the major-version bump that Dependabot PR build(deps): bump the all group across 1 directory with 8 updates #14 would have applied as a floating@v7tagfoundry-rs/foundry-toolchain@v1→ v1.8.0 (c7450ba6) — inreusable-ci-solidity.yml×4ORG_SETTINGS.md
Test plan
@vNor@mainaction tags remain:grep -rE 'uses: [^@]+@v[0-9]' .github/workflows/Breaking changes
actions/dependency-review-actionv4 → v5 is a major bump. The action's interface in this workflow is limited tofail-on-severityandcomment-summary-in-prinputs, both of which are unchanged in v5. No caller-side changes needed.https://claude.ai/code/session_01BpyforRsUYR5iVDTrP9YKh
Generated by Claude Code