Skip to content

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

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/github-actions-8cb3c991c1
Open

chore(deps): bump the github-actions group across 1 directory with 4 updates#1643
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/github-actions-8cb3c991c1

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Apr 27, 2026

Bumps the github-actions group with 4 updates in the / directory: astral-sh/setup-uv, actions/cache, github/codeql-action and dependabot/fetch-metadata.

Updates astral-sh/setup-uv from 8.0.0 to 8.1.0

Release notes

Sourced from astral-sh/setup-uv's releases.

v8.1.0 🌈 New input no-project

Changes

This add the a new boolean input no-project. It only makes sense to use in combination with activate-environment: true and will append --no project to the uv venv call. This is for example useful if you have a pyproject.toml file with parts unparseable by uv

🚀 Enhancements

  • Add input no-project in combination with activate-environment @​eifinger (#856)

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates

  • chore(deps): bump release-drafter/release-drafter from 7.1.1 to 7.2.0 @dependabot[bot] (#855)
Commits
  • 0880764 fix: grant contents:write to validate-release job (#860)
  • 717d6ab Add a release-gate step to the release workflow (#859)
  • 5a911eb Draft commitish releases (#858)
  • 080c31e Add action-types.yml to instructions (#857)
  • b3e97d2 Add input no-project in combination with activate-environment (#856)
  • 7dd591d chore(deps): bump release-drafter/release-drafter from 7.1.1 to 7.2.0 (#855)
  • 1541b77 chore: update known checksums for 0.11.7 (#853)
  • cdfb2ee Refactor version resolving (#852)
  • cb84d12 chore: update known checksums for 0.11.6 (#850)
  • 1912cc6 chore: update known checksums for 0.11.5 (#845)
  • Additional commits viewable in compare view

Updates actions/cache from 5.0.4 to 5.0.5

Release notes

Sourced from actions/cache's releases.

v5.0.5

What's Changed

Full Changelog: actions/cache@v5...v5.0.5

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

Updates github/codeql-action from 4.35.1 to 4.35.2

Release notes

Sourced from github/codeql-action's releases.

v4.35.2

  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
  • The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
  • Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
  • Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807
  • Update default CodeQL bundle version to 2.25.2. #3823
Changelog

Sourced from github/codeql-action's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.35.2 - 15 Apr 2026

  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable is deprecated and will be removed in May 2026. If you are affected by this, we recommend disabling TRAP caching by passing the trap-caching: false input to the init Action. #3795
  • The Git version 2.36.0 requirement for improved incremental analysis now only applies to repositories that contain submodules. #3789
  • Python analysis on GHES no longer extracts the standard library, relying instead on models of the standard library. This should result in significantly faster extraction and analysis times, while the effect on alerts should be minimal. #3794
  • Fixed a bug in the validation of OIDC configurations for private registries that was added in CodeQL Action 4.33.0 / 3.33.0. #3807
  • Update default CodeQL bundle version to 2.25.2. #3823

4.35.1 - 27 Mar 2026

4.35.0 - 27 Mar 2026

4.34.1 - 20 Mar 2026

  • Downgrade default CodeQL bundle version to 2.24.3 due to issues with a small percentage of Actions and JavaScript analyses. #3762

4.34.0 - 20 Mar 2026

  • Added an experimental change which disables TRAP caching when improved incremental analysis is enabled, since improved incremental analysis supersedes TRAP caching. This will improve performance and reduce Actions cache usage. We expect to roll this change out to everyone in March. #3569
  • We are rolling out improved incremental analysis to C/C++ analyses that use build mode none. We expect this rollout to be complete by the end of April 2026. #3584
  • Update default CodeQL bundle version to 2.25.0. #3585

4.33.0 - 16 Mar 2026

  • Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562

    To opt out of this change:

    • Repositories owned by an organization: Create a custom repository property with the name github-codeql-file-coverage-on-prs and the type "True/false", then set this property to true in the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using default setup: Switch to an advanced setup workflow and set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
    • User-owned repositories using advanced setup: Set the CODEQL_ACTION_FILE_COVERAGE_ON_PRS environment variable to true in your workflow.
  • Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557

  • The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as github-codeql-disable-overlay that was previously only available on GitHub.com. #3559

  • Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563

  • Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564

  • A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570

4.32.6 - 05 Mar 2026

... (truncated)

Commits
  • 95e58e9 Merge pull request #3824 from github/update-v4.35.2-d2e135a73
  • 6f31bfe Update changelog for v4.35.2
  • d2e135a Merge pull request #3823 from github/update-bundle/codeql-bundle-v2.25.2
  • 60abb65 Add changelog note
  • 5a0a562 Update default bundle to codeql-bundle-v2.25.2
  • 6521697 Merge pull request #3820 from github/dependabot/github_actions/dot-github/wor...
  • 3c45af2 Merge pull request #3821 from github/dependabot/npm_and_yarn/npm-minor-345b93...
  • f1c3393 Rebuild
  • 1024fc4 Rebuild
  • 9dd4cfe Bump the npm-minor group across 1 directory with 6 updates
  • Additional commits viewable in compare view

Updates dependabot/fetch-metadata from 3.0.0 to 3.1.0

Release notes

Sourced from dependabot/fetch-metadata's releases.

v3.1.0

What's Changed

New Contributors

Full Changelog: dependabot/fetch-metadata@v3...v3.1.0

Commits
  • 25dd0e3 v3.1.0 (#692)
  • e073f50 Merge pull request #705 from dependabot/dependabot/npm_and_yarn/hono-4.12.14
  • 0670e16 build(deps-dev): bump hono from 4.12.12 to 4.12.14
  • 7a7fe10 Merge pull request #702 from dependabot/dependabot/npm_and_yarn/dependencies-...
  • 5168191 Updating dist build
  • 23882e1 build(deps): bump @​actions/github in the dependencies group
  • 1072469 Merge pull request #701 from dependabot/dependabot/github_actions/actions/cre...
  • 43f8a00 build(deps): bump actions/create-github-app-token from 3.0.0 to 3.1.1
  • b4d904a Merge pull request #703 from dependabot/dependabot/npm_and_yarn/globals-17.5.0
  • c8046bb build(deps-dev): bump globals from 17.4.0 to 17.5.0
  • Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…updates

Bumps the github-actions group with 4 updates in the / directory: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv), [actions/cache](https://github.com/actions/cache), [github/codeql-action](https://github.com/github/codeql-action) and [dependabot/fetch-metadata](https://github.com/dependabot/fetch-metadata).


Updates `astral-sh/setup-uv` from 8.0.0 to 8.1.0
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@cec2083...0880764)

Updates `actions/cache` from 5.0.4 to 5.0.5
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](actions/cache@6682284...27d5ce7)

Updates `github/codeql-action` from 4.35.1 to 4.35.2
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@c10b806...95e58e9)

Updates `dependabot/fetch-metadata` from 3.0.0 to 3.1.0
- [Release notes](https://github.com/dependabot/fetch-metadata/releases)
- [Commits](dependabot/fetch-metadata@ffa630c...25dd0e3)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 8.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: actions/cache
  dependency-version: 5.0.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: github/codeql-action
  dependency-version: 4.35.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: dependabot/fetch-metadata
  dependency-version: 3.1.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 added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 27, 2026
@blacksmith-sh
Copy link
Copy Markdown

blacksmith-sh Bot commented Apr 27, 2026

Found 2 test failures on Blacksmith runners:

Failures

Test View Logs
TestMultiProjectSetup/test_context_isolation_between_projects View Logs
TestMultiProjectSetup/test_cross_project_tracing View Logs

Fix in Cursor

Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

LGTM — straightforward Dependabot bump of pinned GitHub Actions; the stale # v5.0.4 comment for actions/cache (SHA actually points to v5.0.5) is the only issue and is purely cosmetic.

Extended reasoning...

Overview

This PR is a Dependabot group update that bumps four pinned GitHub Actions across .github/workflows/{ci,codeql,dependabot-merge,release}.yml:

  • astral-sh/setup-uv v8.0.0 → v8.1.0 (4 occurrences)
  • actions/cache v5.0.4 → v5.0.5 (1 occurrence)
  • github/codeql-action/{init,analyze} v4.35.1 → v4.35.2 (2 occurrences)
  • dependabot/fetch-metadata v3.0.0 → v3.1.0 (1 occurrence)

All are mechanical SHA + version-comment swaps; no logic, secrets handling, or workflow trigger conditions are changed.

Security risks

Low. Every action remains pinned to an immutable commit SHA (no floating tags), preserving the supply-chain hardening this repo already enforces. Release notes for the bumped actions are bug fixes / minor enhancements (e.g. actions/cache ts-http-runtime bump, CodeQL bundle 2.25.2 update). Nothing introduces new permissions or alters permissions: blocks.

Level of scrutiny

Low. CI/release infra changes warrant a closer look than typical config tweaks — the release workflow handles PyPI publishing and GitHub releases — but in this PR release.yml only changes the setup-uv SHA/version, with no change to the trusted-publishing flow, secret usage, or release logic. Same for dependabot-merge.yml, where only the fetch-metadata action SHA changed; the auto-merge gating on version-update:semver-patch is untouched.

Other factors

The bug-hunting system surfaced one nit: .github/workflows/ci.yml:49 was given the v5.0.5 SHA for actions/cache but the trailing comment still reads # v5.0.4. That mismatch is purely cosmetic — GitHub Actions resolves the SHA, not the comment — but it is worth fixing for auditability since the rest of the diff updated comments correctly. The inline comment already conveys that to the author. Given the mechanical nature of the diff and the nit-level severity of the only finding, this is well within the approval threshold.

Comment thread .github/workflows/ci.yml
python-version: "3.13"
enable-cache: true # zizmor: ignore[cache-poisoning] CI-only, no artifacts published
- uses: actions/cache@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4 # zizmor: ignore[cache-poisoning]
- uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.4 # zizmor: ignore[cache-poisoning]
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 On line 49 of .github/workflows/ci.yml, the actions/cache SHA was bumped to 27d5ce7f107fe9357f9df03efb73ab90386fccae (which is v5.0.5), but the trailing version comment still reads # v5.0.4. Dependabot normally rewrites these comments — this one was missed, so the SHA→version mapping that humans read to audit pinned actions is misleading. Comment-only nit, no runtime impact; please update the comment to # v5.0.5 to match the rest of the diff.

Extended reasoning...

What the bug is. In .github/workflows/ci.yml line 49, the actions/cache step is updated from SHA 668228422ae6a00e4ad889ee87cd7109ec5666a7 to 27d5ce7f107fe9357f9df03efb73ab90386fccae, but the trailing comment is left unchanged at # v5.0.4. The PR description's actions/cache section explicitly bumps that action from v5.0.4 → v5.0.5, and the actions/cache release notes show 27d5ce7f107fe9357f9df03efb73ab90386fccae as the v5.0.5 release commit ("Merge pull request #1747 from actions/yacaovsnc/update-dependency — Update ts-http-runtime dependency"). So the SHA on line 49 is v5.0.5 but the inline annotation still says v5.0.4.\n\nWhy this is a real (if cosmetic) issue. This repo pins every GitHub Action to an immutable SHA with a trailing # vX.Y.Z comment so reviewers can audit pinned versions at a glance — that is the only reason the comments exist. When Dependabot bumps actions, it rewrites those comments together with the SHA. In this same PR every other action comment was updated correctly: astral-sh/setup-uv v8.0.0 → v8.1.0, github/codeql-action v4.35.1 → v4.35.2, and dependabot/fetch-metadata v3.0.0 → v3.1.0 all have matching SHA + comment changes. Line 49 is the lone outlier where the SHA moved but the comment did not, which is a clear Dependabot oversight rather than intentional pinning.\n\nImpact. No runtime impact — GitHub Actions resolves the SHA, and 27d5ce7f... will correctly run v5.0.5 of actions/cache regardless of what the comment says. The cost is purely auditability: a future reviewer reading actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.4 will believe the pin is at v5.0.4 and may waste time tracing the discrepancy, or fail to notice that v5.0.5 is actually deployed when triaging behavior changes (e.g. the v5.0.5 ts-http-runtime bump).\n\nFix. Change # v5.0.4 to # v5.0.5 on line 49 of .github/workflows/ci.yml. No other change needed.\n\nStep-by-step proof.\n1. Open the diff for .github/workflows/ci.yml line 49: it reads - uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.4 # zizmor: ignore[cache-poisoning]. The @SHA was changed (was 668228422ae6...); the # v5.0.4 comment was not.\n2. Confirm the new SHA's release. The PR description quotes the actions/cache v5.0.5 release notes, which list a single commit: 27d5ce7 — "Merge pull request #1747 from actions/yacaovsnc/update-dependency". That is the commit being pinned.\n3. Confirm the PR's intent. The PR description's header for this action reads "Updates actions/cache from 5.0.4 to 5.0.5", so the target version is unambiguously v5.0.5.\n4. Cross-check against sibling bumps in the same diff: every other action comment matches its SHA's release tag. Only line 49 is mismatched.\n5. Therefore the comment # v5.0.4 on line 49 is stale and should read # v5.0.5.\n\nAll four independent verifiers confirmed this with nit severity. Filing as nit (cosmetic, comment-only).

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants