Skip to content

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

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 25, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Pending
github/codeql-action action patch v4.39.0 → v4.39.3 v4.39.4
step-security/harden-runner action patch v2.22.1 → v2.22.4

Release Notes

github/codeql-action

v4.39.3

Compare Source

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #​4283

v4.39.2

Compare Source

  • Update default CodeQL bundle version to 2.27.4. #​4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #​4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #​4243

v4.39.1

Compare Source

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

v2.22.3

Compare Source

What's Changed

  • Added support for Avrea-hosted runners (enterprise tier)
  • Fixed unexpected blocking of allowed connections caused by GitHub’s DNS resolver and outbound proxy experiment on GitHub-hosted Linux runners
  • Added a feature flag to disable implicit AWS endpoint allowances on self-hosted Linux runners (enterprise tier)

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

v2.22.2

Compare Source

What's Changed
  • Fixed inbound (ingress) network traffic being incorrectly classified as outbound (egress) traffic on macOS
  • Fixed implicit endpoints intended for self-hosted runners being applied to custom VM environments on Linux (enterprise tier)
  • Improved network and DNS tracing, enforcement logic, and process information correlation on Linux (enterprise tier)

Full Changelog: step-security/harden-runner@v2.22.1...v2.22.2


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 added the main label Oct 25, 2026
@renovate
renovate Bot requested a review from a team as a code owner October 25, 2026 01:20
@renovate
renovate Bot enabled auto-merge (squash) October 25, 2026 01:20
@coderabbitai

coderabbitai Bot commented Oct 25, 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

Three GitHub Actions workflows update pinned action revisions. The Harden Runner pin changes to v2.22.3. The Scorecard workflow also updates the CodeQL SARIF upload pin to v4.39.3.

Changes: Workflow action pin updates

Layer / File(s) Summary
Update workflow action pins
.github/workflows/docs.yaml, .github/workflows/validate-docs.yaml, .github/workflows/scorecards.yml
The three workflows update the Harden Runner pin to v2.22.3. The Scorecard workflow updates the CodeQL SARIF upload pin to v4.39.3. Existing configuration remains unchanged.

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

Change: Other

Suggested reviewers: robnester-rh, cuipinghuo, simonbaird

Merge Risk: Minimal · previous review c10f7

This updates CI action pins and does not change application behavior. No actionable merge-blocking risk is evident from the supplied context.

Pre-merge checks: Passed 5

Check name Status Explanation
Title check Passed The title identifies GitHub Actions updates, which is related to the changes, but it does not name the actions or versions.
Description check Passed The description explains the GitHub Actions version updates and includes relevant release notes.
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: 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. (1 skipped: 1 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: 222c588d-1e88-455b-b9e3-766b73757a28
Commits

Reviewing files that changed from the base of the PR and between cf031cc and c10f73e.

Files selected for processing: 1

  • .github/workflows/scorecards.yml
Files skipped from review as they are similar to previous changes: 1

  • .github/workflows/scorecards.yml

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 25, 2026
@fullsend-ai-review

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

Copy link
Copy Markdown

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

Details

Renovate bot PR making a minimal 8-line version bump across 3 CI workflow files; Tier 1 signals are unchanged from the prior assessment (bot author, XS size, zero security-sensitive changes, 3 protected CI paths, active workflow change), Tier 2 is unavailable due to shallow repository, and no linked issue provides Tier 3 context — the composite remains moderate at 2.

Previous run

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

Details

Renovate bot PR making a minimal 8-line version bump across 3 CI workflow files; Tier 1 signals are unchanged from the prior assessment (bot author, XS size, zero security-sensitive changes), and while all files are protected CI paths with an active workflow change driving moderate risk, the low Tier 2 churn and stable history confirm a moderate composite score of 2.

Previous run (2)

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

Details

Renovate bot PR making a minimal 8-line version bump across 3 CI workflow files; the bot author, XS size, and zero security-sensitive changes keep risk low, but all files are protected CI paths and a workflow changed, yielding a moderate composite score of 2.

Previous run (3)

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

Details

Bot-authored patch bump of github/codeql-action and step-security/harden-runner across 3 CI workflow files (8 lines changed); signals are unchanged from prior assessment (PROTECTED_PATH_COUNT=3, CI_WORKFLOW_CHANGED=true, bot-authored, small blast radius, no regression commits), yielding composite 0.62x1.875 + 0.38x1.57 = 1.76, rounded to 2 (moderate), consistent with prior score.

Previous run (4)

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

Details

Bot-authored patch bump of github/codeql-action and step-security/harden-runner across 3 CI workflow files (8 lines changed); Tier 1 and Tier 2 signals are unchanged from prior assessment (PROTECTED_PATH_COUNT=3, CI_WORKFLOW_CHANGED=true, bot-authored, small blast radius, avg churn 3.33 commits/file, no fix/revert commits), yielding composite 0.62x1.875 + 0.38x1.43 = 1.71, rounded to 2 (moderate), consistent with prior score.

Previous run (5)

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

Details

Bot-authored patch bump of github/codeql-action and step-security/harden-runner across 3 CI workflow files (8 lines changed); Tier 1 signals are identical to prior assessment (PROTECTED_PATH_COUNT=3, CI_WORKFLOW_CHANGED=true, bot-authored, small blast radius), yielding composite 0.62×1.875 + 0.38×1.43 = 1.71, rounded to 2 (moderate), unchanged from prior score.

Previous run (6)

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

Details

Bot-authored patch bump of github/codeql-action and step-security/harden-runner across 3 CI workflow files (8 lines changed); PROTECTED_PATH_COUNT=3 and CI_WORKFLOW_CHANGED=true elevate Tier 1 to 1.875, offset by bot authorship and minimal blast radius, yielding 0.62x1.875 + 0.38x1.57 = 1.76, rounded to 2 (moderate), unchanged from prior assessment.

Previous run (7)

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

Details

Bot-authored patch bump of step-security/harden-runner across 3 CI workflow files (6 lines changed); PROTECTED_PATH_COUNT and CI_WORKFLOW_CHANGED elevate Tier 1 but the change is routine and low-complexity, yielding a composite of 0.62×1.875 + 0.38×1.43 ≈ 1.71, rounded to 2 (moderate).

@fullsend-ai-review

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

Copy link
Copy Markdown

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml — This PR modifies files under protected paths (.github/): .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml. The PR has no linked issue providing justification for modifying governance or 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

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml — PR modifies files under the protected .github/ path. The PR has no linked issue providing authorization for modifying governance or 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 (2)

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml — All 3 changed files are under the .github/ protected path. The PR has no linked issue providing authorization for modifying governance or 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 (3)

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml — This PR modifies files under protected path .github/: .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml. The PR has no linked issue providing justification 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 (4)

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml — All 3 changed files are under the .github/ protected path. This PR has no linked issue providing justification for modifying governance/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 (5)

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml — PR modifies 3 files under the protected .github/ path: .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml. The PR has no linked issue providing justification for modifying governance or 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 (6)

Review

Findings

High

  • [protected-path] .github/workflows/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml — All changed files are under the protected .github/ path. No linked issue provides authorization for modifying governance/infrastructure files. Human approval is required for changes to protected paths.

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/docs.yaml, .github/workflows/scorecards.yml, .github/workflows/validate-docs.yaml — All changed files are under the .github/ protected path. This PR has no linked issue providing justification for modifying governance/infrastructure files. Human approval is required for protected-path changes.
    Remediation: A maintainer must manually review and approve changes to files under protected paths (.github/).

Labels: PR updates a GitHub Actions dependency (step-security/harden-runner) via Renovate.


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 dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Oct 25, 2026
@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from de4bc67 to 7035872 Compare October 26, 2026 17:53
@renovate renovate Bot changed the title Update step-security/harden-runner action to v2.22.2 (main) Update github actions (main) (patch) Oct 26, 2026
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from 7035872 to e491069 Compare November 1, 2026 21:16
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from e491069 to cf031cc Compare November 8, 2026 13:57
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from cf031cc to c10f73e Compare November 9, 2026 21:58
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from c10f73e to cf36f71 Compare November 11, 2026 18:09
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from cf36f71 to cdfe3f6 Compare November 17, 2026 13:04
fullsend-ai-review[bot]

This comment was marked as outdated.

@renovate
renovate Bot force-pushed the renovate/main-patch-github-actions branch from cdfe3f6 to 0975e1d Compare November 18, 2026 11:58
@fullsend-ai-review

Copy link
Copy Markdown

Review skipped — PR author app/renovate is in the REVIEW_SKIP_AUTHORS list.

Posted by fullsend pre-review check

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

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

Labels

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