posit-dev / posit-dev/images-shared
Account for latency in dependency releases.
Open
Nobody has claimed this yet.
cicd
cvp:0
docker
enhancement
tdp:2
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 22
Description
Python 3.14 was released on 2025-10-07.
Builds for development versions broke due to
- The source we pull from download-metadata.json updated to include
3.14.0 - The image we use astral-sh/uv had not yet been updated.
- The
uvimage update was dependent on the official python images on dockerhub, which had not yet been built
python-3.14.0rc3 successfully installed in the image, but the build failed because it was trying to use /opt/python/cpython-3.14.0-linux-x86_64-gnu as the path.
Options
- Inject a local
download-metadata.jsoninto the image build usingUV_PYTHON_DOWNLOADS_JSON_URL - Install
uvfrom a different source - Let scheduled preview builds fail?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the development-version build that consumes download-metadata.json and compare it with the published astral-sh/uv image and official Python Docker image availability. Reproduce the Python 3.14 timing failure, then establish a build behavior that remains valid when dependency releases arrive at different times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100