Bug Report: Re-support 3.13.0

[okkays]

Describe the bug

The image for 3.13.0 is no longer available with the release of 3.13.1

Our production systems still don't support 3.13.1 - we're hoping to stay on 3.13.0 for a bit until those systems are ready for the update.

To Reproduce

└╼ docker run -t cimg/python:3.13.0 python --version
Unable to find image 'cimg/python:3.13.0' locally
docker: Error response from daemon: manifest for cimg/python:3.13.0 not found: manifest unknown: manifest unknown.
See 'docker run --help'.

Running 3.13 (as expected) now returns 3.13.1

└╼ docker run -t cimg/python:3.13 python --version
Unable to find image 'cimg/python:3.13' locally
3.13: Pulling from cimg/python
a4a2c7a57ed8: Pull complete
08add8a39ea3: Pull complete
70e2139a3a8b: Pull complete
ccf799827602: Pull complete
74c0be46c3d7: Pull complete
cbad6d719f21: Pull complete
f38c2a2b3dd5: Pull complete
4f4fb700ef54: Pull complete
8372ba5e4974: Pull complete
4bc9b1f96278: Pull complete
41e090dc1ce8: Pull complete
570077ec471f: Pull complete
Digest: sha256:87b243ae80d154db75ce5e58af16c72c5dd4b1e23e5c7264a816e85e0c440c13
Status: Downloaded newer image for cimg/python:3.13
Python 3.13.1

Expected behavior

docker run -t cimg/python:3.13.0 python --version should return Python 3.13.0

Workarounds

Not aware of any.

Screenshots and Build Links

(See above)

Additional context

We are relying on cloudfoundry buildpacks for production, which are locked to a specific minor version. We update manually to avoid regressions.