Skip to content

Bump the development-tools group with 2 updates - #4

Merged
sbp merged 1 commit into
mainfrom
dependabot/uv/development-tools-389ccdd7c7
Nov 10, 2026
Merged

sbp merged 1 commit into
mainfrom
dependabot/uv/development-tools-389ccdd7c7

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps the development-tools group with 2 updates: zizmor and nodeenv.

Updates zizmor from 1.31.1 to 1.32.0

Release notes

Sourced from zizmor's releases.

v1.32.0

Sponsorship is appreciated!

New Features 🌈🔗

  • zizmor now has experimental support for GitHub Actions workflow lockfiles. Please see the limitations documentation for more information about the current implementation and its limitations (#2463)

Enhancements 🌱🔗

  • zizmor's input collection is now "root-aware" by default, meaning that invocations like zizmor . will no longer collect inputs unless they would actually be used by GitHub Actions, etc. This should eliminate spurious findings from (e.g.) workflow definitions in vendored directories. See the input collection documentation for more information. (#2454)

  • zizmor's LSP now honors the didChangeWorkspaceFolders event (#2461)

  • zizmor's LSP now audits pre-commit inputs (#2485)

  • zizmor now provides Windows ARM64 wheels on PyPI (#2424)

    Many thanks to @​ndabas for proposing and implementing this improvement!

Bug Fixes 🐛🔗

  • Fixed a bug where the bot-conditions audit did not properly flag if: condition of jobs that call a reusable workflow (#2457)

  • Fixed a bug where the obfuscation audit would incorrectly flag (and suggest an incorrect auto-fix for) expressions that constant-reduce to other expressions (#2483)

  • Fixed a bug where the template-injection audit did not flag attacker-controllable contexts wrapped in fromJSON(...), such as fromJSON(toJSON(github.event.issue.title)) (#2495)

  • Fixed a bug where the template-injection audit did not flag attacker-controllable contexts in the values of case(...), such as case(cond, github.event.issue.title, 'x') (#2504)

  • Fixed a class of bugs in the obfuscation audit where a constant-reducible subexpression would not be replaced with a contextually correct form (#2483)

  • Fixed a bug where zizmor would incorrectly audit pre-commit inputs that ended with .yml, despite pre-commit requiring the .yaml suffix (#2485)

  • Fixed a bug where zizmor would not honor some ignore comments for the stale-action-refs audit (#2494)

  • Fixed a bug where zizmor would not honor some ignore comments for the ref-version-mismatch audit (#2494)

Changelog

Sourced from zizmor's changelog.

1.32.0

New Features 🌈

  • zizmor now has experimental support for GitHub Actions workflow lockfiles. Please see the limitations documentation for more information about the current implementation and its limitations (#2463)

Enhancements 🌱

  • zizmor's input collection is now "root-aware" by default, meaning that invocations like zizmor . will no longer collect inputs unless they would actually be used by GitHub Actions, etc. This should eliminate spurious findings from (e.g.) workflow definitions in vendored directories. See the [input collection] documentation for more information. (#2454)

  • zizmor's LSP now honors the didChangeWorkspaceFolders event (#2461)

  • zizmor's LSP now audits pre-commit inputs (#2485)

  • zizmor now provides Windows ARM64 wheels on PyPI (#2424)

    Many thanks to @​ndabas for proposing and implementing this improvement!

Bug Fixes 🐛

  • Fixed a bug where the [bot-conditions] audit did not properly flag if: condition of jobs that call a reusable workflow (#2457)

  • Fixed a bug where the [obfuscation] audit would incorrectly flag (and suggest an incorrect auto-fix for) expressions that constant-reduce to other expressions (#2483)

  • Fixed a bug where the [template-injection] audit did not flag attacker-controllable contexts wrapped in fromJSON(...), such as fromJSON(toJSON(github.event.issue.title)) (#2495)

  • Fixed a bug where the [template-injection] audit did not flag attacker-controllable contexts in the values of case(...), such as case(cond, github.event.issue.title, 'x') (#2504)

  • Fixed a class of bugs in the [obfuscation] audit where a constant-reducible subexpression would not be replaced with a contextually correct form (#2483)

  • Fixed a bug where zizmor would incorrectly audit pre-commit inputs that ended with .yml, despite pre-commit requiring the .yaml suffix (#2485)

  • Fixed a bug where zizmor would not honor some ignore comments for

... (truncated)

Commits

Updates nodeenv from 1.11.1 to 1.12.0

Release notes

Sourced from nodeenv's releases.

1.12.0

What's Changed

New Features 🎉

Fixed bugs 🐛

Improvements 🛠

Documentation 📄

Other Changes

New Contributors

Full Changelog: ekalinin/nodeenv@1.11.1...1.12.0

Changelog

Sourced from nodeenv's changelog.

Version 1.12.0

  • --print-completion SHELL prints a completion script for bash, zsh or fish. It needs shtab, installed with pip install "nodeenv[completion]" [#351](https://github.com/ekalinin/nodeenv/issues/351) <https://github.com/ekalinin/nodeenv/issues/351>_
  • --prebuilt installs no longer fail when the environment path or the node.js version contains [, * or ? [#441](https://github.com/ekalinin/nodeenv/issues/441) <https://github.com/ekalinin/nodeenv/issues/441>_
  • On Windows, Cygwin and MSYS the node.js zip archive is extracted 32 files at a time instead of one by one, so a security scanner that checks every new file no longer makes the install wait for each file in turn. --no-parallel-extract, or parallel_extract = False in ~/.nodeenvrc, extracts it one file at a time again [#366](https://github.com/ekalinin/nodeenv/issues/366) <https://github.com/ekalinin/nodeenv/issues/366>_
  • --prebuilt installs no longer mistake a cached source tree for a prebuilt archive, or fail when both trees remain in src/ [#443](https://github.com/ekalinin/nodeenv/issues/443) <https://github.com/ekalinin/nodeenv/issues/443>_
  • activate.fish restores the caller's NODE_PATH and npm configuration on deactivation, including empty values and when NODE_VIRTUAL_ENV has been removed. Existing environments keep their old activate.fish; recreate them with the same options to get the fix. With -p, remove the old nodeenv part from the virtualenv's activate.fish first [#399](https://github.com/ekalinin/nodeenv/issues/399) <https://github.com/ekalinin/nodeenv/issues/399>_
  • A % in a [nodeenv] config value, such as a percent-encoded mirror login, no longer crashes nodeenv: a value that can't be interpolated and has no %(name)s reference is read as written. %% still gives %, which setup.cfg needs, as setuptools reads that file too [#440](https://github.com/ekalinin/nodeenv/issues/440) <https://github.com/ekalinin/nodeenv/issues/440>_
  • nodeenv -p no longer puts the python venv's bin directory on PATH a second time: the venv's own activate and activate.fish put it there already. Envs without those scripts, such as conda envs, and the git-bash activate on Windows keep it, and running nodeenv -p again fixes an existing venv [#332](https://github.com/ekalinin/nodeenv/issues/332) <https://github.com/ekalinin/nodeenv/issues/332>_
  • Require Python 3.10 or later, matching the minimum version tested in CI. Update package classifiers and wheel tags, and remove the unused Python 2 compatibility paths. Old Node.js source builds still require Python 2.7 as their build interpreter [#436](https://github.com/ekalinin/nodeenv/issues/436) <https://github.com/ekalinin/nodeenv/issues/436>_
  • --source builds of node.js 13 and later no longer need a python2 command; 8.8 to 12.x still need one but point python at it on their own, so the python to python2 link in PATH is only set up for older versions, and versions before 13 still fail early with a clear error when python2 is missing [#419](https://github.com/ekalinin/nodeenv/issues/419) <https://github.com/ekalinin/nodeenv/issues/419>_
  • The node.js archive download also retries when the connection is reset or times out in the middle of the body, pauses between the attempts and ends with an error message instead of a traceback when all of them fail; a server that stops answering is given up on after 60 seconds instead of

... (truncated)

Commits
  • cb7fc97 chore(release): bump nodeenv version to 1.12.0 (#461)
  • c2e21d0 fix(nodeenv): raise on bad config references again (#458)
  • 0fd263f feat(nodeenv): print shell completion scripts with shtab (#460)
  • e1e016b fix(nodeenv): escape glob characters in prebuilt paths (#447)
  • ac28019 perf(nodeenv): unpack the node.js zip archive in parallel (#459)
  • 0e30103 fix(nodeenv): ignore source trees during prebuilt installs (#450)
  • 02f4ce3 fix(nodeenv): read a config value raw when interpolation fails (#449)
  • 2226040 fix(nodeenv): preserve fish activation environment (#431)
  • e27db1e docs(changes): move the #453 entry under 1.11.1 (#455)
  • 8dee9f3 fix(nodeenv): skip node.js pre-releases for latest and ranges (#454)
  • Additional commits viewable 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 development-tools group with 2 updates: [zizmor](https://github.com/zizmorcore/zizmor) and [nodeenv](https://github.com/ekalinin/nodeenv).


Updates `zizmor` from 1.31.1 to 1.32.0
- [Release notes](https://github.com/zizmorcore/zizmor/releases)
- [Changelog](https://github.com/zizmorcore/zizmor/blob/main/docs/release-notes.md)
- [Commits](zizmorcore/zizmor@v1.31.1...v1.32.0)

Updates `nodeenv` from 1.11.1 to 1.12.0
- [Release notes](https://github.com/ekalinin/nodeenv/releases)
- [Changelog](https://github.com/ekalinin/nodeenv/blob/master/CHANGES)
- [Commits](ekalinin/nodeenv@1.11.1...1.12.0)

---
updated-dependencies:
- dependency-name: zizmor
  dependency-version: 1.32.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development-tools
- dependency-name: nodeenv
  dependency-version: 1.12.0
  dependency-type: indirect
  update-type: version-update:semver-minor
  dependency-group: development-tools
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Nov 10, 2026
@sbp
sbp merged commit 554365b into main Nov 10, 2026
4 checks passed
@dependabot
dependabot Bot deleted the dependabot/uv/development-tools-389ccdd7c7 branch November 10, 2026 12:18
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 python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant