Repository navigation
chore(release): version packages - #24
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 23, 2026 17:41
8e98f7d to
048e8f2
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 24, 2026 22:29
048e8f2 to
2b448d7
Compare
This branch was successfully deployed
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
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies []:
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies []:
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies [
1cb1a7c]:@concile/[email protected]
Patch Changes
1cb1a7c]:@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies []:
@concile/[email protected]
Patch Changes
1cb1a7c]:@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
1cb1a7c]:@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies []:
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies [
1cb1a7c]:@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
#23
1cb1a7cThanks @dbjpanda! - Fix drivers that could never restart afterstop().Every component driver carries a
stoppedguard so an in-flight pass cannot resurrect the loop afterteardown.
stop()set it and nothing cleared it, so a laterstart()on the same instancere-subscribed to commits and then ignored all of them: no dispatch, no sweep, no error logged.
The fleet restarts drivers on the same instances. Drivers follow the default shard, so a node that
released that shard stopped them, and if it later re-acquired the shard after a peer died, its
scheduler, triggers, notifications and reapers came back dead. That is the intermittent fleet e2e
failure "tick chain to resume on the survivor": which node was the survivor depended on rendezvous
hashing over freshly chosen ports.
start()now clears the guard. The runtime's owndriversStartedflag was fixed for the same reasonearlier; this is the same defect one layer down.
Updated dependencies []:
@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
1cb1a7c]:@concile/[email protected]
Patch Changes
@concile/[email protected]
Patch Changes
@concile/[email protected]
@concile/[email protected]
@concile/[email protected]
@concile/[email protected]
@concile/[email protected]
@concile/[email protected]
@concile/[email protected]
Patch Changes
1cb1a7c]:[email protected]
Patch Changes
1cb1a7c]:[email protected]
Patch Changes
[email protected]
Patch Changes