Repository navigation
chore: publish new package versions - #1176
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 30, 2026 20:30
9faaf40 to
97b3609
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 30, 2026 21:12
97b3609 to
1ab5d61
Compare
Contributor
Author
|
Contributor
Author
Contributor
Author
|
Contributor
Author
|
🚀 Deployed on https://6ae53db5202c53f4209af0fb--pglite.netlify.app |
tdrz
approved these changes
Oct 31, 2026
This file contains hidden or 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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@electric-sql/pglite@0.5.14
Patch Changes
pglite.wasm,initdb.wasmandpglite.dataURLs when PGlite has to load them. PassingpgliteWasmModule,initdbWasmModuleandfsBundlenow works in bundles whereimport.meta.urlis undefined, such as an esbuild IIFE build.@electric-sql/pglite-age@0.0.15
Patch Changes
@electric-sql/pglite-hypopg@0.0.6
Patch Changes
@electric-sql/pglite-pg_hashids@0.0.15
Patch Changes
@electric-sql/pglite-pg_ivm@0.0.15
Patch Changes
@electric-sql/pglite-pg_partman@0.0.6
Patch Changes
@electric-sql/pglite-pg_repack@0.0.6
Patch Changes
@electric-sql/pglite-pg_textsearch@0.0.16
Patch Changes
@electric-sql/pglite-pg_uuidv7@0.0.15
Patch Changes
@electric-sql/pglite-pgaudit@0.0.6
Patch Changes
@electric-sql/pglite-pgmq@0.0.12
Patch Changes
@electric-sql/pglite-pgtap@0.0.15
Patch Changes
@electric-sql/pglite-plpgsql-check@0.0.6
Patch Changes
@electric-sql/pglite-postgis@0.2.14
Patch Changes
@electric-sql/pglite-pgvector@0.0.15
Patch Changes
@electric-sql/pglite-prepopulatedfs@0.5.14
Patch Changes
@electric-sql/pglite-react@0.4.14
Patch Changes
@electric-sql/pglite-repl@0.4.14
Patch Changes
@electric-sql/pglite-socket@0.2.17
Patch Changes
stop()already detached from touching the database again. A client socket that closed in the same event-loop turn asstop()queued its own detach, which ran afterdb.close()and failed with an unhandledTypeError: Cannot read properties of undefined (reading '_IsTransactionBlock').@electric-sql/pglite-sync@0.6.15
Patch Changes
@electric-sql/pglite-tools@0.4.14
Patch Changes
@electric-sql/pglite-vue@0.4.14
Patch Changes
@electric-sql/pglite-utils@0.0.5
Patch Changes