You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems #10 is already fixed by 34fe30f and it's already back-ported to REL1_2_STABLE branch.
Would it make sense to tag the current REL1_2_STABLE branch and create a new release with it?
I'm aware that the full migration to GitHub is still being planned, but making a new release at least provides people a stable package location with Postgres 16 support.
The text was updated successfully, but these errors were encountered:
Hi there,
It seems #10 is already fixed by 34fe30f and it's already back-ported to REL1_2_STABLE branch.
Would it make sense to tag the current REL1_2_STABLE branch and create a new release with it?
I'm aware that the full migration to GitHub is still being planned, but making a new release at least provides people a stable package location with Postgres 16 support.
The text was updated successfully, but these errors were encountered: