chore: bump @e4a/pg-wasm to 0.6.0#70
Merged
Merged
Conversation
Tracks postguard pg-core-v0.6.0. Public TypeScript API surface is unchanged; only internal wasm-export symbol order shifted and ReadableStreamReaderMode became exported. Closes #69
![dobby-coder[bot]](https://avatars.githubusercontent.com/in/3365457?s=60&v=4){kind=small}
Contributor
Author
There was a problem hiding this comment.
LGTM (cannot self-approve; the bot account opened this PR). Verified locally on a clean clone: npm ci clean, npm run typecheck no errors, npm test 89/89 pass. CI green. Diff is limited to package.json + lockfile; the published TS surface of @e4a/pg-wasm is unchanged between 0.5.10 and 0.6.0.
rubenhensen
approved these changes
May 16, 2026
|
🎉 This PR is included in version 1.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Bumps
@e4a/pg-wasmfrom^0.5.10to^0.6.0, tracking the upstreampg-core-v0.6.0release.API impact
Diffed the published
web/index.d.tsbetween 0.5.10 and 0.6.0:ReadableStreamReaderModebecomingexported (was an internal alias).pg-core-v0.6.0release notes only mention README / doc-comment typo fixes.No call sites in this repo needed updating, and no follow-up issues are required in downstream consumers (postguard-website, postguard-business, postguard-outlook-addon, postguard-tb-addon).
Verification
Local run on a clean
npm install:npm run typecheck— no errorsnpm run build—tsdownproduces dist/index.mjs (1.03 MB)npm test— 89/89 tests pass in 9 filesReviewer quickstart
Closes #69