Skip to content

release: v1.3.0 to prd - #239

Merged
amenegola merged 1 commit into
mainfrom
release/v1.3.0
Nov 17, 2026
Merged

amenegola merged 1 commit into
mainfrom
release/v1.3.0

Conversation

@amenegola

Copy link
Copy Markdown
Collaborator

Release v1.3.0 to prd. Part of #173.

This PR changes what prd deploys. Nothing is applied by merging it: the apply runs afterwards, unit by unit, following the release runbook.

Changes

  • release/prd.yaml: v1.2.0 → v1.3.0, promoted by digest from dev-0dcd306 (the current main). All six images were built at that commit, deployed to dev and passed esmeralda verify --env dev (gateway probes, registry egress, specialist and orchestrator queries), verify --partner and esmeralda build --verify --env dev. envoy-gateway is listed because promotion requires every Layer 5 image; prd doesn't deploy Envoy.
  • infrastructure/live/prd/env.yaml: legacy_shared_invoker = true for the native Agent Identity rollout, phase A (additive: the shared invoker stays until both agents run the new images). A follow-up PR sets it back to false (phase B).
  • infrastructure/live/prd/layer-4-governance/terragrunt.hcl: alert_on_unattributed_usage = false in prd while verified attribution (attribution.caller_guard) is off, so the alert doesn't page on normal traffic.

Checks

  • make test-all (unit tests, guards, Terraform validation, gateway harness, Apigee conformance) passes.
  • esmeralda guard --diff origin/main...HEAD passes.
  • A read-only esmeralda plan --all --env prd at this commit matches the expected changes listed in Release v1.3.0 to prd #173 (no unexpected destroy or replace, no notification channel change).

After merge

Layers 1–2, then Layer 4 (runaway-loop alert first), iap-egress, identity phase A (Layer 3, MCP services, specialist, orchestrator), then phase B in a follow-up PR. verify --env prd after each group, then tags v1.2.0 (backfill) and v1.3.0 and the GitHub release.

@amenegola
amenegola merged commit 13c778f into main Nov 17, 2026
7 checks passed
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