Skip to content

Conversation

@tdrz
Copy link
Collaborator

@tdrz tdrz commented Dec 16, 2025

Changes needed to make pgcrypto contrib extension work.

@tdrz tdrz requested a review from samwillis December 16, 2025 16:11
@reneleonhardt
Copy link

Thank you for developing this fork!

Would it be possible to upgrade to Postgres 18.1 or 17.7, maybe by using gitmodule instead of file copies?

ES6 is 10 years old, would it be beneficial to upgrade to ES2025?

Would it be possible to publish tags, releases and assets like .wasm binaries? 🙂

@tdrz
Copy link
Collaborator Author

tdrz commented Dec 18, 2025

Would it be possible to upgrade to Postgres 18.1 or 17.7, maybe by using gitmodule instead of file copies?

Are you interested in a particular feature of 17.7 or 18+ of Postgres?

ES6 is 10 years old, would it be beneficial to upgrade to ES2025?

Unsure, we will have to see what this means for backwards compatibility.

Would it be possible to publish tags, releases and assets like .wasm binaries? 🙂

Tags are published on the main repo https://github.com/electric-sql/pglite/
Assets are published for each CI run, see artifacts: https://github.com/electric-sql/pglite/actions/runs/20277798563

Copy link
Collaborator

@samwillis samwillis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks all good.

Couple of merge conflicts, and make sure CI is green.

@tdrz tdrz merged commit bee4a36 into REL_17_5_WASM-pglite-builder Jan 6, 2026
@tdrz tdrz deleted the tdrz/be-pgcrypto branch January 6, 2026 12:26
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.

4 participants