Bogus "3.10.0-beta.1" release
See original GitHub issueIn https://github.com/actions/python-versions/pull/92/, it looks like a 3.10.0-beta.1 release was pushed, which also gets used with python: 3.10-dev
now.
However, the actual Beta 1 release is planned to happen on May 3rd, thus this tag has nothing to do with the “real” beta 1.
Not sure if that was intended? If it was, it sure seems confusing to me…
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Bogus 3.10 beta 1 build? - Discussions on Python.org
GitHub Actions provides Python versions, and made a 3.10beta1 a few weeks ago: [versions-manifest] Update for release from 04/19/2021 by ...
Read more >gatekeeper 3.10.0-beta.0 - Artifact Hub
Option 1: A simple way to upgrade is to uninstall first and re-install with ... This will remove the Helm secret for the...
Read more >PostGIS 3.2.0beta1 Released
The PostGIS Team is pleased to release the first beta of the upcoming PostGIS 3.2.0 release. Best served with PostgreSQL 14.
Read more >UniFi Video 3.10.1 Full Release - Ubiquiti Community
Then, upgrading an NVR from 3.9.12 to 3.10.0+ must be done via the web UI update ... recording recovery failure found in 3.10.0...
Read more >Azure PowerShell release notes - Microsoft Learn
0-beta.1 which uses service fabric resource provider api-version 2021-01-01-preview. Az.Sql. Added cmdlet 'New ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello everyone! Thanks for the notice! We’ve removed the
3.10.0-beta.1
release fromactions/python-versions
repository in scope of this PR.I’m closing this issue. Please let us know if you have any concerns.
I will start an investigation on what process has created such tarball so this doesn’t happen again. I checked and there was no other trace of this so my guess is that this has been some kind of automation or human error at some problem in the download server.