Skip to main content

service-release

Prepares and validates agent-app-ingestion releases. Use for release branches, VERSION, changelog entries, compatible Agent Landing Zone pins, tags, images, and GitHub Release notes.

Datos de origen

Repositorio
Azure/agent-app-ingestion
Última actividad en el origen
8 de octubre de 2026 a las 00:39
Idioma detectado de SKILL.md
inglés
Estrellas
188
Forks
102

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Mostrando SKILL.md

SKILL.md
Instrucciones de origen · Vista previa de solo lectura
name
service-release
description
Prepares and validates agent-app-ingestion releases. Use for release branches, VERSION, changelog entries, compatible Agent Landing Zone pins, tags, images, and GitHub Release notes.
# Ingestion service release Read `.github/copilot-instructions.md` completely before changing a release artifact. 1. Determine the intended semantic version and create `release/x.y.z` from `develop`. 2. Set root `VERSION` to `x.y.z` without `v`. 3. Replace the staged `## [Unreleased]` heading with `## [vX.Y.Z] - YYYY-MM-DD`; do not add a new `Unreleased` section on the release branch. 4. Verify branch, `VERSION`, changelog, Git tag, and GitHub Release title are synchronized. 5. Identify the compatible Azure/agent-landing-zone umbrella and component versions and validate the exact ingestion commit or image in that context. 6. Record Python, frontend, container, and controlled Azure evidence required by the changed behavior. 7. Confirm documentation status and rollback or roll-forward steps. 8. Target the release pull request to `main`. 9. After merge, create exactly `vX.Y.Z` for the tag and release title only with explicit human approval. 10. Re-fetch the release and verify formatting and the absence of private Azure environment or resource-group names. After the release, recreate the empty `Unreleased` section separately on `develop`. Report incompatible contracts, missing validation, or documentation drift as blockers rather than filling gaps by assumption.
Ver en GitHub