Skip to content

chore(deps): bump github/codeql-action to v4.38.0 and group it - #178

Merged
imran-siddique merged 1 commit into
mainfrom
chore/codeql-action-4.38.0-and-group
Sep 14, 2026
Merged

imran-siddique merged 1 commit into
mainfrom
chore/codeql-action-4.38.0-and-group

Conversation

@imran-siddique

Copy link
Copy Markdown
Member

Two changes that belong together: bump every github/codeql-action pin to v4.38.0 (b96794f015dfd88f77b49b1c93e0fa7110f94c63), and group the action in dependabot.yml so this does not recur.

The bump

init, autobuild and analyze in codeql.yml, upload-sarif in scorecard.yml. All four paths of one release share a SHA, so bumping a single path leaves the siblings at v4.37.9 and CodeQL fails on the mismatch. The three in codeql.yml also edit the same file, so dependabot's per-path PRs could not be merged back to back either.

The group

github/codeql-action* is grouped so the next release arrives as one PR rather than four. Deliberately narrow: other action updates keep their own PRs, because the problem is specific to a dependency that breaks when split.

The same pair landed in agent-manifest, demos, examples and integrations earlier today, and agent-manifest has already produced a single grouped PR on the next release, which is the config working as intended.

Supersedes the four per-path dependabot PRs in this repository, closed against this one.

All four action paths of one codeql-action release share a SHA, so bumping one
path strands the siblings at v4.37.9 and CodeQL fails on the mismatch. The three
in codeql.yml edit the same file, so the per-path PRs also conflict with each
other. Bump all four together, and group github/codeql-action* so dependabot
opens one PR per release.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015QRxFm1Z1kE9iraPspwr7j
@imran-siddique
imran-siddique merged commit 34646dd into main Sep 14, 2026
14 checks passed
@imran-siddique
imran-siddique deleted the chore/codeql-action-4.38.0-and-group branch September 14, 2026 19:18
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.

1 participant