chore: publish new package versions#1044
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
1ba3ad5 to
2c1f3de
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
2c1f3de to
5de1e16
Compare
Contributor
Author
|
Contributor
Author
Contributor
Author
|
🚀 Deployed on https://6a467a04f63682af708076e0--pglite.netlify.app |
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
1 participant
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.4
Patch Changes
process.typeinstead ofprocess.versions.electron. The previous Electron guard (fix: exclude Electron renderer from IN_NODE detection #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 fix: exclude Electron renderer from IN_NODE detection #951 / Package does not work in electron due to current checks ofIN_NODE#813.@electric-sql/pglite-age@0.0.5
Patch Changes
@electric-sql/pglite-pg_hashids@0.0.5
Patch Changes
@electric-sql/pglite-pg_ivm@0.0.5
Patch Changes
@electric-sql/pglite-pg_textsearch@0.0.6
Patch Changes
@electric-sql/pglite-pg_uuidv7@0.0.5
Patch Changes
@electric-sql/pglite-pgmq@0.0.2
Patch Changes
@electric-sql/pglite-pgtap@0.0.5
Patch Changes
@electric-sql/pglite-pgvector@0.0.5
Patch Changes
@electric-sql/pglite-postgis@0.2.4
Patch Changes
@electric-sql/pglite-prepopulatedfs@0.5.4
Patch Changes
@electric-sql/pglite-react@0.4.4
Patch Changes
@electric-sql/pglite-repl@0.4.4
Patch Changes
@electric-sql/pglite-socket@0.2.7
Patch Changes
@electric-sql/pglite-sync@0.6.5
Patch Changes
@electric-sql/pglite-tools@0.4.4
Patch Changes
@electric-sql/pglite-vue@0.4.4
Patch Changes