Repository navigation
Upgrade Atomic to the stable 0.9.75 release - #807
Merged
Merged
Conversation
Moves the Atomic harness from 0.9.74 to the stable 0.9.75 release, and refreshes every other dependency in bun.lock to the newest version its range allows. Versions. catalog:harness pins `@bastani/atomic` 0.9.75. The lockfile resolves `@bastani/atomic`, `@bastani/atomic-natives` with its platform packages, and `@bastani/pi-ai` at 0.9.75, with no older `@bastani` package left. Atomic 0.9.75 names a stage it holds between turns `suspended` instead of `waiting`. A Planner's run card still shows such a stage as running, and an event recorded by an older Atomic that says `waiting` still reads the same way. Assistant-model: Claude Opus 5.5 Assistant-workflow: inline Assistant-verification: bun test unit passed: the suspended case in apps/server/src/harness/atomic/full.test.ts fails without the mapping and passes with it, and the waiting case still passes Assistant-verification: bun test passed with PostgreSQL: TEST_DATABASE_URL on a disposable PostgreSQL, GIT_CONFIG_GLOBAL=/dev/null bun test, 7993 tests, 0 fail, 17 skip Assistant-verification: typecheck and lint passed: bun run types and bun run ci User-preference: Keep everything on the latest Atomic and redeploy as new versions come out 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.74 to the stable 0.9.75 release, and
refreshes every other dependency in bun.lock to the newest version its
range allows.
Versions. catalog:harness pins
@bastani/atomic0.9.75. The lockfileresolves
@bastani/atomic,@bastani/atomic-nativeswith its platformpackages, and
@bastani/pi-aiat 0.9.75, with no older@bastanipackageleft.
Atomic 0.9.75 names a stage it holds between turns
suspendedinstead ofwaiting. A Planner's run card still shows such a stage as running, and anevent recorded by an older Atomic that says
waitingstill reads the sameway.
Assistant-model: Claude Opus 5.5
Assistant-workflow: inline
Assistant-verification: bun test unit passed: the suspended case in apps/server/src/harness/atomic/full.test.ts fails without the mapping and passes with it, and the waiting case still passes
Assistant-verification: bun test passed with PostgreSQL: TEST_DATABASE_URL on a disposable PostgreSQL, GIT_CONFIG_GLOBAL=/dev/null bun test, 7993 tests, 0 fail, 17 skip
Assistant-verification: typecheck and lint passed: bun run types and bun run ci
User-preference: Keep everything on the latest Atomic and redeploy as new versions come out
Co-authored-by: Alex Lavaee lavaman131@github.com