Warn that the buildpack is deprecated + no longer required

[edmorley]

This buildpack is no longer required now that the Heroku Python buildpack supports Poetry natively:

• https://devcenter.heroku.com/changelog-items/3050
• Add support for Poetry heroku/heroku-buildpack-python#1682

As such, a deprecation warning has been added to both the build log and the README.

The warning borrows from the implementation here (which uses colour, and also makes sure to ANSI wrap each line individually to prevent issues with streaming logs from git push etc):
https://github.com/heroku/heroku-buildpack-python/blob/ca99c39f9e3627fff727788206f7fcc4ff064b7f/lib/output.sh#L50-L66

Closes #75.

[edmorley]

Example of the warning in the build log in the dashboard (showing the usage of colour):

[felix11h]

Thank you for preparing these changes! 👍

[marns93]

🚀

[edmorley]

Thank you for the review and merge!

[edmorley]

I don't suppose you own the moneymeets namespace on the Heroku Buildpack Registry? (Namespace names are independent of Heroku team names)

If so, would it be ok for you to push a new version there? :-)

$ heroku buildpacks:versions moneymeets/python-poetry
 Version Released At              Status
 ─────── ──────────────────────── ─────────
 2       2021-01-29T08:36:35.597Z published
 1       2020-12-27T22:10:28.531Z published

To save having to set up the Heroku CLI (and install the buildpack registry plugin) it's possible to trigger a publish from main of this repo via the UI here (if logged in as a user who is a member of the Heroku team connected to the registry namespace):
https://addons-next.heroku.com/buildpacks

[marns93]

@edmorley Thanks for pointing to this. This was created by my account. I've published an updated version.

$ heroku buildpacks:versions moneymeets/python-poetry 
Version Released At              Status    
 ─────── ──────────────────────── ───────── 
 3       2024-11-21T12:57:43.849Z published 
 2       2021-01-29T08:36:35.597Z published 
 1       2020-12-27T22:10:28.531Z published 

This is not used, so in theory I could archive this. Same will be true for this repository, we will archive this in the next few days.

[edmorley]

That sounds great! Thank you so much for both creating/maintaining this buildpack over the years and now helping with the transition :-)

[edmorley]

This is not used, so in theory I could archive this.

Archiving is also a safe operation (the assets on S3 will remain, so existing apps using it will continue to build):
https://devcenter.heroku.com/articles/buildpack-registry#archiving-your-buildpack

Archiving a buildpack is a safe operation that will not break apps that currently use the buildpack.

[marns93]

That sounds great! Thank you so much for both creating/maintaining this buildpack over the years and now helping with the transition :-)

It was our pleasure to create/maintain this buildpack and see the community using it.

[marns93]

This is not used, so in theory I could archive this.

Archiving is also a safe operation (the assets on S3 will remain, so existing apps using it will continue to build): https://devcenter.heroku.com/articles/buildpack-registry#archiving-your-buildpack

Archiving a buildpack is a safe operation that will not break apps that currently use the buildpack.

Okay, if it is a safe operation there is absolutely nothing against archiving it. Archived already :)