Versioning standard now documents the MR flow: bump pyproject.toml/VERSION and promote CHANGELOG in the MR (referencing the version/tag, not a commit id), merge/squash, then tag the resulting commit. Adds the agent-assisted tagging procedure (wait for the go-ahead, find the version-bump commit, tag only it, ask the user to push) to both the reference page and the releasing wiki runbook. Adds the repo inventory (src/repos.json -> mcp/repos.json), the registry://repos resource + list_repos tool, the 15_repository_inventory lib page, and two MCP prompts: compliance (remediate repos) and release (agent tagging).
38 lines
793 B
Markdown
38 lines
793 B
Markdown
# Changelog
|
|
|
|
All notable changes to this project are documented here.
|
|
|
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
|
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
|
|
## [Unreleased]
|
|
|
|
### Added
|
|
|
|
### Changed
|
|
|
|
### Deprecated
|
|
|
|
### Removed
|
|
|
|
### Fixed
|
|
|
|
### Security
|
|
|
|
<!--
|
|
In the release merge request, promote the entries above into a new heading and
|
|
leave a fresh, empty [Unreleased] section. Name the version/tag, never a commit
|
|
id:
|
|
|
|
## [0.1.0] - YYYY-MM-DD
|
|
|
|
### Added
|
|
- Initial release.
|
|
|
|
Then update the compare links below. The tag is created on the merged commit —
|
|
see the standard: Versioning & Changelog (registry://release).
|
|
-->
|
|
|
|
[Unreleased]: <repo-url>/compare/0.1.0...HEAD
|
|
[0.1.0]: <repo-url>/releases/tag/0.1.0
|