Agent Landing Zone multi-repository release
Read .github/copilot-instructions.md completely before changing a release
artifact. Its branching, versioning, changelog, and release-note requirements
are authoritative.
- Determine the intended semantic version and create the release branch from
developusingrelease/x.y.z. - Update
manifest.jsontagtovX.Y.Zand verify it matches the release branch version, changelog heading, Git tag, and GitHub Release title. - Read every runtime component tag from
manifest.jsoncomponents[]and the infrastructure provenance frominfra.source(repo,tag,commit); never copy a previous version table. Align the bundledapp-definition.jsonsource commits and the exact component-pin review ininfra/tests/contracts/fixtures/incorporated-foundation-normalization.jsonin the same change. Run the release gate against the real loaded application definition, not just the manifest values. infra/is repository-owned source (no submodule). Keepmanifest.jsoninfra.sourceequal to the AI Landing Zone release the in-repositoryinfra/was incorporated from, and validate the exactinfra/tree being released.- Confirm that the exact pinned combination was validated and record the relevant commands and Azure deployment mode without private environment or resource group names.
- Replace
[Unreleased]with## [vX.Y.Z] - YYYY-MM-DDfor the release. - Keep
CHANGELOG.mdand GitHub Release notes consistent, including the full required component version table. - Use exactly
vX.Y.Zfor both the tag and GitHub Release title. - Target the release pull request to
main. - Re-fetch published release notes and verify headings, lists, tables, and the
absence of private
gptrag-*andrg-gptrag-*validation names.
Do not publish a tag, release, package, image, or production deployment without explicit human approval. Report incompatible pins, missing validation, or documentation drift as blockers rather than filling gaps by assumption.
