Skip to content

chore(deps): update dependency @electric-sql/pglite to v0.5.10 - #46

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/electric-sql-pglite-0.x
Open

renovate[bot] wants to merge 1 commit into
masterfrom
renovate/electric-sql-pglite-0.x

Conversation

@renovate

@renovate renovate Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@electric-sql/pglite (source) 0.5.8 → 0.5.10 age confidence

Release Notes

electric-sql/pglite (@​electric-sql/pglite)

v0.5.10

Compare Source

Patch Changes
  • 367ee2f: Bug fix: wait for running queries to finish before doing a data dir dump
  • cb06c21: Wait for queries to finish before closing PGlite instance. See #​1128
  • 78012ca: Fix a windowed live.query (one given offset and limit) leaking its live_query_<id>_get_total_count prepared statement on unsubscribe. Only live_query_<id>_get was 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.9

Compare Source

Patch Changes
  • 389b731: upgrade to PostgreSQL 18.6
  • 389b731: Export additional core symbols from the main WASM module required by the plpgsql_check extension

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Oct 12, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @nestjs/authentication@0.1.1
npm error Found: @electric-sql/pglite@0.5.10
npm error node_modules/@electric-sql/pglite
npm error   dev @electric-sql/pglite@"0.5.10" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @electric-sql/pglite@"0.5.8" from @electric-sql/pglite-socket@0.2.11
npm error node_modules/@electric-sql/pglite-socket
npm error   dev @electric-sql/pglite-socket@"0.2.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-15T21_14_46_392Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-15T21_14_46_392Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/electric-sql-pglite-0.x branch 5 times, most recently from 572fd7e to 4423d16 Compare October 14, 2026 18:02
@renovate renovate Bot changed the title chore(deps): update dependency @electric-sql/pglite to v0.5.9 chore(deps): update dependency @electric-sql/pglite to v0.5.10 Oct 14, 2026
@renovate
renovate Bot force-pushed the renovate/electric-sql-pglite-0.x branch from 4423d16 to 2f828eb Compare October 15, 2026 21:14
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.

0 participants