π¦ New version release#268
Merged
Merged
Conversation
brentrager
force-pushed
the
changeset-release/main
branch
from
July 25, 2026 20:16
5c76eab to
8b78f50
Compare
brentrager
enabled auto-merge (squash)
July 25, 2026 20:16
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 publish to npm yourself or setup this action to publish 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
@smooai/smooth@0.23.3
Patch Changes
da9afac: Pearl store: unified backoff+jitter retry on the read-only lock-flap
(pearl th-e979ac).
The transient
Error 1105: cannot update manifest: database is read onlyβ a concurrent writer (usually another agent's push) briefly holding the
single-writer lock β used to fail fast in CLI mode (auto-doctor found no
orphan β immediate error) and after one respawn in server mode. Now every
dolt write funnels through a single
retry_on_lock_flaphelper that:smooth-dolt serve; server: force-respawn a wedged child), thenbudget elapses (
SMOOTH_DOLT_LOCK_RETRY_BUDGET_SECS, default 30s).This consolidates the two former one-shot ad-hoc retries into one place
and covers
th pearlscreate/update/close,th msg send/reply, push,and memory writes alike β so a momentary collision with a peer's in-flight
push is waited out transparently instead of surfacing. Non-lock errors
(syntax, transport, corruption) still propagate immediately; a genuinely
stuck store returns a clear error with a
th pearls doctor --reaphintrather than hanging. The th-mail skill's hand-rolled retry guidance is
dropped since the store now self-heals the flap. No new dependency (jitter
from
SystemTime).