Skip to content

ci: bump github/codeql-action from 4 to 4.37.4 in the all-ci-actions group across 1 directory - #95

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/all-ci-actions-83bd6e4a5a
Closed

ci: bump github/codeql-action from 4 to 4.37.4 in the all-ci-actions group across 1 directory#95
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/all-ci-actions-83bd6e4a5a

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor

Bumps the all-ci-actions group with 1 update in the / directory: github/codeql-action.

Updates github/codeql-action from 4 to 4.37.4

Release notes

Sourced from github/codeql-action's releases.

v4.37.4

  • This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
  • Update default CodeQL bundle version to 2.26.2. #4051

v4.37.3

No user facing changes.

v4.37.2

  • The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
  • The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

v4.37.1

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
  • Update default CodeQL bundle version to 2.26.1. #4019

v4.37.0

  • Update default CodeQL bundle version to 2.26.0. #3995
  • In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

v4.36.3

No user facing changes.

v4.36.2

  • Cache CodeQL CLI version information across Actions steps. #3943
  • Reduce requests while waiting for analysis processing by using exponential backoff when polling SARIF processing status. #3937
  • Update default CodeQL bundle version to 2.25.6. #3948

v4.36.1

No user facing changes.

v4.36.0

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.19.4. #3894
  • Add support for SHA-256 Git object IDs. #3893
  • Update default CodeQL bundle version to 2.25.5. #3926

v4.35.5

  • We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #3899
  • For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #3791
  • If multiple inputs are provided for the GitHub-internal analysis-kinds input, only code-scanning will be enabled. The analysis-kinds input is experimental, for GitHub-internal use only, and may change without notice at any time. #3892
  • Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #3880

v4.35.4

  • Update default CodeQL bundle version to 2.25.4. #3881

v4.35.3

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.19.3 and earlier. These versions of CodeQL were discontinued on 9 April 2026 alongside GitHub Enterprise Server 3.15, and will be unsupported by the next minor release of the CodeQL Action. #3837
  • Configurations for private registries that use Cloudsmith or GCP OIDC are now accepted. #3850
  • Best-effort connection tests for private registries now use GET requests instead of HEAD for better compatibility with various registry implementations. For NuGet feeds, the test is now always performed against the service index. #3853
  • Fixed a bug where two diagnostics produced within the same millisecond could overwrite each other on disk, causing one of them to be lost. #3852
  • Update default CodeQL bundle version to 2.25.3. #3865

... (truncated)

Changelog

Sourced from github/codeql-action's changelog.

4.37.4 - 29 Jul 2026

  • This version of the CodeQL Action adds support for the tools input for the codeql-action/init step to be specified using a github-codeql-tools repository property. This feature will gradually be rolled out following the release of this version. Once rolled out, this allows for the CodeQL CLI version that is used in GitHub-managed workflows, such as Default Setup, to be set to a custom value. For example, customers who run into issues with rate limits when a new CodeQL CLI version is released can set the value to toolcache to always use the CodeQL CLI version that is available in the runner toolcache. For Advanced Setup workflows, the value provided for tools in the workflow definition always takes precedence unless the value of the repository property starts with !. #4037
  • Update default CodeQL bundle version to 2.26.2. #4051

4.37.3 - 22 Jul 2026

No user facing changes.

4.37.2 - 21 Jul 2026

  • The new address format for the config-file input that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, the remote= prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023
  • The CodeQL Action can now make use of configured private registries in Default Setup to retrieve CodeQL configuration files from remote repositories that require authentication. This will allow customers to store their CodeQL configuration in a single repository that can then be referenced by Default Setup workflows in other repositories. We expect to roll this and other, related changes out to everyone in July. #4007

4.37.1 - 16 Jul 2026

  • Upcoming breaking change: Add a deprecation warning for customers using CodeQL version 2.20.6 and earlier. These versions of CodeQL were discontinued on 1 July 2026 alongside GitHub Enterprise Server 3.16, and will be unsupported by the next minor release of the CodeQL Action. #3956
  • Update default CodeQL bundle version to 2.26.1. #4019

4.37.0 - 08 Jul 2026

  • Update default CodeQL bundle version to 2.26.0. #3995
  • In addition to the existing input format, the config-file input for the codeql-action/init step will soon support a new [owner/]repo[@ref][:path] format. All components except the repository name are optional. If omitted, owner defaults to the same owner as the repository the analysis is running for, ref to main, and path to .github/codeql-action.yaml. Support for this format ships in this version of the CodeQL Action, but will only be enabled over the coming weeks. #3973

4.36.3 - 01 Jul 2026

No user facing changes.

Commits
  • 18420e3 Merge pull request #4043 from github/mbg/ts/changelog
  • 7e8d897 Merge pull request #4046 from github/mbg/repo-prop/code-quality
  • 2d4c474 Log !analysisKindSupported case
  • 98c05a1 Fix argument validation in rollback-changelog.ts
  • 8289a49 Ignore repository property for unsupported analysis kinds
  • 2a8731c Move config-file computation after determining the analysisKinds
  • 3434fbb Merge pull request #4044 from github/mbg/ff/promote-toolcache
  • 3013ac0 Promote AllowToolcacheInput feature
  • 74b15aa Install JS deps if needed in post-release-mergeback workflow
  • f00f809 Fix checking keys rather than values
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 3, 2026
deftio added a commit that referenced this pull request Aug 4, 2026
commit 635acf05d86320b74be87224f686585330ceb0cd
Author: deftio <deftio@deftio.com>
Date:   Mon Aug 3 22:25:58 2026 -0700

    v2.1.5 release

commit 43a7cf04f1468ebe958ea586ee9b3949dc4028d6
Author: deftio <deftio@deftio.com>
Date:   Mon Aug 3 22:15:48 2026 -0700

    2.1.5 js artifacts build and ci cleaned up

commit 13c8a5dfbfe8e0c657968c6dce644f8b313852ea
Author: deftio <deftio@deftio.com>
Date:   Mon Aug 3 19:05:23 2026 -0700

    tools: derive the squash subject from the CHANGELOG, confirm it separately

    The merge subject came from the branch name, so a release landed on main
    described by whatever the branch happened to be called -- v2.1.4 was a
    CommonJS packaging fix and would have read "dependabot deps".

    release.js now:
    - derives a subject from the CHANGELOG section for the version being
      released, preferring the first column-0 prose sentence. Indented lines are
      skipped because they are wrapped list items, and HTML comments because
      drift-lint pragmas are HTML comments and were being picked up as summaries.
    - accepts --squash-msg="..." as an override, in both the argv form and the
      npm_config form, since `npm run release --squash-msg=x` (no --) is what
      people type and npm swallows it into the environment.
    - falls back to the branch name only when the CHANGELOG yields nothing.
    - confirms the subject in its own step ([a]ccept/[e]dit/[q]uit) before the
      separate y/n on actually merging, so wording is settled apart from the
      decision to release.
    - writes subject + full CHANGELOG section to .git/SQUASH_MSG and commits with
      -F, so main's history carries the changelog and the body is not mangled by
      shell quoting.
    - prints the derived subject and body size during --dry-run.

    publish.yml sets nullglob: an unmatched glob is passed through literally in
    bash and gh would fail on the nonexistent filename, so a build that stopped
    emitting one asset family would break the release rather than degrade it.

    CHANGELOG dated and given a summary paragraph, which is both the release
    notes body and the source of the derived subject.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit ebf181b955bd0781b61d95086816d8e24ef2278c
Author: deftio <deftio@deftio.com>
Date:   Mon Aug 3 17:41:47 2026 -0700

    tools: start-release leaves a green branch; guard repo URLs

    start-release bumped the version but did not rebuild dist, so every
    test:bundles banner assertion failed until the developer happened to run a
    build -- 58 failures on a branch where nothing had been written yet. It now
    rebuilds and includes dist in the "start vX.Y.Z" commit.

    Added a drift-lint rule for bitwrench repo URLs that do not point at
    github.com/deftio. A fabricated owner (github.com/nicktackes/bitwrench) sat
    in the embedded C headers and the Rust Cargo.toml from 2026-03 until v2.1.0
    removed it. Verified it never reached npm (0 hits in the 2.0.32, 2.1.0 and
    2.1.4 tarballs) and it is absent from main -- but nothing would have caught
    it, and the embedded registries render these URLs on the package page.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit 71a267ee41cdbbd84b503ccd4586440556ced773
Author: deftio <deftio@deftio.com>
Date:   Mon Aug 3 14:50:16 2026 -0700

    chore: hygiene pass + document the data-bw-action removal

    Docs:
    - CHANGELOG gains a v2.1.5 note recording that data-bw-action/data-bw-id
      were removed in v2.1.0 without being called out. Includes the before/after
      migration: markup annotation -> bw_act_* class tokens, which BCCL emits
      automatically (makeButton({action:'save'}) -> bw_act_save).
    - Brief matching notes in agents.md and llms.txt. All three are wrapped in
      drift-lint ignore pragmas, since a migration note has to name the retired
      attribute to be useful.
    - Preserved dev/boilerroom-field-report.md, production feedback from a
      ~5,500 LOC bwserve app, which otherwise only existed on a stray remote
      branch.

    Infra:
    - codeql-action pinned back to @v4 from @v4.37.3. The exact-patch pin made
      dependabot open a PR on every patch release (#95 arrived within a day).
    - publish.yml release assets now include dist/*.cjs, *.cjs.map, *.gz and
      *.d.ts. The glob was dist/*.js, so the v2.1.4 release attached 76 assets
      and zero CommonJS bundles -- the very thing that release existed to fix.
    - publish.yml prefers the curated CHANGELOG section for release notes,
      falling back to --generate-notes when the section is missing.
    - release.js no longer runs test:cli separately; it is part of npm test
      as of v2.1.4.

    Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

commit c8f12e2dba306cf09c9bbf827889d34ca5a84738
Author: deftio <deftio@deftio.com>
Date:   Mon Aug 3 14:45:16 2026 -0700

    start v2.1.5: embedded release
Bumps the all-ci-actions group with 1 update in the / directory: [github/codeql-action](https://github.com/github/codeql-action).


Updates `github/codeql-action` from 4 to 4.37.4
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](github/codeql-action@v4...v4.37.4)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-version: 4.37.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: all-ci-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title ci: bump github/codeql-action from 4.37.3 to 4.37.4 in the all-ci-actions group across 1 directory ci: bump github/codeql-action from 4 to 4.37.4 in the all-ci-actions group across 1 directory Aug 4, 2026
@dependabot
dependabot Bot force-pushed the dependabot/github_actions/all-ci-actions-83bd6e4a5a branch from 845ca18 to e676a53 Compare August 4, 2026 05:54
@deftio

deftio commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Closing: codeql-action is intentionally pinned to the floating @v4 tag, which is GitHub's recommendation and receives patches automatically at run time. An exact pin generates a PR on every patch release with no benefit. Added an ignore rule for github/codeql-action in dependabot.yml so this stops recurring.

@deftio deftio closed this Aug 4, 2026
@dependabot @github

dependabot Bot commented on behalf of github Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@deftio
deftio deleted the dependabot/github_actions/all-ci-actions-83bd6e4a5a branch August 4, 2026 18:27
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.

1 participant