Remove testing & binary generation support for Heroku-16 #1214
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Heroku-16 stack reached end-of-life on May 1st, 2021, and from June 1st, 2021, builds will be disabled:
https://help.heroku.com/0S5P41DC/heroku-16-end-of-life-faq
This removes support for testing against Heroku-16 in CI, and also for building new Python binaries for the stack.
This change is non-breaking as it only affects the development of this buildpack (hence why it's landing a few days early), however a changelog entry has been added regardless, for improved visibility into the support status of the stack.
Closes GUS-W-9329579.