Repository navigation
fix(deps): update dependency @electric-sql/pglite to ^0.5.0 - #749
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
2 times, most recently
from
August 29, 2026 19:49
56439ce to
c055847
Compare
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
from
September 3, 2026 00:19
c055847 to
1e9850a
Compare
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
from
September 15, 2026 11:24
1e9850a to
3337bc7
Compare
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
2 times, most recently
from
September 30, 2026 17:53
509640f to
e802a0a
Compare
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
2 times, most recently
from
October 12, 2026 12:18
73b65c7 to
f77df1d
Compare
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
2 times, most recently
from
October 20, 2026 10:01
d4132d1 to
33eacac
Compare
renovate
Bot
force-pushed
the
renovate/electric-sql-pglite-0.x
branch
from
October 22, 2026 19:08
33eacac to
5fb28d4
Compare
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 contains the following updates:
^0.3.15→^0.5.0Release Notes
electric-sql/pglite (@electric-sql/pglite)
v0.5.11Compare Source
Patch Changes
5573bb0: bug fix: check ready before close2372f39: Update submodule4321a41: Fix premature ReadyForQuery responses after extended-query errors, preventing PostgreSQL clients from desynchronizing before Sync.v0.5.10Compare Source
Patch Changes
367ee2f: Bug fix: wait for running queries to finish before doing a data dir dumpcb06c21: Wait for queries to finish before closing PGlite instance. See #112878012ca: Fix a windowedlive.query(one givenoffsetandlimit) leaking itslive_query_<id>_get_total_countprepared statement onunsubscribe. Onlylive_query_<id>_getwas deallocated, so the count statement survived every teardown while its backing view was dropped, accumulating dangling prepared statements for the lifetime of the database.v0.5.9Compare Source
Patch Changes
389b731: upgrade to PostgreSQL 18.6389b731: Export additional core symbols from the main WASM module required by the plpgsql_check extensionv0.5.8Compare Source
Patch Changes
c771db3: Do not set process.exitCode at allv0.5.7Compare Source
Patch Changes
2f9cf75: Fix convert_tov0.5.6Compare Source
Patch Changes
69b7d87: Apply the second options argument when callingPGlite.create(undefined, options).6c14380: fixes for process.exitCodev0.5.5Compare Source
Patch Changes
a290741: Reset retained protocol parser state after a malformed backend message so later queries can recover.6b6f28d: FixPGlite.create({ fs })on a fresh database calling the provided filesystem'sinit()twice: the inner initdb instance no longer inherits the user-providedfsand always runs on its own scratch filesystem. Previously any VFS holding exclusive resources (e.g. OPFS sync access handles) failed with a contention error on first create.354f4ae: FixformatQuery(used bylive.query/live.incrementalQueryto inline parameters) emitting%NLinstead of the positional%N$Lformat specifier. A bare%NLis "min width N" and consumesformat()arguments sequentially, so placeholders that are out of textual order silently bound the wrong values, and repeated placeholders failed withtoo few arguments for format().219af1e: Expose the fields node-postgres derives from the CommandComplete command tag onResults:command(e.g.SELECT,INSERT,CREATE), androwCount(the per-statement count from the tag). The tag was already received and parsed internally to computeaffectedRows, but these values were not surfaced. Matching node-postgres'command/rowCountresult fields lets pg-compatible adapters report them without re-parsing SQL.20839a7: Preserve the hostprocess.exitCodewhen closing a PGlite instance.close()calls_emscripten_force_exit(0), whose Emscripten runtime setsprocess.exitCode = 0, clobbering any exit code the host process had already set. This mirrors the existing save/restore guards in#init()andexecProtocolRaw(), so closing a database no longer silently resets the host process's exit code.7e784a4: Reject operations performed through transaction handles after the transaction has closed.v0.5.4Compare Source
Patch Changes
7e0d6d1: Detect the Node environment viaprocess.typeinstead ofprocess.versions.electron. The previous Electron guard (#951) also treated the Electron main and utility processes as non-Node, which broke PGlite's filesystem code path there.process.typeonly excludes Electron's web contexts (renderer, web worker, service worker), so PGlite keeps using the Node.js path in the Electron main and utility processes. Follow-up to #951 / #813.v0.5.3Compare Source
Patch Changes
2ccbb4c: Improve parsing/raw results handlingv0.5.2Compare Source
Patch Changes
21fc995: fix serializing arrays of BigInts0720cb6: Alow serializing untyped parameterse09535f: add pg_stat_statements.tar.gz to main packagea4e163a: fix process exit code set/restorev0.5.1Compare Source
Patch Changes
5573bb0: bug fix: check ready before close2372f39: Update submodule4321a41: Fix premature ReadyForQuery responses after extended-query errors, preventing PostgreSQL clients from desynchronizing before Sync.v0.5.0Minor Changes
93d50aa: Upgrade to Postgres 18.3; move other extensions to their own npm packages;v0.4.6Patch Changes
2aa4d1a: Allow parsing of nulls in arrays #9972095d4e: Add ICU support.e937669: Restore process.exitCode54ed6dc: new API method copyToFs() and new param postgresqlconf817d073: restore exit codev0.4.5Compare Source
Patch Changes
c6bddde: Fix caching of artifacts such that they are not downloaded multiple timesv0.4.4Compare Source
Patch Changes
b88c5c3: Disable checkpointerv0.4.3Compare Source
Patch Changes
2ae666f: Default database, user and role are now all "postgres"fb95e66: Allow setting initial memory size.65fc101: Disable background workers.v0.4.2Compare Source
Patch Changes
41632c4: Allow passing initdb.wasm asset for bundlers that need it.v0.4.1Patch Changes
37fb39e: clear timers on exit; remove pglite-socket dependency on pglite-postgisv0.4.0Minor Changes
d848955: New simplified PGlite with separate initdb.New included extension: pg_textsearch (experimental).
New package for postgis (experimental) as extension.
Breaking changes: 'postgres' is the default database instead of 'template1'.
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.