Repository navigation
Upgrade Atomic to the stable 0.9.48 release - #732
Merged
Merged
Conversation
Moves the Atomic harness from 0.9.45 to the stable 0.9.48 release. Versions. catalog:harness pins @bastani/atomic 0.9.48. The lockfile resolves @bastani/atomic, @bastani/atomic-natives with its eight platform packages, and @bastani/pi-ai at 0.9.48, with no older @Bastani package left. Atomic's own dependencies move with it: @smithy/node-http-handler 4.13.0 and quickjs-wasi 3.6.3. Nothing else in the lockfile moves. What changed in Atomic, and what it means here. These affect an atomic Planner and its workflow runs; none needs a code change: - Rate limits: Retry-After is honored on every provider path, and an exhausted quota (HTTP 402) moves a turn to its next fallback model instead of retrying the same one. - Forked subagents no longer finish at once with the parent's last message as their output. - Local worker pools: a resumed run keeps its in-flight children, and journal writers no longer time out under contention. - Intercom (0.9.48): a restored session or resumed stage rejoins the groups it had joined. Assistant-model: Claude Opus 5.5 (fast) Assistant-workflow: inline Assistant-verification: bun test unit passed: GIT_CONFIG_GLOBAL=/dev/null bun test (6737 pass, 0 fail) Assistant-verification: typecheck and lint passed: bun run types and bun run ci User-preference: Keep Atomic and its transitive packages on the same release everywhere Co-authored-by: Alex Lavaee <lavaman131@github.com>
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.
Moves the Atomic harness from 0.9.45 to the stable 0.9.48 release.
Versions. catalog:harness pins @bastani/atomic 0.9.48. The lockfile
resolves @bastani/atomic, @bastani/atomic-natives with its eight platform
packages, and @bastani/pi-ai at 0.9.48, with no older @Bastani package
left. Atomic's own dependencies move with it: @smithy/node-http-handler
4.13.0 and quickjs-wasi 3.6.3. Nothing else in the lockfile moves.
What changed in Atomic, and what it means here. These affect an atomic
Planner and its workflow runs; none needs a code change:
exhausted quota (HTTP 402) moves a turn to its next fallback model
instead of retrying the same one.
message as their output.
journal writers no longer time out under contention.
groups it had joined.
Assistant-model: Claude Opus 5.5 (fast)
Assistant-workflow: inline
Assistant-verification: bun test unit passed: GIT_CONFIG_GLOBAL=/dev/null bun test (6737 pass, 0 fail)
Assistant-verification: typecheck and lint passed: bun run types and bun run ci
User-preference: Keep Atomic and its transitive packages on the same release everywhere
Co-authored-by: Alex Lavaee lavaman131@github.com