Repository navigation
Upgrade the Atomic harness to 0.9.33 - #467
Merged
Merged
Conversation
Moves the Atomic harness to 0.9.33, which fixes Atomic's managed PostgreSQL cluster being refused with "Managed Postgres cluster identity mismatch" after a macOS reboot changes the data volume's device number (bastani-inc/atomic#3555). Atomic then fell back to its non-durable in-memory workflow backend, so Planner workflow runs on a self-hosted macOS Chopin lost the durable run state that lets an interrupted run be resumed from a later session. Atomic now reattaches the cluster when the data directory inode, path, cluster ID, major version and PostgreSQL system identifier still match, and a genuine mismatch names the fields that differ. 0.9.33 also makes the interactive terminal's program status (OSC 7501) report workflow runs (bastani-inc/atomic#3556). Chopin runs Atomic through its headless SDK, so that change does not reach it. No Chopin code changes: the SDK and workflow type declarations Chopin imports are unchanged between 0.9.32 and 0.9.33. bun.lock moves @bastani/atomic, @bastani/atomic-natives (all eight platform packages) and @bastani/pi-ai to 0.9.33. Atomic's other dependencies, including the @earendil-works packages at 1.1.0, are unchanged. No patch targets these packages; the existing patches still apply. docs/self-hosting.md now says 0.9.33. Assistant-model: Claude Opus 5.5 (fast) Assistant-workflow: inline (worker subagent) Assistant-verification: bun install passed: lockfile moves only the @Bastani packages to 0.9.33, patches applied Assistant-verification: bun run types passed: all workspace checks and e2e Assistant-verification: bun test passed: 4587 pass, 4 skip, 0 fail (GIT_CONFIG_GLOBAL=/dev/null) Assistant-verification: bun run ci passed: dprint, oxlint (31 warnings, 0 errors), tokens, design contract, design record, Impeccable (no new findings) Assistant-verification: Atomic contract suite passed: atomic.contract.test.ts 22 pass, 0 fail Co-authored-by: Alex Lavaee <alexlavaee@microsoft.com>
|
I'd appreciate if your AI generated comments would stop tagging me |
Collaborator
Author
Fixed, it's a good username 😅 |
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
2 participants
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.
Upgrade the Atomic harness to 0.9.33
Moves the Atomic harness to 0.9.33, which fixes Atomic's managed
PostgreSQL cluster being refused with "Managed Postgres cluster identity
mismatch" after a macOS reboot changes the data volume's device number
(bastani-inc/atomic#3555). Atomic then fell back to its non-durable
in-memory workflow backend, so Planner workflow runs on a self-hosted
macOS Chopin lost the durable run state that lets an interrupted run be
resumed from a later session. Atomic now reattaches the cluster when the
data directory inode, path, cluster ID, major version and PostgreSQL
system identifier still match, and a genuine mismatch names the fields
that differ.
0.9.33 also makes the interactive terminal's program status (OSC 7501)
report workflow runs (bastani-inc/atomic#3556). Chopin runs Atomic
through its headless SDK, so that change does not reach it.
No Chopin code changes: the SDK and workflow type declarations Chopin
imports are unchanged between 0.9.32 and 0.9.33. bun.lock moves
@bastani/atomic,@bastani/atomic-natives(all eight platform packages)and
@bastani/pi-aito 0.9.33. Atomic's other dependencies, including the@earendil-workspackages at 1.1.0, are unchanged. No patch targets thesepackages; the existing patches still apply. docs/self-hosting.md now says
0.9.33.
Assistant-model: Claude Opus 5.5 (fast)
Assistant-workflow: inline (worker subagent)
Assistant-verification: bun install passed: lockfile moves only the
@bastanipackages to 0.9.33, patches appliedAssistant-verification: bun run types passed: all workspace checks and e2e
Assistant-verification: bun test passed: 4587 pass, 4 skip, 0 fail (GIT_CONFIG_GLOBAL=/dev/null)
Assistant-verification: bun run ci passed: dprint, oxlint (31 warnings, 0 errors), tokens, design contract, design record, Impeccable (no new findings)
Assistant-verification: Atomic contract suite passed: atomic.contract.test.ts 22 pass, 0 fail
Co-authored-by: Alex Lavaee alexlavaee@microsoft.com