Skip to content

Release v0.45.0#191

Merged
arjunkomath merged 64 commits into
releasefrom
automation/release/v0.45.0
Jul 25, 2026
Merged

Release v0.45.0#191
arjunkomath merged 64 commits into
releasefrom
automation/release/v0.45.0

Conversation

@github-actions

Copy link
Copy Markdown

Automated release PR.

Version: v0.45.0
Base: release
Source: main

Merging this PR will tag the merge commit as v0.45.0 and dispatch the release workflow.

@github-actions github-actions Bot added the release-pr Automated release PR label Jul 23, 2026
ampagent and others added 15 commits July 23, 2026 12:47
Amp-Thread-ID: https://ampcode.com/threads/T-019f8f03-2036-7380-860a-e27fc3df0f6e

Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Add GPT-5.6 Sol xhigh agent mode
Amp-Thread-ID: https://ampcode.com/threads/T-019f8f0b-e5a5-7319-83a5-dd4a4fd78f49

Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
arjunkomath and others added 23 commits July 24, 2026 21:37
During fast deploys, a status report could snapshot a container in
podman's 'created' state. The agent mapped any non-running/non-exited
state to 'stopped', and the control plane moved the deployment to an
observedPhase of 'stopped' that non-serverless deployments never
recovered from, so rollouts timed out after 10 minutes despite the
container running fine.

Agent: skip containers in transient states in the status report,
matching the existing log-collector filter; they get reported on a
later tick once they settle.

Control plane: allow any desired-running deployment stuck in a
stopped/sleeping phase (previously serverless-only) to be promoted
back to ready when its container reports running, and when it belongs
to a rollout, emit resource/status-changed and a rollout log so the
waiting workflow unblocks immediately.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Omitting transient-state containers from the status report made the
control plane treat them as absent: attached deployments were marked
unknown and removed deployments were deleted while their container
still existed. The unknown -> running recovery then emitted no
resource/status-changed event, so a rollout could still stall for the
full waitForEvent timeout.

The agent now reports these containers with status "transient"; the
control plane counts them as reported (no unknown-marking, no early
deletion) but skips all phase and health transitions until the state
settles. The unknown -> running restore path now also sets the
ready-transition flag so rollouts are notified after persistence.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Use separate CLI config for development builds
The transient default swallowed settled states: a paused, stopped, or
unknown-state container would be reported presence-only forever,
leaving a previously healthy deployment marked ready and routable.

Reserve "transient" for intended intermediates (created, configured,
initialized, stopping, removing). Settled non-running states (stopped,
paused) and unknown/unrecognized states now map to stopped — the
deployment leaves routing and drift reconciliation can repair it, with
unexpected states logged for visibility.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Fix rollout health-check timeouts from transient container states
- Compile Traefik routes, certificates, ports, and hashes once per expected-state snapshot so planning, application, and sync reporting share one representation.
- Type work-queue payloads by work type, including direct managed-upgrade insertion.
- Reuse deployment-status classifications instead of repeating ready/starting phase checks.

Amp-Thread-ID: https://ampcode.com/threads/T-019f9175-c0fd-7330-96ae-d88f29592a56

Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Simplify routing state, work payloads, and status checks
Re-adds the agent guide dropped in the rework of #204: project facts
(unreleased beta, no compat shims), repo map, verified commands, and
run restrictions. CLAUDE.md symlinks to it so Claude Code loads it
automatically.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019f964d-30a3-7407-b18f-23692b93b328

Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019f96c4-1a7d-7199-873b-94867b6c3437

Co-authored-by: Arjun Komath <arjunkomath@gmail.com>
@arjunkomath
arjunkomath marked this pull request as ready for review July 25, 2026 03:39
@arjunkomath
arjunkomath merged commit cb55e44 into release Jul 25, 2026
23 checks passed
@arjunkomath
arjunkomath deleted the automation/release/v0.45.0 branch July 25, 2026 03:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release-pr Automated release PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants