Skip to content

[Snyk] Security upgrade python from 3.9 to 3.13.12 #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ashmuck wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade python from 3.9 to 3.13.12 #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# This Dockerfile is only for GitHub Actions
FROM python:3.9
FROM python:3.13.12
Copy link

@cursor cursor bot Mar 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Python 3.13 upgrade breaks pinned dependency compatibility

High Severity

Upgrading from python:3.9 to python:3.13.12 jumps four major versions while setup.py pins dependencies to old ranges only tested through Python 3.9. Notably, invoke>=1.4.1,<2 (used via from invoke import run in dist.py and pre_commit.py) has known inspect.getargspec removal issues on Python 3.11+, and twine>=3,<4 relies on distutils which was removed in Python 3.12. These pinned constraints prevent installing newer compatible versions, risking build or runtime failures.

Fix in Cursor Fix in Web


RUN set -ex; \
apt-get update; \
Expand Down