chore: version packages #1379
Merged
chore: version packages #1379
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
665f867 to
3e9cb6d
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
3e9cb6d to
4542807
Compare
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
[email protected]
Patch Changes
#1381
dae8801ea3ddf732d8284ff84bc7dc21ada22f0eThanks @typedarray! - Fixed a bug where data inserted using raw SQL near the beginning of historical indexing was not found by subsequentfind,update, ordeleteoperations using the store/in-memory API.#1375
1687033a74fb8e7a7d843b4fe1f7f1cd4cf866a9Thanks @typedarray! - Improved logs for Postgres pool errors.[email protected]
[email protected]