Repository navigation
Update github actions (main) - #3627
red-hat-konflux[bot] wants to merge 1 commit into
Conversation
|
<!-- fullsend:risk-assessment --> DetailsRoutine Renovate bot SHA-pin update across the same 8 CI workflow files as prior review; unchanged Tier 1 signals and a Tier 2 composite of 1.875 both confirm the prior moderate score of 2, with benchmark.yaml elevated fix/revert history (12 in 90d) reflecting ongoing CI maintenance rather than instability. Previous runRisk Assessment: moderate (2/5) DetailsRoutine Renovate bot GitHub Actions SHA bump across 8 CI workflow files; low blast radius and bot authorship keep composite risk moderate despite all files being under the protected .github/ path. Previous run (2)Risk Assessment: moderate (2/5) DetailsRoutine Renovate bot PR updating GitHub Actions versions across 8 CI workflow files; Tier 1 signals identical to prior assessment (elevated PROTECTED_PATH_COUNT and CI_WORKFLOW_CHANGED structural to any CI workflow PR, offset by bot authorship and zero security-sensitive files), Tier 2 git history unchanged, composite 1.92 rounds to 2. Previous run (3)Risk Assessment: moderate (2/5) DetailsRoutine Renovate bot PR updating GitHub Actions versions across 8 CI workflow files. Tier 1 signals unchanged from prior assessment (2/5 moderate): elevated PROTECTED_PATH_COUNT and CI_WORKFLOW_CHANGED are structural to any CI workflow PR, offset by bot authorship, zero security-sensitive files, and XS line count. Tier 2 regression-history score driven by EC-1818 benchmark feature iterations, not post-ship breakage. Composite 2.30 rounds to 2. Previous run (4)Risk Assessment: moderate (2/5) DetailsRoutine Renovate bot PR updating GitHub Actions versions across 8 CI workflow files; bot authorship, zero security-sensitive files, and low recent churn offset the elevated protected-path count and CI_WORKFLOW_CHANGED flag, yielding a moderate composite of 2. |
ReviewFindingsHigh
Labels: PR updates GitHub Actions version pins across CI workflow files Next steps:
<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous runReviewFindingsHigh
Next steps:
<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (2)ReviewFindingsMedium
<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (3)Automated Renovate dependency bump: pinned action SHA/version updates for <!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> Previous run (4)ReviewFindingsHigh
Next steps:
<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 --> |
Codecov Report✅ All modified and coverable lines are covered by tests.
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
0c18175 to
292faaa
Compare
Superseded by updated review
4b6688c to
f89003c
Compare
|
🤖 Review · Commit: |
f89003c to
bbf77ed
Compare
bbf77ed to
5181ab3
Compare
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
5181ab3 to
90c8983
Compare
|
🤖 Review · Commit: |
This PR contains the following updates:
837d70f→ff1126b837d70f→ff1126bv4.38.2→v4.39.0v4.39.1v2.4.4→v2.5.0v2.21.1→v2.22.1v2.22.2Release Notes
github/codeql-action (github/codeql-action)
v4.39.0Compare Source
codeql-action/analyzestep now validates that a correct argument for thecheckout_pathinput has been provided. Thecheckout_pathinput must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used bycodeql-action/init, then the CodeQL Action now produces a warning. #4148codeql-action/start-proxystep that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic ascodeql-action/init. This primarily benefits customers who are using GitHub instances other thangithub.comwhere thecodeql-action/start-proxystep may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #4198v4.38.3Compare Source
ossf/scorecard-action (ossf/scorecard-action)
v2.5.0Compare Source
What's Changed
This release moves the action to Scorecard v5.6.0, the first Scorecard release since its hosted
services moved to new infrastructure.
For changes to checks and results, and what the infrastructure move means for you, see the
Scorecard v5.6.0 release notes.
@justaugustus in #1716
cmd/installer) now creates.github/workflows/scorecard.yml, and stillrecognizes existing
scorecards.ymlandscorecards-analysis.ymlworkflows. by @justaugustus in #1716with. by @justaugustus in #1718
@arpitjain099 in #1709
results_formatacceptsintoto, which wraps the JSON results in an in-toto attestationstatement. by @puerco in #1702
Other
RELEASE.md by @justaugustus in #1716
New Contributors
Full Changelog: ossf/scorecard-action@v2.4.4...v2.5.0
step-security/harden-runner (step-security/harden-runner)
v2.22.1Compare Source
What's Changed
Full Changelog: step-security/harden-runner@v2.22.0...v2.22.1
v2.22.0Compare Source
What's Changed
Full Changelog: step-security/harden-runner@v2.21.1...v2.22.0
Configuration
📅 Schedule: (UTC)
* 0-3 * * *)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.