Skip to content

Conversation

@tianon
Copy link
Member

@tianon tianon commented Mar 20, 2024

This is necessary to account for an upstream release-signing snafu where the 3.8 and 3.9 release manager also signed the latest 3.10 release. 😄

See python/cpython#117053 for details (and to track the resolution).

This is necessary to account for an upstream release-signing snafu where the 3.8 and 3.9 release manager also signed the latest 3.10 release. 😄
@tianon
Copy link
Member Author

tianon commented Mar 20, 2024

Since this is a security release, we don't want to wait for a reply to python/cpython#117053 (comment) in order to get the builds out, especially since it's not like it's signed by a random rogue key (Łukasz is the 3.8 and 3.9 release manager and wrote the blog post about the security releases 😄).

We can easily fix this again later if/when there's a resolution. 👍

@yosifkit yosifkit merged commit f2406ed into docker-library:master Mar 20, 2024
@yosifkit yosifkit deleted the 3.10.14 branch March 20, 2024 18:59
docker-library-bot added a commit to docker-library-bot/official-images that referenced this pull request Mar 20, 2024
Changes:

- docker-library/python@f2406ed: Merge pull request docker-library/python#912 from infosiftr/3.10.14
- docker-library/python@3973575: Update to 3.10.14 manually for now
- docker-library/python@b12dd3e: Update 3.9 to 3.9.19
- docker-library/python@cce15d1: Update 3.8 to 3.8.19
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.

2 participants