Skip to content

[codex] Ensure stateful builds use deployment target#48

Merged
arjunkomath merged 1 commit into
mainfrom
feat/stateful-build-target-builds
Jun 25, 2026
Merged

[codex] Ensure stateful builds use deployment target#48
arjunkomath merged 1 commit into
mainfrom
feat/stateful-build-target-builds

Conversation

@arjunkomath

Copy link
Copy Markdown
Member

Summary

  • Route stateful service builds to the single active replica server instead of the locked server or any same-arch build server.
  • Resolve stateful target platforms from that active deployment target and fail early when the target server is missing, offline, or missing architecture metadata.
  • Keep stateless multi-arch build assignment behavior, including allowed build server filtering.

Why

Stateful services should build on the same machine that will deploy/run them. The previous path could fall back to generic architecture matching when a stateful service was not yet locked, which could build on a different machine from the deployment target.

Validation

  • pnpm test
  • pnpm exec tsc --noEmit
  • git diff --check
  • Global Smart Review pass outside sandbox, with review feedback addressed in tests and helper cleanup.

@arjunkomath arjunkomath marked this pull request as ready for review June 25, 2026 01:53
@arjunkomath arjunkomath merged commit 6d35178 into main Jun 25, 2026
8 checks passed
@arjunkomath arjunkomath deleted the feat/stateful-build-target-builds branch June 25, 2026 01:54
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