Add support for Heroku-22 #161
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary generated using `make build-heroku-22`. GUS-W-10346720.
Malax
approved these changes
May 19, 2022
Merged
edmorley
added a commit
that referenced
this pull request
May 19, 2022
To pick up #161. GUS-W-10346720.
shrolox
added a commit
to klaxit/heroku-buildpack-pgbouncer
that referenced
this pull request
Oct 5, 2022
* Add support for Heroku-22 (heroku#161) Binary generated using `make build-heroku-22`. GUS-W-10346720. * Release v0.10.0 (heroku#162) To pick up heroku#161. GUS-W-10346720. * Update to pgbouncer v1.17.0 on Heroku-22 (heroku#166) To fix crashes/seg faults seen on Heroku-22 due to Ubuntu 22.04 now shipping with OpenSSL 3. See: https://www.pgbouncer.org/2022/03/pgbouncer-1-17-0 https://www.pgbouncer.org/changelog.html#pgbouncer-117x The other stacks remain on pgbouncer 1.14.0 for now, until heroku#150 (the reason an earlier upgrade to pgbouncer was rolled back) can be investigated. heroku#165 is also open for improving the CI of this repo (since it didn't catch these crashes), though fixing that is out of the scope of this PR, as we just need to stop the crashes for now. Fixes heroku#164. GUS-W-11319779. * Patch sigterm for version 1.17.0 too (heroku#169) * Adds the missing patchfile for 1.17.0, meaning sigterm is now correctly patched for that version too. * Removes the "default" patchfiles directory and makes the per-version directories mandatory, so future releases can't accidentally forget to add a new patchfile. * Removes the patchfile for pgbouncer 1.7 and 1.13.0 since those versions are no longer built. Closes heroku#150. Closes heroku#168. GUS-W-11700066. * Update pgbouncer to v1.17.0 for Heroku-18 and Heroku-20 (heroku#170) For parity with Heroku-22 (thereby reducing differences between stacks, so there is one fewer thing to think about when upgrading stacks), now that the cause of heroku#150 is understood and fixed. https://www.pgbouncer.org/changelog.html#pgbouncer-117x Binaries generated using `make build-heroku-18 build-heroku-20`. * Convert to Github Actions (heroku#172) * Allow SSL certificate usage for database connections * remake binaries Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com> Co-authored-by: Ken Barber <ken@bob.sh> Co-authored-by: teckwan <wong.teck.wan@outlook.com> Co-authored-by: Pierre-Olivier Maugis <pierre-olivier.maugis@klaxit.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Binary generated using
make build-heroku-22.GUS-W-10346720.