Repository navigation
fix: repair Docker build with Python 3.14 and bump to 5.7.2 - #238
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.
Fix the Docker build failure caused by copying an untracked
.python-versionfile. Select Python 3.14 withUV_PYTHON, preserve thesrc/anddata/directories when copying them into the image, and bump Konoha to 5.7.2 inpyproject.tomlanduv.lock.Failed job: https://github.com/himkt/konoha/actions/runs/40188258679/job/121153554335
Validation:
uv sync --all-extrassucceeded on Python 3.14.9; the lockfile diff contains only the project version bump.linux/amd64Docker image built successfully with Python 3.14.3 and Konoha 5.7.2. API startup and single/batch tokenization passed for every supported tokenizer.Mykyteamodule; both tokenizers passed the Docker API checks. The deselected test requires an S3 resource.