Version Packages - #2
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
30 times, most recently
from
July 25, 2026 03:42
19212f2 to
70f7cda
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
July 31, 2026 00:03
4a39ca4 to
fd6a811
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
24 times, most recently
from
August 10, 2026 02:13
2225bef to
9f4be74
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 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
@lucas-barake/effect-local@0.2.0
Minor Changes
#1
4b0d162Thanks @lucas-barake! - Initial release of Effect Local and its core, SQL, RPC, browser, and testing packages.Local first state uses optimistic mutations in local SQLite and an authenticated server reconciled mutation log. The
server assigns a dense total order to accepted mutations, exact retries return durable receipts, clients replay
pending work after catch up, and Effect Atom exposes reactive entities, queries, receipts, and status. Optional field
semantics cover counters and sets without making CRDT metadata part of ordinary state.
Authoritative history and terminal receipts have explicit retained targets and hard admission caps. Maintenance
publishes verified immutable state snapshots before reclaiming either prefix. Fresh or lagged clients durably stage
bounded snapshot pages, atomically install canonical state, and continue from the snapshot sequence. Expired receipt
watermarks preserve at most once execution after private results are reclaimed. Client receipts and accepted evidence
are bounded without deleting rows still required by pending mutations.
@lucas-barake/effect-local-browser@0.2.0
Minor Changes
#1
4b0d162Thanks @lucas-barake! - Initial release of Effect Local and its core, SQL, RPC, browser, and testing packages.Local first state uses optimistic mutations in local SQLite and an authenticated server reconciled mutation log. The
server assigns a dense total order to accepted mutations, exact retries return durable receipts, clients replay
pending work after catch up, and Effect Atom exposes reactive entities, queries, receipts, and status. Optional field
semantics cover counters and sets without making CRDT metadata part of ordinary state.
Authoritative history and terminal receipts have explicit retained targets and hard admission caps. Maintenance
publishes verified immutable state snapshots before reclaiming either prefix. Fresh or lagged clients durably stage
bounded snapshot pages, atomically install canonical state, and continue from the snapshot sequence. Expired receipt
watermarks preserve at most once execution after private results are reclaimed. Client receipts and accepted evidence
are bounded without deleting rows still required by pending mutations.
Patch Changes
4b0d162]:@lucas-barake/effect-local-rpc@0.1.0
Minor Changes
#1
4b0d162Thanks @lucas-barake! - Initial release of Effect Local and its core, SQL, RPC, browser, and testing packages.Local first state uses optimistic mutations in local SQLite and an authenticated server reconciled mutation log. The
server assigns a dense total order to accepted mutations, exact retries return durable receipts, clients replay
pending work after catch up, and Effect Atom exposes reactive entities, queries, receipts, and status. Optional field
semantics cover counters and sets without making CRDT metadata part of ordinary state.
Authoritative history and terminal receipts have explicit retained targets and hard admission caps. Maintenance
publishes verified immutable state snapshots before reclaiming either prefix. Fresh or lagged clients durably stage
bounded snapshot pages, atomically install canonical state, and continue from the snapshot sequence. Expired receipt
watermarks preserve at most once execution after private results are reclaimed. Client receipts and accepted evidence
are bounded without deleting rows still required by pending mutations.
Patch Changes
4b0d162]:@lucas-barake/effect-local-sql@0.2.0
Minor Changes
#1
4b0d162Thanks @lucas-barake! - Initial release of Effect Local and its core, SQL, RPC, browser, and testing packages.Local first state uses optimistic mutations in local SQLite and an authenticated server reconciled mutation log. The
server assigns a dense total order to accepted mutations, exact retries return durable receipts, clients replay
pending work after catch up, and Effect Atom exposes reactive entities, queries, receipts, and status. Optional field
semantics cover counters and sets without making CRDT metadata part of ordinary state.
Authoritative history and terminal receipts have explicit retained targets and hard admission caps. Maintenance
publishes verified immutable state snapshots before reclaiming either prefix. Fresh or lagged clients durably stage
bounded snapshot pages, atomically install canonical state, and continue from the snapshot sequence. Expired receipt
watermarks preserve at most once execution after private results are reclaimed. Client receipts and accepted evidence
are bounded without deleting rows still required by pending mutations.
Patch Changes
4b0d162]:@lucas-barake/effect-local-test@0.2.0
Minor Changes
#1
4b0d162Thanks @lucas-barake! - Initial release of Effect Local and its core, SQL, RPC, browser, and testing packages.Local first state uses optimistic mutations in local SQLite and an authenticated server reconciled mutation log. The
server assigns a dense total order to accepted mutations, exact retries return durable receipts, clients replay
pending work after catch up, and Effect Atom exposes reactive entities, queries, receipts, and status. Optional field
semantics cover counters and sets without making CRDT metadata part of ordinary state.
Authoritative history and terminal receipts have explicit retained targets and hard admission caps. Maintenance
publishes verified immutable state snapshots before reclaiming either prefix. Fresh or lagged clients durably stage
bounded snapshot pages, atomically install canonical state, and continue from the snapshot sequence. Expired receipt
watermarks preserve at most once execution after private results are reclaimed. Client receipts and accepted evidence
are bounded without deleting rows still required by pending mutations.
Patch Changes
4b0d162]: