Skip to content

[Snyk] Security upgrade python from 3.13.1-alpine to 3.14.2-alpine#286

Merged
adthrasher merged 4 commits intosnyk-fix-29f47df8693f754e3a31c4fb20799183from
snyk-fix-2a188fd777e3c8c8cba6680c84ad1716
Feb 6, 2026
Merged

[Snyk] Security upgrade python from 3.13.1-alpine to 3.14.2-alpine#286
adthrasher merged 4 commits intosnyk-fix-29f47df8693f754e3a31c4fb20799183from
snyk-fix-2a188fd777e3c8c8cba6680c84ad1716

Conversation

@kevin-benton
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to fix 4 vulnerabilities in the dockerfile dependencies of this project.

Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.

Snyk changed the following file(s):

  • docker/umap/Dockerfile

We recommend upgrading to python:3.14.2-alpine, as this image has only 0 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
critical severity Integer Overflow or Wraparound
SNYK-ALPINE321-SQLITE-12675067
  264  
critical severity CVE-2025-6965
SNYK-ALPINE321-SQLITE-11191065
  263  
high severity Integer Overflow or Wraparound
SNYK-ALPINE321-SQLITE-9712340
  161  
high severity CVE-2025-26519
SNYK-ALPINE321-MUSL-8720634
  139  
high severity CVE-2025-26519
SNYK-ALPINE321-MUSL-8720634
  139  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Integer Overflow or Wraparound

@kevin-benton
Copy link
Contributor Author

Merge Risk: High

This upgrade to Python 3.14 introduces significant new features and a key breaking change.

Breaking Change:

  • Code using return, break, or continue to exit a finally block will now raise a SyntaxError due to the implementation of PEP 765. [4, 9]

Major Change:

  • Type annotations are now evaluated lazily by default (PEP 649). This may affect advanced frameworks or libraries that perform introspection on type hints and rely on eager evaluation. [1, 2, 10]

Source: What's New in Python 3.14 documentation
Recommendation: Review code for control flow statements (return, break, continue) inside finally blocks. Validate any code that relies on the specific timing of type annotation evaluation.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@adthrasher
Copy link
Member

The corresponding package.json needs to have the version updated. All references to the image also need to be bumped to the new version.

adthrasher added a commit that referenced this pull request Feb 6, 2026
Snyk's automated PR updated the Dockerfile but missed the repository's
container versioning system. Container images are tagged as
`{version}-{revision}` based on `package.json`, and workflows reference
these tags explicitly.

## Changes

- Incremented `docker/umap/package.json` revision: `10` → `11`
- Updated `workflows/methylation/methylation-cohort.wdl` container tag:
`ghcr.io/stjudecloud/umap:0.5.7-10` → `0.5.7-11`

This ensures the Python 3.14.2-alpine base image (fixing 2 critical + 2
high severity vulnerabilities) is properly versioned and consumed by
dependent workflows.

Before submitting this PR, please make sure:

- [x] You have added a few sentences describing the PR here.
- [ ] The code passes all CI tests without any errors or warnings.
- [ ] You have added tests (when appropriate).
- [ ] You have added an entry in any relevant CHANGELOGs (when
appropriate).
- [x] If you have made any changes to the `scripts/` or `docker/`
directories, please ensure any image versions have been incremented
accordingly!
- [ ] You have updated the README or other documentation to account for
these changes (when appropriate).

<!-- START COPILOT CODING AGENT SUFFIX -->



<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> Pull Request: #286


</details>



<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in
our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: adthrasher <1165729+adthrasher@users.noreply.github.com>
a-frantz
a-frantz previously approved these changes Feb 6, 2026
@adthrasher
Copy link
Member

It looks like the image is failing to build. So this can't merge quite yet.

------
 > [stage-0 3/4] RUN pip install umap-learn==0.5.7 pandas:
222.7   Stored in directory: /root/.cache/pip/wheels/38/5d/34/a5742fbe6152e861b78e9f4327b490a608b859e225b805b570
222.7 Successfully built numba scikit-learn
222.7 Failed to build llvmlite
222.8 
Notice: 222.8 [notice] A new release of pip is available: 25.3 -> 26.0.1
Notice: 222.8 [notice] To update, run: pip install --upgrade pip
222.8 error: failed-wheel-build-for-install
222.8 
222.8 × Failed to build installable wheels for some pyproject.toml based projects
222.8 ╰─> llvmlite
------
Dockerfile:8
--------------------
   6 |         && ln -s /usr/bin/llvm-config-15 /usr/bin/llvm-config
   7 |     
   8 | >>> RUN pip install umap-learn==0.5.7 pandas
   9 |     
  10 |     COPY --from=scripts --chmod=777 methylation/generate_umap.py /scripts/methylation/generate_umap.py
--------------------
ERROR: failed to build: failed to solve: process "/bin/sh -c pip install umap-learn==0.5.7 pandas" did not complete successfully: exit code: 1

snyk-bot and others added 3 commits February 6, 2026 14:33
Snyk's automated PR updated the Dockerfile but missed the repository's
container versioning system. Container images are tagged as
`{version}-{revision}` based on `package.json`, and workflows reference
these tags explicitly.

## Changes

- Incremented `docker/umap/package.json` revision: `10` → `11`
- Updated `workflows/methylation/methylation-cohort.wdl` container tag:
`ghcr.io/stjudecloud/umap:0.5.7-10` → `0.5.7-11`

This ensures the Python 3.14.2-alpine base image (fixing 2 critical + 2
high severity vulnerabilities) is properly versioned and consumed by
dependent workflows.

Before submitting this PR, please make sure:

- [x] You have added a few sentences describing the PR here.
- [ ] The code passes all CI tests without any errors or warnings.
- [ ] You have added tests (when appropriate).
- [ ] You have added an entry in any relevant CHANGELOGs (when
appropriate).
- [x] If you have made any changes to the `scripts/` or `docker/`
directories, please ensure any image versions have been incremented
accordingly!
- [ ] You have updated the README or other documentation to account for
these changes (when appropriate).

<!-- START COPILOT CODING AGENT SUFFIX -->



<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> Pull Request: #286


</details>



<!-- START COPILOT CODING AGENT TIPS -->
---

💬 We'd love your input! Share your thoughts on Copilot coding agent in
our [2 minute survey](https://gh.io/copilot-coding-agent-survey).

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: adthrasher <1165729+adthrasher@users.noreply.github.com>
@adthrasher adthrasher force-pushed the snyk-fix-2a188fd777e3c8c8cba6680c84ad1716 branch from 01fcb0a to e6c610f Compare February 6, 2026 19:33
@adthrasher adthrasher changed the base branch from main to snyk-fix-29f47df8693f754e3a31c4fb20799183 February 6, 2026 20:09
@adthrasher adthrasher merged commit 8458d33 into snyk-fix-29f47df8693f754e3a31c4fb20799183 Feb 6, 2026
20 of 21 checks passed
@adthrasher adthrasher deleted the snyk-fix-2a188fd777e3c8c8cba6680c84ad1716 branch February 6, 2026 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants