Prepare release v292

[heroku-linguist]

Commits since the last release:

• Remove unused metrics (Remove unused bin/report metrics #1832)
• Require a Pipfile.lock when using Pipenv (Require a Pipfile.lock when using Pipenv #1833)
• Port uv test improvements to other package manager tests (Port uv test improvements to other package manager tests #1834)
• Update checks function names now that they error (Update checks function names now that they error #1836)
• Port package manager test improvements from CNB (Port package manager test improvements from CNB #1835)
• Bump the ruby-dependencies group with 2 updates (Bump the ruby-dependencies group with 2 updates #1838)
• Remove superseded python_version_reason metric (Remove superseded python_version_reason metric #1839)
• Update Pipenv to 2025.0.4 and improve installation/caching (Update Pipenv to 2025.0.4 and improve installation/caching #1840)

For the full diff, see the compare view:
v291...main

[edmorley]

$ make publish
Checking environment...
Checking buildpack versions in sync...
Extracting changelog entry for this release...

- Updated Pipenv from 2024.0.1 to 2025.0.4. ([#1840](https://github.com/heroku/heroku-buildpack-python/pull/1840))
- Fixed the way Pipenv is installed, so that it and its dependencies are installed into a separate virtual environment rather than same environment as the app. If your app inadvertently depended on Pipenv's internal dependencies, you will need to add those dependencies explicitly to your `Pipfile`. ([#1840](https://github.com/heroku/heroku-buildpack-python/pull/1840))
- Stopped installing pip when Pipenv is the chosen package manager. ([#1840](https://github.com/heroku/heroku-buildpack-python/pull/1840))
- The build cache is now cleared when using Pipenv if the contents of `Pipfile.lock` has changed since the last build. This is required to work around Pipenv not uninstalling packages when they are removed from the lockfile. ([#1840](https://github.com/heroku/heroku-buildpack-python/pull/1840))
- The build now errors when using Pipenv without its lockfile (`Pipfile.lock`). This replaces the warning displayed since November 2024. ([#1833](https://github.com/heroku/heroku-buildpack-python/pull/1833))

Deploy as v292 [y/n]? y

Creating GitHub release...
https://github.com/heroku/heroku-buildpack-python/releases/tag/v292

Publishing to the Heroku Buildpack Registry...
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful

 Version Released At              Status    
 ─────── ──────────────────────── ───────── 
 292     2025-07-23T13:39:36.947Z published