| name | component-release |
| description | Prepares a verifiable GPT-RAG UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval. |
GPT-RAG UI component release
- Start from the current
develop branch and create release/X.Y.Z.
- Choose a semantic version from the shipped change set. Do not change
VERSION on develop merely to anticipate a release.
- Set root
VERSION to X.Y.Z without a v prefix.
- Keep one empty
## [Unreleased] section at the top of CHANGELOG.md and
convert the accumulated entries into ## [vX.Y.Z] - YYYY-MM-DD.
- Verify the branch name,
VERSION, changelog heading, proposed tag
vX.Y.Z, and release title describe the same version.
- Run the complete existing test suite and any auth, accessibility,
deployment, or cross-repository validation required by the changes.
- Confirm documentation, migration, compatibility, and rollback status.
- Open the release pull request from
release/X.Y.Z to main.
- After merge and explicit human approval, create the tag and release using
the validated commit. Publishing images or deploying production requires
separate explicit approval.
- Record the release artifacts, evidence, compatibility assumptions, and
rollback path in the handoff.
Do not introduce unrelated feature work on a release branch. Never include
credentials, personal data, private environment names, tenant or subscription
identifiers, or internal endpoints in release artifacts.
