Repository navigation
Audit Snyk check/fix 1.22 - #4079
Open
geo-ghci-int[bot] wants to merge 1 commit into
Open
geo-ghci-int[bot] wants to merge 1 commit into
geo-ghci-int[bot] wants to merge 1 commit into
Conversation
sbrunner
disabled auto-merge
November 6, 2026 18:14
geo-ghci-int
Bot
force-pushed
the
ghci/audit/snyk/1.22
branch
from
November 6, 2026 19:47
c6837e7 to
395935f
Compare
…ith used Poetry version The Snyk fix pinned poetry>=2.3.4 in ci/requirements.txt and bumped poetry to 2.3.4 in requirements.txt, but poetry-plugin-tweak-dependencies-version 1.5.7 requires poetry<2.1.0, and pip failed with ResolutionImpossible. The poetry upgrade is blocked by the plugin incompatibility, and while poetry stays at 1.8.5, the following transitive dependencies cannot be upgraded to their fixed versions: - dulwich: poetry requires dulwich<0.23.0, the fixes need dulwich>=1.1.0 (SNYK-PYTHON-DULWICH-17054926/17054927/17266106/18016337/20416729/20416732/22220108) - virtualenv: poetry requires virtualenv<21.0.0, the fixes need virtualenv>=21.7.11 (SNYK-PYTHON-VIRTUALENV-20335491/20335492/20335493/20335500/21282339/21282342/21282424/21282484/21282509) - filelock: virtualenv requires filelock<4.0.0, the fixes need filelock>=4.0.9 (SNYK-PYTHON-FILELOCK-21280750/21280753/21280754/21280755/21280756/21280759/21280760/21280761/21689161/21689162/21802489/21802490/21802520) - poetry itself: Plugin not compatible with new Poetry version (SNYK-PYTHON-POETRY-15873752/16122096) Drop the Snyk pins from ci/requirements.txt and requirements.txt and ignore those advisories in .snyk and ci/.snyk, following the same policy already applied on the 1.21 branch. Failing CI: https://github.com/camptocamp/tilecloud-chain/actions/runs/42282692329/job/128115474462 Audit logs: https://geoservices-int.camptocamp.com/github/logs/3302538
sbrunner
force-pushed
the
ghci/audit/snyk/1.22
branch
from
November 6, 2026 22:17
395935f to
cb0ce8c
Compare
geo-ghci-int
Bot
force-pushed
the
ghci/audit/snyk/1.22
branch
from
November 7, 2026 20:32
cb0ce8c to
af30563
Compare
sbrunner
force-pushed
the
ghci/audit/snyk/1.22
branch
from
November 8, 2026 14:05
af30563 to
cb0ce8c
Compare
geo-ghci-int
Bot
force-pushed
the
ghci/audit/snyk/1.22
branch
from
November 8, 2026 20:19
cb0ce8c to
0c3d299
Compare
sbrunner
force-pushed
the
ghci/audit/snyk/1.22
branch
from
November 8, 2026 20:40
0c3d299 to
cb0ce8c
Compare
Member
|
CI fails deterministically: the Snyk pin The branch was again reset to the fix commit Note: the audit runs scan the |
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.
Fixes applied (pins added to requirements files)
The rescan still reports these vulnerabilities because Snyk builds the pip dependency tree
from the packages installed in the audit environment, which is not reinstalled after the fix.
dulwich0.21.7inci/requirements.txt— CVE-2026-122299, SNYK-PYTHON-DULWICH-22220108 — fixed in1.2.20— pinned to1.2.20virtualenv20.39.1inci/requirements.txt— CVE-2026-113725, SNYK-PYTHON-VIRTUALENV-21282484 — fixed in21.14.7— pinned to21.14.7virtualenv20.39.1inci/requirements.txt— CVE-2026-113725, SNYK-PYTHON-VIRTUALENV-21282509 — fixed in21.14.7— pinned to21.14.7filelock3.32.7inci/requirements.txt— CVE-2026-112910, SNYK-PYTHON-FILELOCK-21802490 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112911, SNYK-PYTHON-FILELOCK-21280756 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112939, SNYK-PYTHON-FILELOCK-21280760 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112909, SNYK-PYTHON-FILELOCK-21280759 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112908, SNYK-PYTHON-FILELOCK-21802489 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112938, SNYK-PYTHON-FILELOCK-21802520 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112935, SNYK-PYTHON-FILELOCK-21280755 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112915, SNYK-PYTHON-FILELOCK-21280750 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112913, SNYK-PYTHON-FILELOCK-21689161 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112940, SNYK-PYTHON-FILELOCK-21280753 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112912, SNYK-PYTHON-FILELOCK-21280761 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inci/requirements.txt— CVE-2026-112907, SNYK-PYTHON-FILELOCK-21689162 — fixed in4.2.1— pinned to4.2.1poetry1.8.5inci/requirements.txt— CVE-2026-41140, SNYK-PYTHON-POETRY-16122096 — fixed in2.3.4— pinned to2.3.4dulwich0.21.7inrequirements.txt— CVE-2026-122299, SNYK-PYTHON-DULWICH-22220108 — fixed in1.2.20— pinned to1.2.20virtualenv20.39.1inrequirements.txt— CVE-2026-113725, SNYK-PYTHON-VIRTUALENV-21282509 — fixed in21.14.7— pinned to21.14.7virtualenv20.39.1inrequirements.txt— CVE-2026-113725, SNYK-PYTHON-VIRTUALENV-21282484 — fixed in21.14.7— pinned to21.14.7filelock3.32.7inrequirements.txt— CVE-2026-112909, SNYK-PYTHON-FILELOCK-21280759 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112940, SNYK-PYTHON-FILELOCK-21280753 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112911, SNYK-PYTHON-FILELOCK-21280756 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112938, SNYK-PYTHON-FILELOCK-21802520 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112915, SNYK-PYTHON-FILELOCK-21280750 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112939, SNYK-PYTHON-FILELOCK-21280760 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112913, SNYK-PYTHON-FILELOCK-21689161 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112910, SNYK-PYTHON-FILELOCK-21802490 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112908, SNYK-PYTHON-FILELOCK-21802489 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112935, SNYK-PYTHON-FILELOCK-21280755 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112907, SNYK-PYTHON-FILELOCK-21689162 — fixed in4.2.1— pinned to4.2.1filelock3.32.7inrequirements.txt— CVE-2026-112912, SNYK-PYTHON-FILELOCK-21280761 — fixed in4.2.1— pinned to4.2.1poetry1.8.5inrequirements.txt— CVE-2026-41140, SNYK-PYTHON-POETRY-16122096 — fixed in2.3.4— pinned to2.3.4snyk fix output
⠋ Running
snyk testfor /root/.cache/ghci/git/worktrees/camptocamp/tilecloud-chain/1.22/tilecloud-chain► Running
snyk testfor /root/.cache/ghci/git/worktrees/camptocamp/tilecloud-chain/1.22/tilecloud-chain✔ Looking for supported Python items
✔ Looking for supported Python items
⠋ Processing 1 pyproject.toml items⠋ Processing 2 requirements.txt items✔ Processed 2 requirements.txt items
✔ Processed 1 pyproject.toml items
ERROR Unspecified Error (SNYK-CLI-0000)
✖ No successful fixes
Unresolved items:
pyproject.toml
x Failed to upgrade pillow from 12.3.0 to 13.0.0
Reason: No fixes could be applied.
Tip: Try running
poetry add pillow==13.0.0Summary:
1 items were not fixed
1 items were not vulnerable
39 issues: 6 Critical | 23 High | 10 Medium
36 issues are fixable
Tip: Re-run in debug mode to see more information: DEBUG=*snyk* .
If the issue persists contact support@snyk.io
Docs: https://docs.snyk.io/scan-with-snyk/error-catalog#snyk-cli-0000
Tip: Try snyk doctor:
snyk <command> -d 2>&1 | snyk doctor --stdinID: urn:snyk:interaction:f9456136-b9a2-4c08-8b69-979428ebb132
Logs | Output