Add support for Python 3.12.5 (#244)

Release announcement:
https://blog.python.org/2024/08/python-3125-released.html

Changelog:
https://docs.python.org/release/3.12.5/whatsnew/changelog.html#python-3-12-5

Binary builds:
https://github.com/heroku/heroku-buildpack-python/actions/runs/10285472077

GUS-W-14846791.

Author: edmorley

CHANGELOG.md

@@ -9,6 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Changed
 
+- Updated the default Python version from 3.12.4 to 3.12.5. ([#244](https://github.com/heroku/buildpacks-python/pull/244))
 - Updated pip from 24.1.2 to 24.2. ([#236](https://github.com/heroku/buildpacks-python/pull/236))
 
 ## [0.14.0] - 2024-08-07

README.md

@@ -43,7 +43,7 @@ To install a different version, add a `runtime.txt` file to your app’s root di
 
 ```term
 $ cat runtime.txt
-python-3.12.4
+python-3.12.5
 ```
 
 In the future this buildpack will also support specifying the Python version via a `.python-version` file (see [#6](https://github.com/heroku/buildpacks-python/issues/6)).

src/python_version.rs

@@ -9,7 +9,7 @@ use std::path::Path;
 pub(crate) const DEFAULT_PYTHON_VERSION: PythonVersion = PythonVersion {
     major: 3,
     minor: 12,
-    patch: 4,
+    patch: 5,
 };
 
 /// Representation of a specific Python `X.Y.Z` version.

tests/fixtures/python_3.12/runtime.txt

@@ -1 +1 @@
-python-3.12.4
+python-3.12.5

tests/mod.rs

@@ -18,7 +18,7 @@ const LATEST_PYTHON_3_8: &str = "3.8.19";
 const LATEST_PYTHON_3_9: &str = "3.9.19";
 const LATEST_PYTHON_3_10: &str = "3.10.14";
 const LATEST_PYTHON_3_11: &str = "3.11.9";
-const LATEST_PYTHON_3_12: &str = "3.12.4";
+const LATEST_PYTHON_3_12: &str = "3.12.5";
 const DEFAULT_PYTHON_VERSION: &str = LATEST_PYTHON_3_12;
 
 const DEFAULT_BUILDER: &str = "heroku/builder:24";

tests/pip_test.rs

@@ -102,16 +102,11 @@ fn pip_basic_install_and_cache_reuse() {
 #[test]
 #[ignore = "integration test"]
 fn pip_cache_invalidation_with_compatible_metadata() {
-    // TODO: Re-enable this test the next time the default-Python/pip versions change, at which point
-    // there will be a historic buildpack version with compatible metadata that triggers invalidation.
-    #![allow(unreachable_code)]
-    return;
-
     let config = default_build_config("tests/fixtures/pip_basic");
 
     TestRunner::default().build(
         config.clone().buildpacks([BuildpackReference::Other(
-            "docker://docker.io/heroku/buildpack-python:TODO".to_string(),
+            "docker://docker.io/heroku/buildpack-python:0.14.0".to_string(),
         )]),
         |context| {
             context.rebuild(config, |rebuild_context| {
@@ -125,8 +120,8 @@ fn pip_cache_invalidation_with_compatible_metadata() {
                         
                         [Installing Python and pip]
                         Discarding cache since:
-                         - The Python version has changed from 3.12.3 to {DEFAULT_PYTHON_VERSION}
-                         - The pip version has changed from 24.0 to {PIP_VERSION}
+                         - The Python version has changed from 3.12.4 to {DEFAULT_PYTHON_VERSION}
+                         - The pip version has changed from 24.1.2 to {PIP_VERSION}
                         Installing Python {DEFAULT_PYTHON_VERSION}
                         Installing pip {PIP_VERSION}