Skip to content

chore(deps): bump the github-actions group across 1 directory with 3 updates - #4250

Merged
tekton-robot merged 1 commit into
mainfrom
dependabot/github_actions/github-actions-354d78c9e6
Oct 12, 2026
Merged

tekton-robot merged 1 commit into
mainfrom
dependabot/github_actions/github-actions-354d78c9e6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the github-actions group with 3 updates in the / directory: step-security/harden-runner, chainguard-dev/actions/kind-diag and fgrosse/go-coverage-report.

Updates step-security/harden-runner from 2.21.1 to 2.22.0

Release notes

Sourced from step-security/harden-runner's releases.

v2.22.0

What's Changed

  • Linux ARM64 support for community tier
  • GHES support for self-hosted VMs (enterprise tier)
  • MacOS and Windows runner deny list support for block policy (enterprise tier).

Full Changelog: step-security/harden-runner@v2.21.1...v2.22.0

Commits

Updates chainguard-dev/actions/kind-diag from 1.6.37 to 1.6.40

Release notes

Sourced from chainguard-dev/actions/kind-diag's releases.

v1.6.40

What's Changed

New Contributors

Full Changelog: chainguard-dev/actions@v1.6.39...v1.6.40

v1.6.39

What's Changed

Full Changelog: chainguard-dev/actions@v1.6.38...v1.6.39

v1.6.38

What's Changed

Full Changelog: chainguard-dev/actions@v1.6.37...v1.6.38

Commits
  • 84b1be4 fix(setup-eksctl): match archive checksum exactly (#1066)
  • ec1df73 fix(release): stop persisting checkout credentials (#1065)
  • 0a46f70 fix(git-tag): push with the token input via a credential helper (#1062)
  • afed75b build(deps): bump @​octokit/app from 16.1.2 to 16.1.4 in /githubapp-token (#1060)
  • 4eb623e release-notes: set up the stable Go release instead of 1.25 (#1059)
  • 24c9d6b githubapp-token: install @​octokit/app from a lockfile (#1057)
  • 65926d1 hugo2confluence: fix gomarkdown OOB read, require Go 1.27 (#1058)
  • de02a2b ci: suppress zizmor self-repository on local action refs (#1052)
  • d2cfb82 ci: suppress zizmor github-env on fixed PATH/ENV writes (#1053)
  • ee8d9ae setup-kind: validate registry-authority before writing GITHUB_ENV (#1054)
  • Additional commits viewable in compare view

Updates fgrosse/go-coverage-report from 1.4.0 to 1.5.0

Release notes

Sourced from fgrosse/go-coverage-report's releases.

v1.5.0

  • If the base commit of the pull request has no usable baseline run (e.g. because it failed, is still running or its artifact expired), the action now uses the nearest commit in the first-parent history of the base commit with a usable run instead of the latest run on the target branch. The runs of each commit are filtered client-side, since the filtered workflow runs API can return stale results, and further candidates are tried if a coverage artifact cannot be downloaded or does not fgrosse/go-coverage-report#113
  • Add baseline-search-depth and baseline-max-downloads inputs to configure how far the action searches for a baseline fgrosse/go-coverage-report#113
  • fgrosse/go-coverage-report#13
  • Behavior change: By default, the baseline coverage is now taken from the latest successful run for the base commit of the pull request (new baseline-sha input, defaults to github.event.pull_request.base.sha) instead of the latest successful run on the target branch. If there is no such run, the action falls back to the latest successful run on the target branch and emits a warning. Set baseline-sha to ""fgrosse/go-coverage-report#110
  • Add baseline-run-idfgrosse/go-coverage-report#110
  • Improve diagnostics when no baseline coverage is available: warnings and the pull request comment now distinguish between no successful baseline run being found and the coverage artifact of the selected run not being downloadable, and the fgrosse/go-coverage-report#110
  • Show a caution callout at the top of the pull request comment if the report does not compare against the base commit fgrosse/go-coverage-report#110
  • Name the baseline commit and run in the details section of the report via the new -baseline-commit, -baseline-run-id and -baseline-run-urlfgrosse/go-coverage-report#110
  • Simplify the details section of the report: rename it to "Coverage details" and drop its headings to avoid mixing many fgrosse/go-coverage-report#110
Changelog

Sourced from fgrosse/go-coverage-report's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

Nothing yet

[v1.5.0] - 2026-10-02

  • If the base commit of the pull request has no usable baseline run (e.g. because it failed, is still running or its artifact expired), the action now uses the nearest commit in the first-parent history of the base commit with a usable run instead of the latest run on the target branch. The runs of each commit are filtered client-side, since the filtered workflow runs API can return stale results, and further candidates are tried if a coverage artifact cannot be downloaded or does not fgrosse/go-coverage-report#113
  • Add baseline-search-depth and baseline-max-downloads inputs to configure how far the action searches for a baseline fgrosse/go-coverage-report#113
  • fgrosse/go-coverage-report#13
  • Behavior change: By default, the baseline coverage is now taken from the latest successful run for the base commit of the pull request (new baseline-sha input, defaults to github.event.pull_request.base.sha) instead of the latest successful run on the target branch. If there is no such run, the action falls back to the latest successful run on the target branch and emits a warning. Set baseline-sha to ""fgrosse/go-coverage-report#110
  • Add baseline-run-idfgrosse/go-coverage-report#110
  • Improve diagnostics when no baseline coverage is available: warnings and the pull request comment now distinguish between no successful baseline run being found and the coverage artifact of the selected run not being downloadable, and the fgrosse/go-coverage-report#110
  • Show a caution callout at the top of the pull request comment if the report does not compare against the base commit fgrosse/go-coverage-report#110
  • Name the baseline commit and run in the details section of the report via the new -baseline-commit, -baseline-run-id and -baseline-run-urlfgrosse/go-coverage-report#110
  • Simplify the details section of the report: rename it to "Coverage details" and drop its headings to avoid mixing many fgrosse/go-coverage-report#110

[v1.4.0] - 2026-09-20

  • Also report packages whose coverage changed without any of their files being changed, e.g. when running integration tests with go test -coverpkgfgrosse/go-coverage-report#102
  • fgrosse/go-coverage-report#103
  • Fix the excludefgrosse/go-coverage-report#104

[v1.3.1] - 2026-07-20

  • fgrosse/go-coverage-report#82
  • Fix the ::endgroup::fgrosse/go-coverage-report#89

[v1.3.0] - 2026-03-11

  • Add event-name and target-branch inputs to support workflows triggered by events other than pushfgrosse/go-coverage-report#58
  • fgrosse/go-coverage-report#72
  • fgrosse/go-coverage-report#71
  • Add --excludefgrosse/go-coverage-report#59
  • Add structured outputs (total_coverage, coverage_delta, coverage_trend, total_statements, covered_statements, missed_statementsfgrosse/go-coverage-report#64

[v1.2.0] - 2024-08-28

... (truncated)

Commits
  • c4bf7e7 Release v1.5.0
  • 2d3d0a9 action: fall back to the nearest ancestor of the base commit (#113)
  • 7752bdc action: select the baseline by the PR base commit and explain it in the repor...
  • 6093ed4 Bump github/codeql-action from 4.38.0 to 4.38.1 (#112)
  • b1b031a go-coverage-report: drop package name limitation (#111)
  • See full diff in compare view

@dependabot dependabot Bot added dependencies Used by dependabot - identifies all PRs created by dependabot kind/misc Categorizes issue or PR as a miscellaneuous one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesnt merit a release note. labels Oct 12, 2026
@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Oct 12, 2026
@codecov

codecov Bot commented Oct 12, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 30.25%. Comparing base (64b3dae) to head (2951afe).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4250   +/-   ##
=======================================
  Coverage   30.25%   30.25%           
=======================================
  Files         478      478           
  Lines       23169    23169           
=======================================
  Hits         7010     7010           
  Misses      16159    16159           
Flag Coverage Δ
unit-tests 30.25% <ø> (ø)

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

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

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

@khrm khrm left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 12, 2026
@jkhelil

jkhelil commented Oct 12, 2026

Copy link
Copy Markdown
Member

@dependabot rebase

…updates

Bumps the github-actions group with 3 updates in the / directory: [step-security/harden-runner](https://github.com/step-security/harden-runner), [chainguard-dev/actions/kind-diag](https://github.com/chainguard-dev/actions) and [fgrosse/go-coverage-report](https://github.com/fgrosse/go-coverage-report).


Updates `step-security/harden-runner` from 2.21.1 to 2.22.0
- [Release notes](https://github.com/step-security/harden-runner/releases)
- [Commits](step-security/harden-runner@e14015d...351661c)

Updates `chainguard-dev/actions/kind-diag` from 1.6.37 to 1.6.40
- [Release notes](https://github.com/chainguard-dev/actions/releases)
- [Commits](chainguard-dev/actions@805da2e...84b1be4)

Updates `fgrosse/go-coverage-report` from 1.4.0 to 1.5.0
- [Release notes](https://github.com/fgrosse/go-coverage-report/releases)
- [Changelog](https://github.com/fgrosse/go-coverage-report/blob/main/CHANGELOG.md)
- [Commits](fgrosse/go-coverage-report@2eb52af...c4bf7e7)

---
updated-dependencies:
- dependency-name: chainguard-dev/actions/kind-diag
  dependency-version: 1.6.40
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: fgrosse/go-coverage-report
  dependency-version: 1.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: step-security/harden-runner
  dependency-version: 2.22.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump the github-actions group with 3 updates chore(deps): bump the github-actions group across 1 directory with 3 updates Oct 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/github-actions-354d78c9e6 branch from d96b191 to 2951afe Compare October 12, 2026 16:35
@tekton-robot tekton-robot removed the lgtm Indicates that a PR is ready to be merged. label Oct 12, 2026

@jkhelil jkhelil left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/approve

@tekton-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 12, 2026

@jkhelil jkhelil left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 12, 2026
@tekton-robot
tekton-robot merged commit 51c5c85 into main Oct 12, 2026
17 checks passed
@dependabot
dependabot Bot deleted the dependabot/github_actions/github-actions-354d78c9e6 branch October 12, 2026 17:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dependencies Used by dependabot - identifies all PRs created by dependabot kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesnt merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants