Skip to content

build(deps): bump github/codeql-action from 4 to 4.37.3 in the github group - #917

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-d2809b2831
Closed

build(deps): bump github/codeql-action from 4 to 4.37.3 in the github group#917
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/github-d2809b2831

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 31, 2026

Copy link
Copy Markdown
Contributor

Bumps the github group with 1 update: github/codeql-action.

Updates 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 <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

Bumps the github group with 1 update: [github/codeql-action](https://github.com/github/codeql-action).


Updates `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
  dependency-group: github
...

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 Jul 31, 2026
@dependabot
dependabot Bot requested review from AtomicFS and MDr164 as code owners July 31, 2026 00:13
@dependabot dependabot Bot added the github_actions Pull requests that update GitHub Actions code label Jul 31, 2026
@AtomicFS
AtomicFS enabled auto-merge July 31, 2026 00:13
@github-actions

Copy link
Copy Markdown

MegaLinter analysis: Error

Descriptor Linter Files Fixed Errors Warnings Elapsed time
✅ ACTION actionlint 15 0 0 0.53s
⚠️ ACTION zizmor 15 339 0 36.63s
✅ BASH bash-exec 10 0 0 0.02s
✅ BASH shellcheck 9 0 0 0.09s
✅ BASH shfmt 9 0 0 0.01s
✅ DOCKERFILE hadolint 5 0 0 0.24s
✅ EDITORCONFIG editorconfig-checker 227 0 0 0.15s
✅ GO revive 31 0 0 37.72s
✅ JSON jsonlint 14 0 0 1.52s
✅ JSON prettier 14 0 0 3.16s
✅ JSON v8r 14 0 0 5.96s
✅ MARKDOWN markdownlint 32 0 0 2.75s
✅ PYTHON black 20 0 0 2.18s
✅ PYTHON flake8 20 0 0 1.36s
✅ PYTHON isort 20 0 0 0.3s
✅ PYTHON mypy 20 0 0 10.91s
✅ PYTHON pylint 20 0 0 8.45s
✅ PYTHON pyright 20 0 0 0.98s
✅ PYTHON ruff 20 0 0 0.04s
✅ REPOSITORY betterleaks yes no no 0.85s
✅ REPOSITORY checkov yes no no 25.62s
✅ REPOSITORY gitleaks yes no no 7.91s
✅ REPOSITORY git_diff yes no no 0.02s
✅ REPOSITORY grype yes no no 104.58s
❌ REPOSITORY osv-scanner yes 6 no 6.68s
✅ REPOSITORY secretlint yes no no 1.26s
✅ REPOSITORY syft yes no no 12.47s
❌ REPOSITORY trivy yes 1 no 16.21s
✅ REPOSITORY trivy-sbom yes no no 1.77s
✅ REPOSITORY trufflehog yes no no 11.44s
✅ SPELL cspell 227 0 0 5.24s
✅ YAML prettier 35 0 0 2.78s
✅ YAML v8r 35 0 0 14.72s
✅ YAML yamllint 35 0 0 2.84s

Detailed Issues

❌ REPOSITORY / osv-scanner - 6 errors
Scanning dir .
Starting filesystem walk for root: /
Scanned .dagger-ci/daggerci/requirements.txt file and found 9 packages
Scanned cmd/firmware-action/go.mod file and found 59 packages
End status: 76 dirs visited, 336 inodes visited, 2 Extract calls, 8.362209ms elapsed, 8.362419ms wall time
Failed to run code analysis (govulncheck) on 'cmd/firmware-action/go.mod' because govulncheck: loading packages: err: exit status 1: stderr: go: go.mod requires go >= 1.26.5 (running go 1.26.3; GOTOOLCHAIN=local)

(the Go toolchain is required)

Total 3 packages affected by 7 known vulnerabilities (0 Critical, 1 High, 5 Medium, 0 Low, 1 Unknown) from 2 ecosystems.
6 vulnerabilities can be fixed.

+-------------------------------------+------+-----------+---------------------+---------+---------------+--------------------------------------+
| OSV URL                             | CVSS | ECOSYSTEM | PACKAGE             | VERSION | FIXED VERSION | SOURCE                               |
+-------------------------------------+------+-----------+---------------------+---------+---------------+--------------------------------------+
| https://osv.dev/GO-2026-5932        |      | Go        | golang.org/x/crypto | 0.54.0  | --            | cmd/firmware-action/go.mod           |
| https://osv.dev/PYSEC-2026-215      | 6.9  | PyPI      | idna                | 3.9.0   | 3.15          | .dagger-ci/daggerci/requirements.txt |
| https://osv.dev/GHSA-65pc-fj4g-8rjx |      |           |                     |         |               |                                      |
| https://osv.dev/PYSEC-2018-28       | 7.5  | PyPI      | requests            | 2.9.2   | 2.20.0        | .dagger-ci/daggerci/requirements.txt |
| https://osv.dev/GHSA-x84v-xcm2-53pg |      |           |                     |         |               |                                      |
| https://osv.dev/PYSEC-2023-74       | 6.1  | PyPI      | requests            | 2.9.2   | 2.31.0        | .dagger-ci/daggerci/requirements.txt |
| https://osv.dev/GHSA-j8r2-6x86-q33q |      |           |                     |         |               |                                      |
| https://osv.dev/PYSEC-2026-1872     | 5.3  | PyPI      | requests            | 2.9.2   | 2.32.4        | .dagger-ci/daggerci/requirements.txt |
| https://osv.dev/GHSA-9hjg-9r4m-mvj7 |      |           |                     |         |               |                                      |
| https://osv.dev/PYSEC-2026-1873     | 5.6  | PyPI      | requests            | 2.9.2   | 2.32.0        | .dagger-ci/daggerci/requirements.txt |
| https://osv.dev/GHSA-9wx4-h78v-vm56 |      |           |                     |         |               |                                      |
| https://osv.dev/PYSEC-2026-2275     | 5.5  | PyPI      | requests            | 2.9.2   | 2.33.0        | .dagger-ci/daggerci/requirements.txt |
| https://osv.dev/GHSA-gc5v-m9x4-r6x2 |      |           |                     |         |               |                                      |
+-------------------------------------+------+-----------+---------------------+---------+---------------+--------------------------------------+
❌ REPOSITORY / trivy - 1 error
2026-07-31T00:16:02Z	INFO	Loaded	file_path=".trivy.yaml"
2026-07-31T00:16:02Z	INFO	[vulndb] Need to update DB
2026-07-31T00:16:02Z	INFO	[vulndb] Downloading vulnerability DB...
2026-07-31T00:16:02Z	INFO	[vulndb] Downloading artifact...	repo="mirror.gcr.io/aquasec/trivy-db:2"
1.60 MiB / 103.10 MiB [>_____________________________________________________________] 1.56% ? p/s ?18.64 MiB / 103.10 MiB [---------->_________________________________________________] 18.08% ? p/s ?43.42 MiB / 103.10 MiB [------------------------->__________________________________] 42.11% ? p/s ?65.90 MiB / 103.10 MiB [----------------------------->________________] 63.92% 107.09 MiB p/s ETA 0s92.59 MiB / 103.10 MiB [----------------------------------------->____] 89.80% 107.09 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [------------------------------------------->] 100.00% 107.09 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [------------------------------------------->] 100.00% 104.18 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [------------------------------------------->] 100.00% 104.18 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [------------------------------------------->] 100.00% 104.18 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 97.46 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 97.46 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 97.46 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 91.17 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 91.17 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 91.17 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 85.29 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 85.29 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 85.29 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 79.79 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 79.79 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 79.79 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 74.64 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 74.64 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 74.64 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 69.83 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 69.83 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 69.83 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 65.32 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 65.32 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 65.32 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 61.11 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 61.11 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 61.11 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 57.16 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-------------------------------------------->] 100.00% 57.16 MiB p/s ETA 0s103.10 MiB / 103.10 MiB [-----------------------------------------------] 100.00% 14.88 MiB p/s 7.1s2026-07-31T00:16:11Z	INFO	[vulndb] Artifact successfully downloaded	repo="mirror.gcr.io/aquasec/trivy-db:2"
2026-07-31T00:16:11Z	INFO	[vuln] Vulnerability scanning is enabled
2026-07-31T00:16:11Z	INFO	[misconfig] Misconfiguration scanning is enabled
2026-07-31T00:16:11Z	INFO	[checks-client] Need to update the checks bundle
2026-07-31T00:16:11Z	INFO	[checks-client] Downloading the checks bundle...
234.65 KiB / 234.65 KiB [--------------------------------------------------------->] 100.00% ? p/s ?234.65 KiB / 234.65 KiB [--------------------------------------------------------->] 100.00% ? p/s ?234.65 KiB / 234.65 KiB [--------------------------------------------------------->] 100.00% ? p/s ?234.65 KiB / 234.65 KiB [---------------------------------------------] 100.00% 485.72 KiB p/s 700ms2026-07-31T00:16:18Z	INFO	Number of language-specific files	num=1
2026-07-31T00:16:18Z	INFO	[gomod] Detecting vulnerabilities...
2026-07-31T00:16:18Z	INFO	Detected config files	num=5
2026-07-31T00:16:18Z	WARN	Using severities from other vendors for some vulnerabilities. Read https://trivy.dev/docs/v0.71/guide/scanner/vulnerability#severity-selection for details.

Report Summary

┌────────────────────────────┬────────────┬─────────────────┬───────────────────┐
│           Target           │    Type    │ Vulnerabilities │ Misconfigurations │
├────────────────────────────┼────────────┼─────────────────┼───────────────────┤
│ cmd/firmware-action/go.mod │   gomod    │        1        │         -         │
├────────────────────────────┼────────────┼─────────────────┼───────────────────┤
│ docker/coreboot/Dockerfile │ dockerfile │        -        │         0         │
├────────────────────────────┼────────────┼─────────────────┼───────────────────┤
│ docker/edk2/Dockerfile     │ dockerfile │        -        │         0         │
├────────────────────────────┼────────────┼─────────────────┼───────────────────┤
│ docker/linux/Dockerfile    │ dockerfile │        -        │         0         │
├────────────────────────────┼────────────┼─────────────────┼───────────────────┤
│ docker/uboot/Dockerfile    │ dockerfile │        -        │         0         │
├────────────────────────────┼────────────┼─────────────────┼───────────────────┤
│ docker/uroot/Dockerfile    │ dockerfile │        -        │         0         │
└────────────────────────────┴────────────┴─────────────────┴───────────────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)


For OSS Maintainers: VEX Notice
--------------------------------
If you're an OSS maintainer and Trivy has detected vulnerabilities in your project that you believe are not actually exploitable, consider issuing a VEX (Vulnerability Exploitability eXchange) statement.
VEX allows you to communicate the actual status of vulnerabilities in your project, improving security transparency and reducing false positives for your users.
Learn more and start using VEX: https://trivy.dev/docs/v0.71/guide/supply-chain/vex/repo#publishing-vex-documents

To disable this notice, set the TRIVY_DISABLE_VEX_NOTICE environment variable.


cmd/firmware-action/go.mod (gomod)
==================================
Total: 1 (UNKNOWN: 1, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

┌─────────────────────┬───────────────┬──────────┬──────────┬───────────────────┬───────────────┬──────────────────────────────────────────────────────────┐
│       Library       │ Vulnerability │ Severity │  Status  │ Installed Version │ Fixed Version │                          Title                           │
├─────────────────────┼───────────────┼──────────┼──────────┼───────────────────┼───────────────┼──────────────────────────────────────────────────────────┤
│ golang.org/x/crypto │ GO-2026-5932  │ UNKNOWN  │ affected │ v0.54.0           │               │ The golang.org/x/crypto/openpgp package is unmaintained, │
│                     │               │          │          │                   │               │ unsafe by design, and has known security...              │
└─────────────────────┴───────────────┴──────────┴──────────┴───────────────────┴───────────────┴──────────────────────────────────────────────────────────┘

📣 Notices:
  - Version 0.72.0 of Trivy is now available, current version is 0.71.2

To suppress version checks, run Trivy scans with the --skip-version-check flag
⚠️ ACTION / zizmor - 339 errors
uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/lint.yml:54:15
   |
54 |         uses: oxsecurity/megalinter/flavors/cupcake@v9
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/lint.yml:64:15
   |
64 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/lint.yml:66:15
   |
66 |         uses: actions/setup-go@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/lint.yml:71:15
   |
71 |         uses: golangci/golangci-lint-action@v9
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/lint.yml:80:15
   |
80 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/lint.yml:82:15
   |
82 |         uses: goreleaser/goreleaser-action@v7
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

help[artipacked]: credential persistence through GitHub Actions artifacts
  --> .github/workflows/pytest.yml:41:9
   |
41 |         - name: Checkout
   |  _________^
42 | |         uses: actions/checkout@v7
43 | |         with:
44 | |           fetch-depth: 0
   | |________________________^ does not set persist-credentials: false
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#artipacked

help[artipacked]: credential persistence through GitHub Actions artifacts
  --> .github/workflows/pytest.yml:65:9
   |
65 |         - name: Checkout
   |  _________^
66 | |         uses: actions/checkout@v7
   | |_________________________________^ does not set persist-credentials: false
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#artipacked

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/pytest.yml:27:15
   |
27 |         uses: re-actors/alls-green@release/v1
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/pytest.yml:42:15
   |
42 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/pytest.yml:45:15
   |
45 |       - uses: dorny/paths-filter@v4
   |               ^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/pytest.yml:60:15
   |
60 |         uses: arduino/setup-task@v3
   |               ^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/pytest.yml:62:15
   |
62 |         uses: actions/setup-python@v7
   |               ^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/pytest.yml:66:15
   |
66 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

help[artipacked]: credential persistence through GitHub Actions artifacts
  --> .github/workflows/release-prepare.yml:19:9
   |
19 |         - name: Checkout
   |  _________^
20 | |         uses: actions/checkout@v7
21 | |         with:
22 | |           fetch-depth: 0
...  |
25 | |       # Automatically determinate the next release version from Conventional Commits since the latest tag
   | |_________________________________________________________________________________________________________^ does not set persist-credentials: false
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#artipacked

info[template-injection]: code injection via template expansion
  --> .github/workflows/release-prepare.yml:37:59
   |
36 |         run: |
   |         --- this run block
37 |           sed -i -E "s/default: 'v[0-9\.]+'/default: '${{ steps.semver.outputs.next }}'/g" action.yml
   |                                                           ^^^^^^^^^^^^^^^^^^^^^^^^^ may expand into attacker-controllable code
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#template-injection

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release-prepare.yml:20:15
   |
20 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release-prepare.yml:28:15
   |
28 |         uses: ietf-tools/semver-action@v1
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release-prepare.yml:50:15
   |
50 |         uses: peter-evans/create-pull-request@v8
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

help[artipacked]: credential persistence through GitHub Actions artifacts
  --> .github/workflows/release.yml:28:9
   |
28 |         - name: Checkout code
   |  _________^
29 | |         uses: actions/checkout@v7
30 | |         with:
31 | |           fetch-depth: 0
32 | |           fetch-tags: true
   | |__________________________^ does not set persist-credentials: false
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#artipacked

help[artipacked]: credential persistence through GitHub Actions artifacts
  --> .github/workflows/release.yml:87:9
   |
87 |         - name: Checkout code
   |  _________^
88 | |         uses: actions/checkout@v7
89 | |         with:
90 | |           fetch-depth: 0
91 | |           fetch-tags: true
   | |__________________________^ does not set persist-credentials: false
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#artipacked

info[template-injection]: code injection via template expansion
  --> .github/workflows/release.yml:52:28
   |
51 |         run: |
   |         --- this run block
52 |           NEXT_VERSION=${{ steps.get_version.outputs.version }}
   |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ may expand into attacker-controllable code
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#template-injection

info[template-injection]: code injection via template expansion
   --> .github/workflows/release.yml:108:27
    |
 99 |         uses: actions/github-script@v9
    |         ------------------------------ action accepts arbitrary code
...
102 |           script: |
    |           ------ via this input
...
108 |                 ref: "${{ steps.get_version.outputs.version }}",
    |                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ may expand into attacker-controllable code
    |
    = note: audit confidence → Low
    = help: audit documentation → https://docs.zizmor.sh/audits/#template-injection

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release.yml:29:15
   |
29 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release.yml:34:15
   |
34 |         uses: actions/setup-go@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release.yml:60:15
   |
60 |         uses: goreleaser/goreleaser-action@v7
   |               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release.yml:88:15
   |
88 |         uses: actions/checkout@v7
   |               ^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[unpinned-uses]: unpinned action reference
  --> .github/workflows/release.yml:99:15
   |
99 |         uses: actions/github-script@v9
   |               ^^^^^^^^^^^^^^^^^^^^^^^^ action is not pinned to a hash (required by blanket policy)
   |
   = note: audit confidence → High
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#unpinned-uses

error[cache-poisoning]: runtime artifacts potentially vulnerable to a cache poisoning attack
  --> .github/workflows/release.yml:34:9
   |
34 |         uses: actions/setup-go@v7
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^ enables caching by default
...
60 |         uses: goreleaser/goreleaser-action@v7
   |         ------------------------------------- runtime artifacts usually published here
   |
   = note: audit confidence → Low
   = note: this finding has an auto-fix
   = help: audit documentation → https://docs.zizmor.sh/audits/#cache-poisoning

339 findings (121 suppressed, 1 safe fixes, 156 unsafe fixes): 62 informational, 36 low, 4 medium, 116 high

(Truncated to last 13333 characters out of 106979)

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

  • Documentation: Custom Flavors
  • Command: npx mega-linter-runner@9.6.0 --custom-flavor-setup --custom-flavor-linters PYTHON_PYLINT,PYTHON_BLACK,PYTHON_FLAKE8,PYTHON_ISORT,PYTHON_MYPY,PYTHON_PYRIGHT,PYTHON_RUFF,ACTION_ACTIONLINT,ACTION_ZIZMOR,BASH_EXEC,BASH_SHELLCHECK,BASH_SHFMT,DOCKERFILE_HADOLINT,EDITORCONFIG_EDITORCONFIG_CHECKER,GO_REVIVE,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_BETTERLEAKS,REPOSITORY_GRYPE,REPOSITORY_OSV_SCANNER,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,SPELL_CSPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

MegaLinter is graciously provided by OX Security
Show us your support by starring ⭐ the repository

@dependabot @github

dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

Looks like github/codeql-action is no longer updatable, so this is no longer needed.

@dependabot dependabot Bot closed this Aug 3, 2026
auto-merge was automatically disabled August 3, 2026 00:13

Pull request was closed

@dependabot
dependabot Bot deleted the dependabot/github_actions/github-d2809b2831 branch August 3, 2026 00:13
@AtomicFS

AtomicFS commented Aug 3, 2026

Copy link
Copy Markdown
Collaborator

@dependabot recreate

@dependabot @github

dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

Looks like this PR is closed. If the branch still exists, you can re-open the PR and then use @dependabot rebase or @dependabot recreate. If the branch was deleted, Dependabot will create a new PR on the next scheduled run, or you can trigger an update from the Dependency graph page.

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