Repository navigation
fix: Bump Pygments and setuptools to patched versions - #434
Merged
Merged
Conversation
![kodiakhq[bot]](https://avatars.githubusercontent.com/in/29196?s=60&v=4){kind=small}
kodiakhq Bot
pushed a commit
that referenced
this pull request
Nov 3, 2026
🤖 I have created a release *beep* *boop* --- ## [0.1.61](v0.1.60...v0.1.61) (2026-11-03) ### Bug Fixes * Bump Pygments and setuptools to patched versions ([#434](#434)) ([dee6e3a](dee6e3a)) * **deps:** Update dependency setuptools to v84 [SECURITY] ([#433](#433)) ([a51a5b8](a51a5b8)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the vulnerable dependencies in
uv.lockwithuv lock --upgrade-package pygments --upgrade-package setuptools(uv 0.13.6, the version the Dockerfile pins).The lock also syncs the
cloudquery-plugin-sdkversion (0.1.58 → 0.1.60), whichuv lockdoes on its own.Only
uv.lockchanges.pyproject.tomlhas no direct pin on either package; Pygments and setuptools are resolved transitively.Overlap
mainstill resolves setuptools 82.0.1. Alerts 8 and 10 are still open onmain.cloudquery-plugin-sdkversion line inuv.lock. It does not bump setuptools, so it does not fix alerts 8 or 10, and it is superseded by this change.main.Test
Lock-only change, so there is no new test. The existing suite is the check.
Before (
main, setuptools 82.0.1, Pygments 2.19.2):uv sync --frozenandmake testgive 1 failed, 87 passed in 59.23s.After (this branch, setuptools 84.2.1, Pygments 2.21.0):
uv sync --frozenandmake testgive 1 failed, 87 passed in 59.23s.make fmt-checkpasses (88 files unchanged).The one failure is
tests/serve/plugin.py::test_plugin_package. It fails the same way onmain:Unable to run Docker command: ERROR: failed to connect to the docker API at unix:///var/run/docker.sock. The sandbox has no Docker daemon. The test needs Docker, and CI will show whether it passes there.Fixes https://linear.app/env-zero/issue/ATH-1516/fix-open-dependabot-alerts-in-cloudqueryplugin-sdk-python