Skip to content

chore(ci): bump github/codeql-action from 4 to 4.37.3 - #241

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/github/codeql-action-4.37.3
Closed

chore(ci): bump github/codeql-action from 4 to 4.37.3#241
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/github/codeql-action-4.37.3

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps github/codeql-action from 4 to 4.37.3.

Release notes

Sourced from github/codeql-action's releases.

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

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

... (truncated)

Changelog

Sourced from github/codeql-action's changelog.

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
  • e4fba86 Merge pull request #4031 from github/update-v4.37.3-72f6a9da0
  • fb50ab5 Update changelog for v4.37.3
  • 72f6a9d Merge pull request #4030 from github/mbg/fix/no-proxy
  • 3b5ee58 Use default request options instead of undefined
  • bfb6be4 Merge pull request #4028 from github/mergeback/v4.37.2-to-main-e0647621
  • 526ab84 Rebuild
  • d6217b9 Update changelog and version after v4.37.2
  • e064762 Merge pull request #4027 from github/update-v4.37.2-385bcdc5a
  • e0faed8 Add a couple of change notes
  • 73aad0e Update changelog for v4.37.2
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github/codeql-action](https://github.com/github/codeql-action) from 4 to 4.37.3.
- [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.3)

---
updated-dependencies:
- dependency-name: github/codeql-action
  dependency-version: 4.37.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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 Aug 1, 2026
@dependabot
dependabot Bot requested a review from thiagoluga as a code owner August 1, 2026 04:55
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Aug 1, 2026
@sonarqubecloud

sonarqubecloud Bot commented Aug 1, 2026

Copy link
Copy Markdown

@sonarqubecloud

sonarqubecloud Bot commented Aug 1, 2026

Copy link
Copy Markdown

@dependabot @github

dependabot Bot commented on behalf of github Aug 4, 2026

Copy link
Copy Markdown
Contributor Author

Looks like github/codeql-action is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Aug 4, 2026
@dependabot
dependabot Bot deleted the dependabot/github_actions/github/codeql-action-4.37.3 branch August 4, 2026 18:57
thiagoluga added a commit that referenced this pull request Aug 5, 2026
…n lockstep (#266)

* chore(deps): bump the safe dependency lot, with the Hangfire family in lockstep

All eleven Dependabot PRs (#241-#251) were closed unmerged, so the bumps are redone here
as one verified change. This is the lot where the new version is a patch or minor within
the same major; the major jumps (Npgsql 9->10, Microsoft.Data.Sqlite 9->10,
Microsoft.Data.SqlClient 5->7, TestHost 8->10, Aspire 9.5->13.4) are deliberately left
out and assessed separately.

Hangfire.Core, Hangfire.SqlServer and Hangfire.AspNetCore move together to 1.8.24.
Hangfire.NetCore arrives transitively and pins Hangfire.Core to an exact version, so
bumping any one member alone fails restore with NU1608 — which is why #246 and #247 were
red and could never have gone green on their own. dependabot.yml now groups Hangfire* so
the family only ever travels as a unit.

Microsoft.AspNetCore.TestHost goes to 8.0.29 rather than the available 10.0.10: the test
projects target net8.0, so staying in the 8.x servicing line is the bump that belongs
here.

DocumentFormat.OpenXml 3.1.1 -> 3.5.1 made WorkbookPart.Workbook nullable, which
TreatWarningsAsErrors turned into a build failure in XlsxRowReader. It is now checked
rather than assumed; the existing "contains no worksheets" error covers that case.

Verified after a --no-incremental rebuild: Core 303, AspNetCore 159, UI (bUnit 2.9) 245,
WebUi E2E (Playwright 1.61) 24 passed / 0 skipped with NEOREPORTS_REQUIRE_BROWSER=1,
Jobs 34, Sources.Xlsx 32, Formats.Xlsx 7, Formats.Csv 5, Destinations.S3 3,
Destinations.Local 14 — 0 failures.

* chore(deps): use an explicit type on the OpenXml nullability guard

Sonar's new-code maintainability gate is a debt ratio, and this PR changes exactly three
lines of C#, so a single 'use explicit type instead of var' on one of them was enough to
take the rating to 3. Sheet[]? is also the clearer read next to the null-conditional
chain that produces it.

* fix(sources): validate XlsxRowReader's arguments before the iterator starts

`ReadRows` contains `yield`, so none of its body — including
`ArgumentNullException.ThrowIfNull(stream)` — executed until the caller's first
MoveNext. A null stream therefore surfaced from inside the enumeration, with a stack that
no longer pointed at the call that passed it. Splitting the eager wrapper from the
iterator makes the check fire where the mistake was made.

This is what SonarCloud's new-code maintainability gate flagged on the dependency-bump
PR. The line is pre-existing (63deea1, 2026-07-17) and Sonar counts it as new because
the master baseline has been broken since the 50k-LOC free-tier cap hit on 2026-07-12 —
but the finding itself is real, and the file already had to change here for the OpenXml
nullability guard, so it is fixed rather than worked around.

No test: XlsxRowReader is internal with no InternalsVisibleTo, and the public surface
takes a file path or S3 config rather than a Stream, so the null path is not reachable
from outside. The existing 32 tests pass unchanged, which is what confirms the split did
not alter enumeration semantics.
thiagoluga added a commit that referenced this pull request Aug 5, 2026
…running one (#272)

The last item from the closed Dependabot set (#241-#251), held out of #266 and #267 because
9.5.2 -> 13.4.6 crosses four majors and reads like a framework migration.

It is not one. All six AppHosts compile clean on net8.0 with no source changes, no NU
warnings and no deprecation warnings: every API the samples use — AddPostgres,
WithDataVolume, AddDatabase, AddProject<>, WithReference, WaitFor,
WithExternalHttpEndpoints — survived intact.

A clean build proves nothing about an orchestrator, so sample 10 was actually run, both
ways the docs offer: `dotnet run --project .../AppHost` and the new `aspire run` CLI. Both
bring the Postgres container up (~10-25s) and connect it to the session network. The
documented workflow is unchanged; the CLI is an addition, not a replacement.

Two real findings from running it:

- The default PostgreSQL image moved from 17.6 to 18.3 with the Aspire version. Sample 10's
  header comment asserted "postgres:17", which was now false; it no longer names a tag it
  does not control. The READMEs' `docker run ... postgres:17` lines are untouched — those
  describe running Postgres yourself as an alternative to Aspire, and remain accurate.
- `aspire run` writes an `aspire.config.json` pinned to whichever AppHost ran last. With six
  in this repo, committing it would tie everyone to one sample, so it is gitignored.

Full solution rebuilt with --no-incremental; Core 303, Jobs 39, AspNetCore 159, UI 245.
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