BitSight Community MCP Server

--- name: release description: Prep a release from a dev branch with an active PR argument-hint: Prepare current dev branch for release with minimal interaction, provide next_version agent: git tools: [ 'changes', 'github/github-mcp-server/get_commit', 'github/github-mcp-server/get_latest_release', 'github/github-mcp-server/get_release_by_tag', 'github/github-mcp-server/get_tag', 'github/github-mcp-server/list_branches', 'github/github-mcp-server/list_commits', 'github/github-mcp-server/list_releases', 'github/github-mcp-server/list_tags', 'github/github-mcp-server/push_files', 'runCommands' --- ## Goal Given context: you’re on a dev branch with multiple existing changes and an active PR Prepare the branch for release with minimal interaction ## Inputs (from user) - next_version (e.g., 4.0.0-alpha.3) ## Playbook ### Changelog up to date - Check [`CHANGELOG.md`](../../CHANGELOG.md) contains a section for `<next_version>` in the six-category format - If missing or style violations are obvious, state what's needed and stop ### Versions bumped - Confirm `pyproject.toml [project].version` equals `<next_version>` - Confirm runtime `__version__` exists in `src/birre/__init__.py` and equals `<next_version>` - If any of the versions are missing or incorrect, mention which files need updating and stop ### Run tests - Offline: `uv run pytest --offline` - Online: `uv run pytest --online-only` (assume `BITSIGHT_API_KEY` exported) - Online selftest: `uv run birre selftest --production` - If failures occur, report and stop ### Stage any updated artifacts - If tests or tooling updated tracked files (e.g., snapshots), include them ### Commit and push - Create commit: `Bump version to v<next_version>` including all staged files - Push the dev branch ### Next step for user - Instruct: Approve/merge the open PR into `main` - Provide tag command to run after the merge on the main branch: - Bash: `git tag v<next_version> && git push origin v<next_version>` ## Notes - Use `changes` to verify staged content - Use `push_files` to create the commit - Use `list_commits`/`get_commit` to report hashes - Keep responses concise: checks → actions → results