Skip to content

Update github actions (main) (patch) - #3660

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-patch-github-actions
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/main-patch-github-actions

Conversation

@renovate

@renovate renovate Bot commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
jlumbroso/free-disk-space action patch v1.3.1 → v1.3.2
oras-project/setup-oras action patch v2.0.1 → v2.0.3
step-security/harden-runner action patch v2.22.3 → v2.22.4

Release Notes

jlumbroso/free-disk-space

v1.3.2: — security fix and the decision records

Compare Source

Fixes the template-injection pattern in input handling (#​51, by @​nbuckwalt).

Also adds docs/adr/ — the reasoning behind this action: why it exists, what it inherited from apache/flink and ShubhamTatvamasi, what it deliberately does not do, and what is still open.

No behaviour changes. The swap-storage default change ships in the next release.

oras-project/setup-oras

v2.0.3

Compare Source

Highlights

  • Support ORAS CLI version(s): 1.3.5, 1.3.6

What's Changed

New Contributors

Full Changelog: oras-project/setup-oras@v2.0.2...v2.0.3

v2.0.2

Compare Source

Highlights

  • Support ORAS CLI version(s): 1.3.4

What's Changed

New Contributors

Full Changelog: oras-project/setup-oras@v2.0.1...v2.0.2

step-security/harden-runner

v2.22.4

Compare Source

What's Changed

  • Fixed a Linux agent memory leak that could cause runners to run out of memory during jobs with heavy process or network activity.
  • The workaround for GitHub’s DNS resolver and outbound proxy experiment on GitHub-hosted Linux runners now defaults to enabled when feature flags can’t be fetched.
  • Improved HTTP/2 TLS interception on Linux (enterprise tier).
  • Added retries for failed monitoring API requests, improving reliability of monitoring initialization and raw-event uploads.

Full Changelog: step-security/harden-runner@v2.22.3...v2.22.4


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner October 30, 2026 01:25
@renovate
renovate Bot enabled auto-merge October 30, 2026 01:25
@coderabbitai

coderabbitai Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • Resume reviews
  • Trigger review

No actionable comments were generated in the recent review.

Walkthrough

Workflow files update pinned action versions or commits. The supplied summaries report no changes to workflow logic or other configuration.

Changes: Workflow action pin updates

Layer / File(s) Summary
Update workflow action pins
.github/workflows/benchmark.yaml, .github/workflows/checks-codecov.yaml, .github/workflows/codeql.yaml, .github/workflows/lint.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml, .github/workflows/website.yaml
The workflows update step-security/harden-runner to v2.22.4. The benchmark workflow updates oras-project/setup-oras to v2.0.3. The release workflow updates jlumbroso/free-disk-space to v1.3.2.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Suggested reviewers: dheerajodha, robnester-rh

Merge Risk: Minimal · previous review 12931

This updates pinned versions of CI actions with no change to workflow logic. No concrete merge risk is identified, and the failing Konflux check is an infrastructure error unrelated to these changes.

Pre-merge checks: Passed 5

Check name Status Explanation
Title check Passed The title accurately identifies a GitHub Actions update and matches the changeset. It is broad but still clear and meaningful.
Description check Passed The description is detailed and directly explains the action version updates and their release-note context. It does not use the repository's What, Why, and Tickets headings, but it provides the requi…
Docstring Coverage Passed No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description is detailed and directly explains the action version updates and their release-note context. It does not use the repository's What, Why, and Tickets headings, but it provides the required information in equivalent sections.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (7 skipped: 7 unsupported.)

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: b63ef80a-0ff0-493a-bb6a-094162072522
Commits

Reviewing files that changed from the base of the PR and between 24de848 and 12931ee.

Files selected for processing: 7

  • .github/workflows/benchmark.yaml
  • .github/workflows/checks-codecov.yaml
  • .github/workflows/codeql.yaml
  • .github/workflows/lint.yaml
  • .github/workflows/release.yaml
  • .github/workflows/scorecard.yml
  • .github/workflows/website.yaml
Files skipped from review as they are similar to previous changes: 4

  • .github/workflows/release.yaml
  • .github/workflows/codeql.yaml
  • .github/workflows/scorecard.yml
  • .github/workflows/benchmark.yaml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Oct 30, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Re-review anchoring applied: Tier 1 signals identical to prior assessment (7 CI workflow files, PROTECTED_PATH_COUNT=7, CI_WORKFLOW_CHANGED=true, bot author, no dependency changes); Tier 2 shows low churn and stable files; composite 0.62x2.13 + 0.38x1.14 = 1.75 rounds to 2, confirming prior moderate score.

Previous run

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot patch bump across 7 CI workflow files; Tier 1 sub-score of 2.13 driven by PROTECTED_PATH_COUNT=7 and CI_WORKFLOW_CHANGED=true but offset by bot authorship; Tier 2 sub-score of 2.14 reflects lifetime fix-commit accumulation; weighted composite (62/38 split, no linked issue) is 2.13, rounds to 2, consistent with the prior moderate assessment.

Previous run (2)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot patch bump of two CI workflow files (2 files, 4 lines, small blast radius); PROTECTED_PATH_COUNT=2 (score 5) and CI_WORKFLOW_CHANGED=true (score 4) elevate Tier 1 to 1.875, while Tier 2 sits at 1.71 driven by minor multi-author contention and revert history on release.yaml; weighted composite (62/38 split, no linked issue) is 1.81, rounded to 2, consistent with the prior moderate assessment.

Previous run (3)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot patch bump of four CI workflow files with XS diff (12 lines); PROTECTED_PATH_COUNT=4 (score 5) and CI_WORKFLOW_CHANGED=true (score 4) elevate Tier 1 to 2.0, but bot authorship, zero security sensitivity, and no dependency changes keep Tier 2 at 1.86, yielding a weighted composite of 1.95 (rounded to 2), consistent with the prior moderate assessment.

Previous run (4)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot patch bump of four GitHub Actions CI workflow files; Tier 1 scores 2.0 and Tier 2 scores 1.68 yield a composite of 1.88 (rounded to 2), anchored to the prior moderate assessment — bot authorship, XS size, and zero security sensitivity offset elevated signals from CI_WORKFLOW_CHANGED, all-protected-paths, and historical fix churn on benchmark.yaml.

Previous run (5)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot patch bump of four GitHub Actions CI workflow files; Tier 1 scores 2.0 and Tier 2 scores 2.14 yield a composite of 2.05 (rounded to 2), consistent with the prior assessment — bot authorship, XS size, and zero security sensitivity offset elevated signals from CI_WORKFLOW_CHANGED, all-protected-paths, and historical fix/revert churn on benchmark.yaml and release.yaml.

Previous run (6)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot patch bump of four GitHub Actions CI workflow files; bot authorship, XS size, and zero security-sensitive changes keep risk moderate, with elevation from CI_WORKFLOW_CHANGED, all files in protected paths, and benchmark.yaml historical fix/revert churn — consistent with prior assessment score of 2.

Previous run (7)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Routine Renovate bot bump of three GitHub Actions patch versions across four CI workflow files; bot authorship, XS size, and zero security-sensitive changes keep risk low, with a slight elevation from CI_WORKFLOW_CHANGED and benchmark.yaml historical fix/revert churn.

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml — PR modifies 7 files under the .github/ protected path (.github/workflows/benchmark.yaml, .github/workflows/checks-codecov.yaml, .github/workflows/codeql.yaml, .github/workflows/lint.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml, .github/workflows/website.yaml). No linked issue provides authorization for modifying governance/infrastructure files. Human approval is required for protected-path changes.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml — All 7 modified files (.github/workflows/benchmark.yaml, .github/workflows/checks-codecov.yaml, .github/workflows/codeql.yaml, .github/workflows/lint.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml, .github/workflows/website.yaml) are under the .github/ protected path. This PR has no linked issue providing justification for modifying governance or infrastructure files. Human approval is always required for protected-path changes.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run (2)

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml — This PR modifies files under protected paths (.github/): .github/workflows/benchmark.yaml and .github/workflows/release.yaml. The PR has no linked issue providing authorization for modifying governance/infrastructure files. Human approval is required for all protected-path changes.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run (3)

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml, .github/workflows/codeql.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml — All four changed files are under the .github/ protected path prefix. This PR has no linked issue providing justification for modifying governance or infrastructure files. Human approval is always required for protected-path changes, regardless of the change's nature.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run (4)

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml, .github/workflows/codeql.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml — All 4 changed files are under the .github/ protected path. This PR has no linked issue providing authorization for modifying governance/infrastructure files. Human approval is required for all protected-path changes.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run (5)

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml, .github/workflows/codeql.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml — All four changed files are under the .github/ protected path. This PR has no linked issue providing justification for modifying governance or infrastructure files. Human approval is always required for protected-path changes.

Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run (6)

Review

Findings

High

  • [protected-path] .github/workflows/ — This PR modifies 4 files under protected paths (.github/): benchmark.yaml, codeql.yaml, release.yaml, scorecard.yml. No linked issue provides justification for modifying governance or infrastructure files. Human approval is always required for protected-path changes.

Labels: All changes are CI workflow files; adding ci label per repo convention for workflow/pipeline changes.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

Previous run (7)

Review

Findings

High

  • [protected-path] .github/workflows/benchmark.yaml, .github/workflows/codeql.yaml, .github/workflows/release.yaml, .github/workflows/scorecard.yml — All 4 changed files are under .github/, a protected path. The PR has no linked issue to justify modifying governance/infrastructure files. Human approval is required for protected-path changes regardless of context.

Labels: PR updates GitHub Actions dependency versions across CI workflow files.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJmaW5kaW5ncyI6W119 -->

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added github_actions Pull requests that update GitHub Actions code dependencies Pull requests that update a dependency file labels Oct 30, 2026
@codecov

codecov Bot commented Oct 30, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag Coverage Δ
acceptance 54.61% <ø> (ø)
generative 12.22% <ø> (ø)
integration 23.62% <ø> (ø)
unit 72.29% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 5e80b23 to 8095d0d Compare November 1, 2026 21:56
fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added the ci label Nov 1, 2026
@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 8095d0d to ed58e2b Compare November 3, 2026 11:37
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from ed58e2b to 786fe79 Compare November 3, 2026 15:32
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 786fe79 to 594c399 Compare November 5, 2026 10:06
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 594c399 to 24de848 Compare November 10, 2026 01:40
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 24de848 to 12931ee Compare November 11, 2026 17:58
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 12931ee to 690fd63 Compare November 12, 2026 13:35
@fullsend-ai-review

Copy link
Copy Markdown

🤖 Finished Review · ❌ Failure (validation failed after 1 iteration(s)) · Started 1:37 PM UTC · Completed 1:47 PM UTC

Commit: 690fd63 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.58

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 690fd63 to 3e01be7 Compare November 12, 2026 14:07

@fullsend-ai-review fullsend-ai-review Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See the review comment for full details.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code main renovate risk/moderate PR risk: moderate size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants