Skip to content

fix(configurator): preserve running app during release staging - #268

Merged
lweberru merged 1 commit into
mainfrom
fix/cf-staging-without-stop
Nov 17, 2026
Merged

lweberru merged 1 commit into
mainfrom
fix/cf-staging-without-stop

Conversation

@lweberru

Copy link
Copy Markdown
Collaborator

Application staging stopped the running Configurator because the pinned CF CLI treats push --no-start as a request to stop an already started app. The v2.1.1 Dev rollout recovered after activation, but its shared staging path would also interrupt production replicas.

Apply the redacted manifest and upload the package separately before staging the verified droplet. Existing app processes can continue serving until the existing gated activation. Migration/Runner checks, disabled staging execution, immutable source binding and production rolling activation remain required. Update both production runbooks and the unpublished v2.1.1 notes.

Validation: 37 focused lifecycle, production, preparation, artifact and image staging tests pass; shell syntax and diff checks pass. New fixtures execute the actual staging shell helper and reject activation/stop commands, failed uploads and mismatched package/build evidence. Full corrected Dev rollout remains required before Prod promotion.

Closes #267.

@lweberru
lweberru merged commit 821d5fe into main Nov 17, 2026
16 checks passed
@lweberru
lweberru deleted the fix/cf-staging-without-stop branch November 17, 2026 14:02
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.

fix(configurator): keep running app available during release staging

1 participant