Skip to content

Upgrade Atomic to the stable 0.9.70 release - #766

Merged
lavaman131 merged 1 commit into
mainfrom
chore/atomic-0.9.70
Nov 3, 2026
Merged

lavaman131 merged 1 commit into
mainfrom
chore/atomic-0.9.70

Conversation

@lavaman131

Copy link
Copy Markdown
Collaborator

Moves the Atomic harness from 0.9.69 to the stable 0.9.70 release.

Versions. catalog:harness pins @bastani/atomic 0.9.70. The lockfile
resolves @bastani/atomic, @bastani/atomic-natives with its platform
packages, and @bastani/pi-ai at 0.9.70, with no older @bastani package
left. Atomic's own dependencies come from the shrinkwrap it publishes.

An atomic Planner runs Atomic in process; the harness tests pass unchanged.

Assistant-model: Claude Opus 5.5
Assistant-workflow: inline
Assistant-verification: bun test unit passed: GIT_CONFIG_GLOBAL=/dev/null bun test src/harness
Assistant-verification: typecheck and lint passed: bun run types and bun run ci
Co-authored-by: Alex Lavaee lavaman131@github.com

Moves the Atomic harness from 0.9.69 to the stable 0.9.70 release.

Versions. catalog:harness pins `@bastani/atomic` 0.9.70. The lockfile
resolves `@bastani/atomic`, `@bastani/atomic-natives` with its platform
packages, and `@bastani/pi-ai` at 0.9.70, with no older `@bastani` package
left. Atomic's own dependencies come from the shrinkwrap it publishes.

An atomic Planner runs Atomic in process; the harness tests pass unchanged.

Assistant-model: Claude Opus 5.5
Assistant-workflow: inline
Assistant-verification: bun test unit passed: GIT_CONFIG_GLOBAL=/dev/null bun test src/harness
Assistant-verification: typecheck and lint passed: bun run types and bun run ci
Co-authored-by: Alex Lavaee <lavaman131@github.com>
@lavaman131
lavaman131 merged commit 3d18a7b into main Nov 3, 2026
24 checks passed
@lavaman131
lavaman131 deleted the chore/atomic-0.9.70 branch November 3, 2026 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant