Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support heroku-22 stack #26

Merged
merged 3 commits into from
Jun 19, 2022
Merged

Support heroku-22 stack #26

merged 3 commits into from
Jun 19, 2022

Conversation

sgerrand
Copy link

💁 These changes add support for the heroku-22 stack.

To test these changes I've successfully deployed some private Heroku apps using the heroku-22 stack that are configured with this buildpack, but am interested to know what else could/would be useful for me to do to validate that these changes will work as expected.

@kapso kapso mentioned this pull request Jun 19, 2022
@brandoncc
Copy link
Contributor

Thank you for adding this. The one thing I also like to keep up to date is the config output in the readme. I will update that, since I'm also going to drop heroku-16 support.

@brandoncc brandoncc merged commit 2bfc574 into Newlywords:master Jun 19, 2022
@brandoncc
Copy link
Contributor

I forgot to answer your question, sorry. I test the buildpacks the same way you did. I don't know of a better way, but I am open to suggestions if there is one.

@sgerrand sgerrand deleted the heroku-22 branch August 1, 2022 15:28
@sgerrand
Copy link
Author

sgerrand commented Aug 1, 2022

I test the buildpacks the same way you did. I don't know of a better way, but I am open to suggestions if there is one.

I think that the changes in your build script should broadly cover it, i.e. that vips --vips-config and vips --vips-version contain a set of expected strings in their output.

@sgerrand
Copy link
Author

sgerrand commented Aug 1, 2022

(Sorry for my delayed reply!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants