Skip to content

build(deps): Bump the python-runtime group across 1 directory with 2 updates - #7

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python-runtime-9367bcaa3a
Open

build(deps): Bump the python-runtime group across 1 directory with 2 updates#7
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python-runtime-9367bcaa3a

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the python-runtime group with 2 updates in the / directory: pydantic and python-frontmatter.

Updates pydantic from 2.13.4 to 2.13.5

Release notes

Sourced from pydantic's releases.

v2.13.5 (2026-08-28)

What's Changed

Fixes

  • Allow reuse of validators when plugins are set by @​Viicos in #13535
  • Fix missing GC traversal on some pydantic-core struct fields by @​Viicos in #13624
  • Fix missing GC traversal in pydantic-core for GeneralFieldsSerializer by @​Viicos in #13629
  • Count validated model fields once in smart unions by @​tamird in #13731
Changelog

Sourced from pydantic's changelog.

v2.13.5 (2026-08-28)

GitHub release

What's Changed

Fixes

  • Allow reuse of validators when plugins are set by @​Viicos in #13535
  • Fix missing GC traversal on some pydantic-core struct fields by @​Viicos in #13624
  • Fix missing GC traversal in pydantic-core for GeneralFieldsSerializer by @​Viicos in #13629
  • Count validated model fields once in smart unions by @​tamird in #13731
Commits
  • 001dea0 Bump pypa/gh-action-pypi-publish action to v1.14.2
  • 558379f Bump twine to v7.0.0
  • 2cfd5d3 Do not check for docs build
  • a735bee Fix more Clippy lints
  • 7eed4a1 Fix Clippy 0.1.95 warnings
  • b353bbb Prepare release v2.13.5
  • 63d2ccc Count validated model fields once in smart unions
  • a53ec2e Speed up PyPy CI tests
  • d65e0f9 Workaround circular import error in Mypy
  • 47a6dbf Fix missing GC traversal in pydantic-core for GeneralFieldsSerializer
  • Additional commits viewable in compare view

Updates python-frontmatter from 1.1.0 to 1.3.0

Release notes

Sourced from python-frontmatter's releases.

v1.3.0 - Now using uv

What's Changed

Full Changelog: eyeseast/python-frontmatter@v1.2.0...v1.3.0

v1.2.0 - Fix type issues and support newer Python versions

What's Changed

New Contributors

This version drops support for Python 3.9.

Full Changelog: eyeseast/python-frontmatter@v1.1.0...v1.2.0

Commits
  • dc7c0af Merge pull request #131 from eyeseast/123-uv
  • 1e787d8 Migrate to uv and pyproject.toml
  • 3622432 Merge pull request #129 from eyeseast/126-remove-codecs
  • c4fdd50 Encoding is a kwarg
  • 6fa3a9a Remove codecs from tests
  • 3a8c600 Merge pull request #128 from eyeseast/upgrade-actions
  • 8243f83 Test on Python 3.14 and upgrade actions
  • 55bcc67 v1.2.0
  • 949826f Merge pull request #125 from giuse-boccia/fix/include-py-typed-marker
  • b12a13b Include py.typed marker in package distribution
  • Additional commits viewable in compare view

@dependabot @github

dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: python. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 7, 2026
SOSOVSKI added a commit that referenced this pull request Sep 10, 2026
CodeQL alert #7, py/tarslip, high severity, on the unfiltered fallback at
vault_commands.py:161. It was right, and this is not a suppression.

The previous shape validated every member and then called `extractall`,
falling back to an unfiltered call on interpreters whose tarfile predates the
`data` filter. That fallback was a genuine weak point rather than a false
positive: tarfile re-derives each destination path from the same member names,
so the validation above it was advisory, not load-bearing. Nothing connected
the check to the write.

Extraction is now explicit, member by member, so the path check is the only
route to disk. That also turns a blacklist into a whitelist: a vault is
directories and regular files, so symlinks, hardlinks, devices and FIFOs are
skipped rather than reasoned about, and archive permissions are not carried
over — nothing can arrive with an executable or setuid bit.

It removes the version-dependent behaviour too. There is no longer a filter
argument that may or may not exist, so every interpreter takes the same path.

No `extractall` and no security suppression remains in the package.

Verified: a hostile archive carrying a symlink to /etc/passwd and a 0o4777
mode installs two nodes and neither the link nor the mode lands; the traversal
refusal still fires; and a bare `akms vault install` against the published
v1.0.0 tarball still yields 264 nodes, 14 payloads and a 909-edge graph.
1757 tests pass, ruff clean, pyright 0 errors, public-tree audit passes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TcdE6eeSDBh8xrgKCoGrkw
SOSOVSKI added a commit that referenced this pull request Sep 10, 2026
CodeQL alert #7, py/tarslip, high severity, on the unfiltered fallback at
vault_commands.py:161. It was right, and this is not a suppression.

The previous shape validated every member and then called `extractall`,
falling back to an unfiltered call on interpreters whose tarfile predates the
`data` filter. That fallback was a genuine weak point rather than a false
positive: tarfile re-derives each destination path from the same member names,
so the validation above it was advisory, not load-bearing. Nothing connected
the check to the write.

Extraction is now explicit, member by member, so the path check is the only
route to disk. That also turns a blacklist into a whitelist: a vault is
directories and regular files, so symlinks, hardlinks, devices and FIFOs are
skipped rather than reasoned about, and archive permissions are not carried
over — nothing can arrive with an executable or setuid bit.

It removes the version-dependent behaviour too. There is no longer a filter
argument that may or may not exist, so every interpreter takes the same path.

No `extractall` and no security suppression remains in the package.

Verified: a hostile archive carrying a symlink to /etc/passwd and a 0o4777
mode installs two nodes and neither the link nor the mode lands; the traversal
refusal still fires; and a bare `akms vault install` against the published
v1.0.0 tarball still yields 264 nodes, 14 payloads and a 909-edge graph.
1757 tests pass, ruff clean, pyright 0 errors, public-tree audit passes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TcdE6eeSDBh8xrgKCoGrkw
@dependabot
dependabot Bot force-pushed the dependabot/uv/python-runtime-9367bcaa3a branch from 5f7bb40 to 7936fc8 Compare September 10, 2026 16:53
…updates

Bumps the python-runtime group with 2 updates in the / directory: [pydantic](https://github.com/pydantic/pydantic) and [python-frontmatter](https://github.com/eyeseast/python-frontmatter).


Updates `pydantic` from 2.13.4 to 2.13.5
- [Release notes](https://github.com/pydantic/pydantic/releases)
- [Changelog](https://github.com/pydantic/pydantic/blob/v2.13.5/HISTORY.md)
- [Commits](pydantic/pydantic@v2.13.4...v2.13.5)

Updates `python-frontmatter` from 1.1.0 to 1.3.0
- [Release notes](https://github.com/eyeseast/python-frontmatter/releases)
- [Commits](eyeseast/python-frontmatter@v1.1.0...v1.3.0)

---
updated-dependencies:
- dependency-name: pydantic
  dependency-version: 2.13.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-runtime
- dependency-name: python-frontmatter
  dependency-version: 1.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-runtime
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/uv/python-runtime-9367bcaa3a branch from 7936fc8 to 5fd64f4 Compare September 10, 2026 18:23
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants