Repository navigation
fix(docker): build the hosted image on Python 3.14 - #107
Merged
Merged
Conversation
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.
The hosted image was built on
python:3.10-slim. Docker Hub has not rebuilt that tag since 2026-10-06, so the image keeps ca-certificates 20250419, which still trustsemSign ECC Root CA - G3(the eMudhra intermediate key leak, GHSA-6q48-6c7w-9gw2). Republishing the image cannot fix that. I moved the default to 3.14, the newest version the package supports and tests. A local build has ca-certificates 20250419+deb13u1 with no G3, certifi 2026.10.19 and uv 0.13.4. The server card, protected-resource metadata and healthcheck all return 200, and/mcpreturns 401 without a token.