Skip to content

ci(deps): bump 5 GitHub Actions to current SHAs (consolidates Dependabot #78–#82)#84

Merged
tomtom215 merged 2 commits into
mainfrom
claude/duckdb-deps-release-489xb1
Jul 21, 2026
Merged

ci(deps): bump 5 GitHub Actions to current SHAs (consolidates Dependabot #78–#82)#84
tomtom215 merged 2 commits into
mainfrom
claude/duckdb-deps-release-489xb1

Conversation

@tomtom215

Copy link
Copy Markdown
Owner

Summary

Consolidates the five open Dependabot github-actions PRs (#78#82) into a single change on current main. Each Dependabot PR was opened ~5 weeks ago and shows stale failing CI — but the failures are from the base main at that time (a since-fixed target/duckdb-download cache issue, commit 458ec31), not the action bumps: e.g. #82 only touches codeql-action yet its Test/Benchmarks jobs failed, which that action can't affect. Rebased onto the v0.9.0 main, these inert workflow-only SHA swaps pass.

Doing this before the v0.9.0 release so the repo ships with all dependencies (Cargo and Actions) current and no open Dependabot PRs.

Changes

Action From → To Supersedes
github/codeql-action 4.35.4 → 4.36.2 #82
actions/checkout 6.0.2 → 6.0.3 #81
codecov/codecov-action 6.0.0 → 7.0.0 #80
EmbarkStudios/cargo-deny-action 2.0.18 → 2.0.20 #79
taiki-e/install-action 2.77.6 → 2.81.11 #78

Each SHA is taken verbatim from the corresponding Dependabot PR diff, with the # vX.Y.Z pin comment updated to match. 26 checkout occurrences across 6 workflow files, codeql-action ×3 (init/autobuild/analyze), install-action ×2, the rest ×1. No other pins changed.

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Performance improvement (non-breaking change that improves performance)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update
  • CI/CD or tooling change

Testing

Workflow-file-only change — no Rust source touched, so runtime behavior is identical to main (already validated at v0.9.0). Verification done here:

  • All 6 workflow YAML files still parse (yaml.safe_load)
  • Every old pinned SHA replaced; no stale v6.0.2/etc. references remain
  • SHAs match the Dependabot-resolved commits for each target tag
  • Full CI on this PR exercises the bumped actions end-to-end (codeql-action, checkout, cargo-deny-action, install-action; codecov-action runs in the informational, continue-on-error Coverage job)

Documentation

  • README / CLAUDE.md / CHANGELOG / mdBook / PERF.md — n/a (CI tooling only, no user-visible change)

Related Issues

Supersedes #78, #79, #80, #81, #82 — those Dependabot PRs will be closed once this merges.

Notes

codecov/codecov-action is a major bump (6→7); it runs only in the Coverage job, which is continue-on-error: true and excluded from the required CI Gate, so it cannot block the merge even if the v7 interface shifted. After merge I'll close the five superseded Dependabot PRs with a pointer here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KtQVSn8MZwxq6vJkLoS83a


Generated by Claude Code

claude added 2 commits July 21, 2026 12:26
Consolidates the five open Dependabot github-actions PRs onto current main.
Each was opened ~5 weeks ago and shows stale failing CI from a since-fixed
base-main issue (the target/duckdb-download cache handling, commit 458ec31);
the bumps themselves are inert workflow-only changes and pass on the v0.9.0
main. SHAs are taken verbatim from the corresponding Dependabot PR diffs,
with version comments updated to match.

- github/codeql-action          4.35.4 -> 4.36.2  (supersedes #82)
- actions/checkout              6.0.2  -> 6.0.3   (supersedes #81)
- codecov/codecov-action        6.0.0  -> 7.0.0   (supersedes #80)
- EmbarkStudios/cargo-deny-action 2.0.18 -> 2.0.20 (supersedes #79)
- taiki-e/install-action        2.77.6 -> 2.81.11 (supersedes #78)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KtQVSn8MZwxq6vJkLoS83a
The Test (cross-platform), Benchmarks compile, and Coverage jobs link the
DuckDB library, and on cache-hit runs they failed with:

    rust-lld: error: unable to find library -lduckdb
    -L .../target/duckdb-download/<triple>/1.5.4

rust-cache restored the libduckdb-sys build-script fingerprint (so the
build script skips the download) while pruning the actual libduckdb under
target/duckdb-download — the exact stranding the cache-directories comment
warns about. Check/Clippy/Doc type-check without linking, so they were
unaffected; the plain Test job hit a good cache and passed. The poison is
per-job (likely a concurrency-cancelled run saving a partial cache).

Bump the rust-cache prefix-key v0-rust -> v1-rust so every job starts from
a cold key: the fresh libduckdb download repopulates target/duckdb-download
and the new caches are saved intact. Unrelated to the Actions-version bumps
in this PR — those are inert workflow-only changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KtQVSn8MZwxq6vJkLoS83a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants