Skip to content

build(deps): bump the pre-commit-monthly group with 4 updates - #3453

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pre_commit/pre-commit-monthly-f285ef3b8a
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pre_commit/pre-commit-monthly-f285ef3b8a

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 13, 2026

Copy link
Copy Markdown
Contributor

Bumps the pre-commit-monthly group with 4 updates: https://github.com/NVIDIA/security-workflows, https://github.com/astral-sh/ruff-pre-commit, https://github.com/pre-commit/mirrors-clang-format and https://github.com/MarcoGorelli/cython-lint.

Updates https://github.com/NVIDIA/security-workflows from v0.4.0 to 0.5.0

Release notes

Sourced from https://github.com/NVIDIA/security-workflows's releases.

v0.5.0 — Vulnerability and malware scans, GuardWords hook

Three new surfaces. The vulnerability scan (vuln-scan-pulse-oss.yml) runs NVIDIA's Pulse OSS scanner against a disposable copy of the checkout and reports to nSpect over a Charon tunnel. The malware scan (malware-scan-pulse.yml) asks the Pulse Malware Service to scan the run's own commit with ReversingLabs — nothing is checked out, and the target cannot be redirected. The GuardWords pre-commit hook (guardwords-scan-code-scanning) sends the staged diff to NVIDIA's internal code-scanning service and skips for anyone without it, so external contributors are never blocked.

Additive. Existing suite callers need no change: enable-vuln-scan and enable-malware-scan default to false, and both scans' permissions are already inside the suite's permission union. Both scans require a Charon tenant grants the Pulse backends and lists every ref they scan from.

Full notes: CHANGELOG.md

Changelog

Sourced from https://github.com/NVIDIA/security-workflows's changelog.

Changelog

All notable changes to the workflows in this repository will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning. See README.md for the SHA-pinning contract that consumers are expected to follow.

[0.5.0] - 2026-11-03

Additive release: two reusable workflows (vulnerability, malware) and one pre-commit hook (GuardWords). Existing suite callers need no change — enable-vuln-scan and enable-malware-scan default to false, and the scans' permissions (contents: read + id-token: write for the vulnerability scan, id-token: write alone for the malware scan) are already inside the suite's permission union.

Added

  • Vulnerability scan (SCA) reusable workflow — https://github.com/NVIDIA/security-workflows/blob/main/.github/workflows/vuln-scan-pulse-oss.yml. Runs NVIDIA's Pulse OSS scanner against a disposable copy of the checkout and reports to the nSpect backend over a Charon loopback tunnel. Consumers supply no credentials: GitHub OIDC is the only identity the scan presents, and the nvcr.io pull login comes from Vault. The scanner image and the tunnel settings are owned by the workflow, so a caller can substitute neither. pull_request / pull_request_target are rejected. Inputs and prerequisites are in the workflow catalogue; build-environment setup is in the scan guide.
  • Vulnerability scan — scan targeting. nspect_id is optional: left empty the scan runs unregistered, which is the only lane open to a repository with no nSpect registration and is rapid-only. sbom_name selects the registration when the registered branch carries more than one SBOM entry, and inventory_writeback requires it. copy-pr-bot mirrors (refs/heads/pull-request/*) are rapid-only.
  • Vulnerability scan — findings never decide the scanner's exit code. The CLI always runs with --no-fail and failure_policy is applied to the validated report, so a non-zero exit is always a failed scan rather than a finding.
  • Vulnerability scan — optional build controls, off by default and forwarded by the suite: prepared Python wheels, typed Detect properties, and redacted console/debug logging. Snippet scanning and snippet-match export are deferred to a follow-up release.
  • Malware scan reusable workflow — https://github.com/NVIDIA/security-workflows/blob/main/.github/workflows/malware-scan-pulse.yml. Asks the Pulse Malware Service to scan the calling run's own commit with ReversingLabs over the production Charon loopback tunnel. The service fetches the commit itself, so nothing is checked out and the scan cannot be pointed at another repository or commit. failure_policy is strict (default — SUSPICIOUS blocks too) or malicious-only; a MALICIOUS verdict, and any scan that ends without one, block under both. pull_request / pull_request_target are rejected. Prerequisites are in the workflow catalogue.
  • Security suite — enable-vuln-scan and enable-malware-scan, each with its own vuln-* / malware-* inputs, plus an unprefixed nspect-id: an nSpect ID identifies the repository rather than one scan, so every scan reporting to nSpect reads the same one. The malware scan requires it — enabling that scan without it fails the preflight.
  • GuardWords (pre-commit) — guardwords-scan-code-scanning sends the staged diff to NVIDIA's internal code-scanning service and blocks the commit on blocking findings. It is for NVIDIA employees only: where the client or service is unavailable it skips with a notice, so external contributors are never blocked. https://github.com/NVIDIA/security-workflows/blob/main/hooks/guardwords/install_client.py sets up the client in one command. See the GuardWords hook guide.
  • Pre-commit hook catalogue — https://github.com/NVIDIA/security-workflows/blob/main/hooks/README.md, the hook-side counterpart to the workflow catalogue.
  • CI — contract tests covering every gate in both new workflows, plus live integration runs. The vulnerability scan's integration is ungated, so its Vault and Charon prerequisites stay hard requirements.
  • Third-party notices — teleport-actions/setup and actions/upload-artifact, both pinned by SHA.

Changed

  • Security suite — the preflight reports every missing companion input in one run rather than exiting on the first.
  • Pin policy — the recommended pre-commit rev: pin is now the 40-character commit SHA with the release tag as a # frozen: comment, the form pre-commit autoupdate --freeze writes, matching the SHA pin already required for reusable workflows. Existing release-tag pins keep working; switch with pre-commit autoupdate --freeze at the next refresh. See Pin policy per surface.

Known limitations

  • Charon is a prerequisite for both scans. The tunnel authorizes per repository and per ref, so a consuming tenant must grant the Pulse backends and list every ref it scans from. Gating pull requests needs the pull-request/* mirrors listed; without them both scans are post-merge and scheduled gates. The malware scan-submission route is not granted by default and needs platform approval.
  • Scanner upgrades ship as workflow releases. Both scanners are pinned by digest — Pulse OSS 0.5.3-charon.11, Pulse malware 1.3.0 — so a new scanner reaches callers only through a new release of this repository.
  • Vulnerability scan — SARIF publication is a follow-up. Findings land in the job summary and an optional artifact, not the Security tab.
  • Vulnerability scan — build: true runs the repository's build inside the scanner. Maven and Go graphs resolve only through a build. Prefer it on post-merge and scheduled runs; see the workflow catalogue before enabling it on pull-request mirrors.
  • Vulnerability scan — Persistent and write-back scans are pilot-only. Inventory write-back with sbom_name against a branch with several SBOM entries has not been validated end-to-end.
  • Malware scan — Detection is not yet proven end-to-end. CI asserts transport and a CLEAN verdict; proving a blocking verdict needs a ProdSec-approved detection sample, and the contract tests cover how one is handled.
  • GuardWords — No CI counterpart. The hook is the only surface and it skips wherever the client or service is unavailable, so a commit that skipped is not re-scanned before merge.

[0.4.0] - 2026-08-19

Additive release. Callers passing languages: '["actions","python"]' need no change; the declared permissions: are unchanged, and the analyze job keeps the name CodeQL (<language>) so required status checks continue to match.

Added

  • SAST (CodeQL) — build mode is resolved per language instead of one value applied to every matrix leg, so sets with conflicting requirements work in a single call. '["go","rust"]' could not previously be expressed (go needs autobuild, rust supports only none). Substitutions are reported as job-log notices and the resolved matrix is written to the job summary.
  • SAST (CodeQL) — languages entries may be objects carrying a per-language build-mode or runs-on: '[{"language":"swift","runs-on":"macos-14"},"rust"]'. Per-entry runs-on makes swift usable, as it requires a macOS runner.
  • SAST (CodeQL) — a resolve job validates the language set before any analysis starts, rejecting unknown languages, manual mode, unsupported explicit modes, duplicate languages, malformed JSON, and empty lists. New resolve-runs-on input (default ubuntu-latest); the suite passes suite-runs-on through to it.
  • Documentation — the workflow catalogue now lists the accepted languages values with per-language buildless support, plus the two coverage gaps: no shell analyzer (use shellcheck) and no CUDA analyzer (c-cpp skips .cu / .cuh).

Changed

... (truncated)

Commits
  • 0659a2e docs(release): stamp v0.5.0 (#30)
  • e8b6246 feat(vuln): add prepared runtimes and scan controls (#27)
  • 7914e46 fix(vuln): make scanner-written files in the scan copy removable (#29)
  • d48e1b9 fix(vuln): scan a disposable copy instead of a read-only checkout (#26)
  • c4e36e1 feat(pre-commit): add guardwords-scan-code-scanning hook. (#24)
  • 01c3188 fix(vuln): pin the Pulse OSS scanner to 0.5.3-charon.11 (#25)
  • 3aec21e feat(malware): add Pulse source-code malware scan to the security suite. (#23)
  • 815b524 feat(vuln): add Pulse OSS vulnerability scan to the security suite. (#22)
  • See full diff in compare view

Updates https://github.com/astral-sh/ruff-pre-commit from v0.17.3 to 0.17.4

Release notes

Sourced from https://github.com/astral-sh/ruff-pre-commit's releases.

v0.17.4

See: https://github.com/astral-sh/ruff/releases/tag/0.17.4

Commits
  • c0f278f Mirror: 0.17.4
  • 0c0cb54 Bump astral-sh/setup-uv from 10.3.0 to 10.3.2 in the github-actions group (#191)
  • 1f5d5de Remove redundant types_or in pyproject.toml example (#190)
  • See full diff in compare view

Updates https://github.com/pre-commit/mirrors-clang-format from v23.1.3 to 23.1.5

Commits

Updates https://github.com/MarcoGorelli/cython-lint from v0.22.0 to 0.22.1

Release notes

Sourced from https://github.com/MarcoGorelli/cython-lint's releases.

v0.22.1

  • Dropped support for Python 3.10, which reached end of life in October 2026. cython-lint now needs Python 3.11 or later, and the tomli dependency has been removed. (#204)
  • cython-lint --version now reports the installed version. It had been stuck at 0.16.0 since that release (#194, thanks @​oscarbenjamin for reporting). The version now comes from the package metadata, so it can't drift again. (#204)
  • Updated ruff to 0.16.10 in pre-commit. (#200)
Commits
  • 7b81144 Bump version to 0.22.1
  • 1b5ea96 Merge pull request #204 from MarcoGorelli/fix-version-194
  • 15cc826 Drop support for EOL Python 3.10
  • e5578ef Read version from package metadata (fixes #194)
  • 6bed103 Merge pull request #200 from MarcoGorelli/pre-commit-ci-update-config
  • e638a50 pre-commit autoupdate: ruff 0.16.10
  • See full diff in compare view

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 pre-commit-monthly group with 4 updates: [https://github.com/NVIDIA/security-workflows](https://github.com/NVIDIA/security-workflows), [https://github.com/astral-sh/ruff-pre-commit](https://github.com/astral-sh/ruff-pre-commit), [https://github.com/pre-commit/mirrors-clang-format](https://github.com/pre-commit/mirrors-clang-format) and [https://github.com/MarcoGorelli/cython-lint](https://github.com/MarcoGorelli/cython-lint).


Updates `https://github.com/NVIDIA/security-workflows` from v0.4.0 to 0.5.0
- [Release notes](https://github.com/NVIDIA/security-workflows/releases)
- [Changelog](https://github.com/NVIDIA/security-workflows/blob/main/CHANGELOG.md)
- [Commits](NVIDIA/security-workflows@c736f04...0659a2e)

Updates `https://github.com/astral-sh/ruff-pre-commit` from v0.17.3 to 0.17.4
- [Release notes](https://github.com/astral-sh/ruff-pre-commit/releases)
- [Commits](astral-sh/ruff-pre-commit@25bcf95...c0f278f)

Updates `https://github.com/pre-commit/mirrors-clang-format` from v23.1.3 to 23.1.5
- [Commits](pre-commit/mirrors-clang-format@98ad4dd...ce4bd72)

Updates `https://github.com/MarcoGorelli/cython-lint` from v0.22.0 to 0.22.1
- [Release notes](https://github.com/MarcoGorelli/cython-lint/releases)
- [Commits](MarcoGorelli/cython-lint@35dbc94...7b81144)

---
updated-dependencies:
- dependency-name: https://github.com/NVIDIA/security-workflows
  dependency-version: 0.5.0
  dependency-type: direct:production
  dependency-group: pre-commit-monthly
- dependency-name: https://github.com/astral-sh/ruff-pre-commit
  dependency-version: 0.17.4
  dependency-type: direct:production
  dependency-group: pre-commit-monthly
- dependency-name: https://github.com/pre-commit/mirrors-clang-format
  dependency-version: 23.1.5
  dependency-type: direct:production
  dependency-group: pre-commit-monthly
- dependency-name: https://github.com/MarcoGorelli/cython-lint
  dependency-version: 0.22.1
  dependency-type: direct:production
  dependency-group: pre-commit-monthly
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added CI/CD CI/CD infrastructure dependencies Pull requests that update a dependency file labels Nov 13, 2026
@copy-pr-bot

copy-pr-bot Bot commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD CI/CD infrastructure dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant