Skip to content

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

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-deps-5763307931
Open

chore(deps): bump the github-actions-deps group across 1 directory with 2 updates#144
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-actions-deps-5763307931

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 22, 2026

Copy link
Copy Markdown
Contributor

Bumps the github-actions-deps group with 2 updates in the / directory: actions/cache and codecov/codecov-action.

Updates actions/cache from 4 to 5

Release notes

Sourced from actions/cache's releases.

v5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

If you are using self-hosted runners, ensure they are updated before upgrading.


What's Changed

Full Changelog: actions/cache@v4.3.0...v5.0.0

v4.3.0

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.3.0

v4.2.4

What's Changed

New Contributors

Full Changelog: actions/cache@v4...v4.2.4

v4.2.3

What's Changed

  • Update to use @​actions/cache 4.0.3 package & prepare for new release by @​salmanmkc in actions/cache#1577 (SAS tokens for cache entries are now masked in debug logs)

New Contributors

Full Changelog: actions/cache@v4.2.2...v4.2.3

... (truncated)

Changelog

Sourced from actions/cache's changelog.

Releases

How to prepare a release

[!NOTE]
Relevant for maintainers with write access only.

  1. Switch to a new branch from main.
  2. Run npm test to ensure all tests are passing.
  3. Update the version in https://github.com/actions/cache/blob/main/package.json.
  4. Run npm run build to update the compiled files.
  5. Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.
  6. Run licensed cache to update the license report.
  7. Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.
  8. Commit your changes and push your branch upstream.
  9. Open a pull request against main and get it reviewed and merged.
  10. Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json
    1. Create a new tag with the version number.
    2. Auto generate release notes and update them to match the changes you made in RELEASES.md.
    3. Toggle the set as the latest release option.
    4. Publish the release.
  11. Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml
    1. There should be a workflow run queued with the same version number.
    2. Approve the run to publish the new version and update the major tags for this action.

Changelog

5.0.4

  • Bump minimatch to v3.1.5 (fixes ReDoS via globstar patterns)
  • Bump undici to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)
  • Bump fast-xml-parser to v5.5.6

5.0.3

5.0.2

  • Bump @actions/cache to v5.0.3 #1692

5.0.1

  • Update @azure/storage-blob to ^12.29.1 via @actions/cache@5.0.1 #1685

5.0.0

[!IMPORTANT] actions/cache@v5 runs on the Node.js 24 runtime and requires a minimum Actions Runner version of 2.327.1.

... (truncated)

Commits
  • 27d5ce7 Merge pull request #1747 from actions/yacaovsnc/update-dependency
  • f280785 licensed changes
  • 619aeb1 npm run build generated dist files
  • bcf16c2 Update ts-http-runtime to 0.3.5
  • 6682284 Merge pull request #1738 from actions/prepare-v5.0.4
  • e340396 Update RELEASES
  • 8a67110 Add licenses
  • 1865903 Update dependencies & patch security vulnerabilities
  • 5656298 Merge pull request #1722 from RyPeck/patch-1
  • 4e380d1 Fix cache key in examples.md for bun.lock
  • Additional commits viewable in compare view

Updates codecov/codecov-action from 6.0.0 to 7.0.0

Release notes

Sourced from codecov/codecov-action's releases.

v7.0.0

⚠️ Due to migration issues with keybase, we are unable to update our keys under the codecovsecurity account. We have deleted the account and are using codecovsecops with the original gpg key

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v7.0.0

v6.0.2

This is a copy of the v7.0.0 release to make updates easier

What's Changed

Full Changelog: codecov/codecov-action@v6.0.1...v6.0.2

v6.0.1

What's Changed

Full Changelog: codecov/codecov-action@v6.0.0...v6.0.1

Changelog

Sourced from codecov/codecov-action's changelog.

v5.5.2

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.1..v5.5.2

v5.5.1

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1

v5.5.0

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0

v5.4.3

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.2..v5.4.3

v5.4.2

... (truncated)

Commits

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions dependencies in continuous integration workflows to use latest available versions for improved reliability.

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels May 22, 2026
@CLAassistant

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@codacy-production

codacy-production Bot commented May 22, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@dependabot dependabot Bot force-pushed the dependabot/github_actions/github-actions-deps-5763307931 branch from c55e4f7 to 745ceda Compare May 27, 2026 03:58
@dependabot dependabot Bot force-pushed the dependabot/github_actions/github-actions-deps-5763307931 branch from 745ceda to 7c31693 Compare June 4, 2026 01:16
@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Workflow YAML updates: actions/cache bumped from v4 to v5 in Codacy and Go workflows; codecov/codecov-action updated to v7.0.0 in both Go workflow jobs.

Changes

GitHub Actions Dependency Version Updates

Layer / File(s) Summary
Codacy coverage reporter cache update
.github/workflows/codacy-coverage-reporter.yaml
actions/cache is bumped from v4 to v5 in the cache dependencies step.
Go test workflow action updates
.github/workflows/go.yml
actions/cache is upgraded from v4 to v5 in both unittest and unittest-report jobs' cache steps, and codecov/codecov-action is updated from v6.0.0 to v7.0.0 in both jobs' coverage upload steps.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I’m a rabbit in CI, nibbling logs by moonlight,
Bumped cache to v5 so workflows run light,
Codecov grew to seven, a hop and a cheer,
Tests zip along while I munch on a gear. 🐇✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main changes: it's a dependency bump of GitHub Actions (actions/cache and codecov/codecov-action) across the repository.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/github_actions/github-actions-deps-5763307931

Comment @coderabbitai help to get the list of available commands and usage tips.

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/codacy-coverage-reporter.yaml:
- Line 26: The workflow step "Cache dependencies" is using the mutable tag
`actions/cache@v5`; update that `uses:` entry to pin to the full commit SHA for
the v5 release (replace `actions/cache@v5` with
`actions/cache@<full-commit-sha>`). Locate the commit SHA by opening the
actions/cache repository tags/releases for v5 and copy the full 40-char commit
SHA, then update the workflow entry so the "Cache dependencies" step uses that
SHA; commit the change to ensure the action is immutably pinned.

In @.github/workflows/go.yml:
- Line 99: Replace mutable tag-based GitHub Action refs with immutable commit
SHAs: find the action references like actions/cache@v5,
codecov/codecov-action@v6.0.1 and any other tag refs in the workflow (the
occurrences flagged such as the refs around those symbols) and update them to
use the corresponding full commit SHA from each action's repository (eg
actions/cache@<full-commit-sha>); fetch the exact commit SHAs from the upstream
action repos or GitHub Marketplace, verify compatibility, and commit the updated
refs so every use of those action identifiers is pinned to a specific immutable
SHA.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cdcfb64b-cd91-46d3-b35a-33f7e8e3407f

📥 Commits

Reviewing files that changed from the base of the PR and between 9b825f1 and 7c31693.

📒 Files selected for processing (2)
  • .github/workflows/codacy-coverage-reporter.yaml
  • .github/workflows/go.yml


- name: Cache dependencies
uses: actions/cache@v4
uses: actions/cache@v5

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="actions/cache"
tag="v5"

ref_json="$(curl -fsSL "https://api.github.com/repos/${repo}/git/ref/tags/${tag}")"
obj_type="$(jq -r '.object.type' <<<"$ref_json")"
obj_sha="$(jq -r '.object.sha' <<<"$ref_json")"

if [ "$obj_type" = "tag" ]; then
  commit_sha="$(curl -fsSL "https://api.github.com/repos/${repo}/git/tags/${obj_sha}" | jq -r '.object.sha')"
else
  commit_sha="$obj_sha"
fi

printf '%s@%s -> %s\n' "$repo" "$tag" "$commit_sha"

Repository: kubeservice-stack/common

Length of output: 118


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Show the relevant workflow lines around the referenced line
sed -n '1,120p' .github/workflows/codacy-coverage-reporter.yaml | nl -ba | sed -n '1,120p'

# Extract any actions/cache usage from the workflow
rg -n "uses:\s*actions/cache@" .github/workflows/codacy-coverage-reporter.yaml || true

# Check whether any workflows pin actions/cache to a SHA elsewhere in the repo
rg -n "uses:\s*actions/cache@" .github/workflows || true

Repository: kubeservice-stack/common

Length of output: 111


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== workflow head (for line context) =="
cat -n .github/workflows/codacy-coverage-reporter.yaml | sed -n '1,120p'

echo
echo "== actions/cache usage in this workflow =="
rg -n "uses:\s*actions/cache@" .github/workflows/codacy-coverage-reporter.yaml || true

echo
echo "== actions/cache usage elsewhere in repo (workflows only) =="
rg -n "uses:\s*actions/cache@" .github/workflows || true

Repository: kubeservice-stack/common

Length of output: 1866


🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n "unpinned-uses" . || true
rg -n "pinned.*uses|pin.*uses|hardening for github actions|security hardening|retargeting" .github README* docs* || true

Repository: kubeservice-stack/common

Length of output: 114


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== repo root =="
ls -la

echo
echo "== search: unpinned-uses =="
rg -n "unpinned-uses" . || true

echo
echo "== search: hardening/pinning/retargeting keywords =="
rg -n "unpinned|pinned.*uses|pin.*uses|retarget|tag retarget|security hardening|hardening for github actions|hardening.*actions" . || true

echo
echo "== search: any policy/config files mentioning actions security/hardening =="
fd -e yml -e yaml -e json -e md -e toml -e config . | wc -l >/dev/null
fd -e yml -e yaml -e json -e toml -e md -e config . | rg -n "(policy|security|hardening|action|github|workflow)" || true

Repository: kubeservice-stack/common

Length of output: 1159


🌐 Web query:

GitHub Actions security hardening unpinned-uses policy enforce full-length commit SHA for actions at org repo level

💡 Result:

GitHub provides an organization-level policy to enforce the use of full-length commit SHAs for GitHub Actions [1][2]. This security control helps mitigate supply chain risks by ensuring that workflows execute immutable versions of actions, preventing attacks where malicious code is injected into mutable references like tags or branches [1][3][4]. Policy Configuration To enable this enforcement, organization owners can navigate to Organization Settings > Actions > General > Policies [5]. Within this section, there is a setting labeled "Require actions to be pinned to a full-length commit SHA" [1][6]. When enabled, any workflow that attempts to use an action not pinned to a full-length (40-character) commit SHA will fail [2][5]. Key Considerations for Enforcement: - Scope: This policy applies to direct 'uses' references in workflow files [5]. It is a critical component of a broader security hardening strategy but should be combined with other controls, as it does not inherently verify transitive dependencies (e.g., actions that pull other mutable code at runtime) or automatically apply to reusable workflows in the same manner [4][5]. - Governance and Blocking: GitHub also allows for explicit allow and block lists for actions [2][6]. Administrators can combine these policies by using '!' to block specific actions or versions, and ',!owner/repo@' to control allowed action usage across the organization [6][7]. - Complementary Practices: Because SHA pinning alone does not guarantee that an action's internal dependencies or execution logic are immutable, security experts recommend additional practices such as: - Enabling Dependabot to manage and update SHA-pinned actions [2][3]. - Conducting periodic drift audits to identify when upstream maintainers update tags [5]. - Utilizing additional runtime security tools (e.g., harden-runner) to monitor egress traffic or token exposure [4][5]. - Implementing pre-commit hooks or linting (e.g., actionlint) to catch non-compliant references before they are pushed to the repository [5].

Citations:


Pin actions/cache to a full commit SHA

The workflow step Cache dependencies uses the mutable tag actions/cache@v5 (line 26). Tags can be retargeted; GitHub’s hardening guidance recommends pinning GitHub Actions to full-length commit SHAs (and org policy can enforce this). https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions

        uses: actions/cache@v5
🧰 Tools
🪛 zizmor (1.25.2)

[error] 26-26: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)

(unpinned-uses)


[error] 26-26: runtime artifacts potentially vulnerable to a cache poisoning attack (cache-poisoning): enables caching by default

(cache-poisoning)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/codacy-coverage-reporter.yaml at line 26, The workflow
step "Cache dependencies" is using the mutable tag `actions/cache@v5`; update
that `uses:` entry to pin to the full commit SHA for the v5 release (replace
`actions/cache@v5` with `actions/cache@<full-commit-sha>`). Locate the commit
SHA by opening the actions/cache repository tags/releases for v5 and copy the
full 40-char commit SHA, then update the workflow entry so the "Cache
dependencies" step uses that SHA; commit the change to ensure the action is
immutably pinned.

Comment thread .github/workflows/go.yml

- name: Cache dependencies
uses: actions/cache@v4
uses: actions/cache@v5

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

resolve_tag() {
  local repo="$1"
  local tag="$2"

  local ref_json obj_type obj_sha commit_sha
  ref_json="$(curl -fsSL "https://api.github.com/repos/${repo}/git/ref/tags/${tag}")"
  obj_type="$(jq -r '.object.type' <<<"$ref_json")"
  obj_sha="$(jq -r '.object.sha' <<<"$ref_json")"

  if [ "$obj_type" = "tag" ]; then
    commit_sha="$(curl -fsSL "https://api.github.com/repos/${repo}/git/tags/${obj_sha}" | jq -r '.object.sha')"
  else
    commit_sha="$obj_sha"
  fi

  printf '%s@%s -> %s\n' "$repo" "$tag" "$commit_sha"
}

resolve_tag "actions/cache" "v5"
resolve_tag "codecov/codecov-action" "v6.0.1"

Repository: kubeservice-stack/common

Length of output: 118


Pin GitHub Action references to immutable commit SHAs.

In .github/workflows/go.yml, the workflow uses tag-based action refs at lines 99, 112, 135, and 151 (e.g., actions/cache@v5, codecov/codecov-action@v6.0.1). Tag refs are mutable; pinning to full commit SHAs provides stronger supply-chain hardening. (GitHub security hardening for GitHub Actions)

🧰 Tools
🪛 zizmor (1.25.2)

[error] 99-99: unpinned action reference (unpinned-uses): action is not pinned to a hash (required by blanket policy)

(unpinned-uses)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/go.yml at line 99, Replace mutable tag-based GitHub Action
refs with immutable commit SHAs: find the action references like
actions/cache@v5, codecov/codecov-action@v6.0.1 and any other tag refs in the
workflow (the occurrences flagged such as the refs around those symbols) and
update them to use the corresponding full commit SHA from each action's
repository (eg actions/cache@<full-commit-sha>); fetch the exact commit SHAs
from the upstream action repos or GitHub Marketplace, verify compatibility, and
commit the updated refs so every use of those action identifiers is pinned to a
specific immutable SHA.

…th 2 updates

Bumps the github-actions-deps group with 2 updates in the / directory: [actions/cache](https://github.com/actions/cache) and [codecov/codecov-action](https://github.com/codecov/codecov-action).


Updates `actions/cache` from 4 to 5
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@v4...v5)

Updates `codecov/codecov-action` from 6.0.0 to 7.0.0
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v6.0.0...v7.0.0)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-version: '5'
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: github-actions-deps
- dependency-name: codecov/codecov-action
  dependency-version: 6.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions-deps
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/github_actions/github-actions-deps-5763307931 branch from 7c31693 to 58573ad Compare June 10, 2026 01:33
@sonarqubecloud

Copy link
Copy Markdown

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

🧹 Nitpick comments (1)
.github/workflows/go.yml (1)

151-151: Codecov config inconsistency in unittest-report job (use cover.out)
codecov/codecov-action@v7.0.0 still runs with default coverage file discovery enabled, so the generated cover.out from unittest-report should be picked up even without a with: block. For consistency with the unittest job and to avoid uploading unintended discovered artifacts, add with: files: cover.out (and optionally fail_ci_if_error: false; use disable_search: true if you want only cover.out).

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/go.yml at line 151, The Codecov step in the
unittest-report job is running with default discovery which can pick up
unintended artifacts; update the step that uses codecov/codecov-action@v7.0.0
(the Codecov action invocation in the unittest-report job) to include a with:
block that specifies files: cover.out and optionally fail_ci_if_error: false
(and set disable_search: true if you want to restrict uploading strictly to
cover.out) so only the generated cover.out is uploaded consistently with the
unittest job.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.github/workflows/go.yml:
- Line 151: The Codecov step in the unittest-report job is running with default
discovery which can pick up unintended artifacts; update the step that uses
codecov/codecov-action@v7.0.0 (the Codecov action invocation in the
unittest-report job) to include a with: block that specifies files: cover.out
and optionally fail_ci_if_error: false (and set disable_search: true if you want
to restrict uploading strictly to cover.out) so only the generated cover.out is
uploaded consistently with the unittest job.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8dad0bed-b6f6-40ff-8f93-84d2fa77c181

📥 Commits

Reviewing files that changed from the base of the PR and between 7c31693 and 58573ad.

📒 Files selected for processing (2)
  • .github/workflows/codacy-coverage-reporter.yaml
  • .github/workflows/go.yml

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 size/S

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant