|
| 1 | +# Release v0.19.0 Instructions |
| 2 | + |
| 3 | +This document provides instructions for creating and publishing the v0.19.0 release of the GitHub MCP Server. |
| 4 | + |
| 5 | +## Option 1: Manual Workflow Dispatch (Recommended) |
| 6 | + |
| 7 | +A GitHub Actions workflow has been created to automate the release process. |
| 8 | + |
| 9 | +### Steps: |
| 10 | +1. Go to [Actions](https://github.com/LadyKerr/github-mcp-server/actions/workflows/create-release-v0.19.0.yml) |
| 11 | +2. Click "Run workflow" |
| 12 | +3. Select the `main` branch |
| 13 | +4. Click "Run workflow" button |
| 14 | +5. Wait for the workflow to complete |
| 15 | +6. Verify the release at https://github.com/LadyKerr/github-mcp-server/releases/tag/v0.19.0 |
| 16 | + |
| 17 | +## Option 2: Using gh CLI |
| 18 | + |
| 19 | +If you have `gh` CLI installed and authenticated: |
| 20 | + |
| 21 | +```bash |
| 22 | +# Set up variables |
| 23 | +TAG="v0.19.0" |
| 24 | +TITLE="GitHub MCP Server v0.19.0" |
| 25 | +TARGET_COMMIT="d216b545e91ca12d6b1bf204e7136aa93254bf82" |
| 26 | + |
| 27 | +# Create and publish the release |
| 28 | +gh release create "${TAG}" \ |
| 29 | + --repo LadyKerr/github-mcp-server \ |
| 30 | + --title "${TITLE}" \ |
| 31 | + --notes-file /tmp/release-body-v0.19.0.md \ |
| 32 | + --target "${TARGET_COMMIT}" |
| 33 | +``` |
| 34 | + |
| 35 | +The release notes file (`/tmp/release-body-v0.19.0.md`) has been prepared with the following content: |
| 36 | + |
| 37 | +```markdown |
| 38 | +# GitHub MCP Server 0.19.0 |
| 39 | + |
| 40 | +## 📚 Documentation |
| 41 | + |
| 42 | +- **Improved GHES/GHEC visibility in README** - Restructured documentation to better highlight GitHub Enterprise Server and GitHub Enterprise Cloud configuration, including fixing an error in the example URL. Addresses user feedback about lacking enterprise documentation. [#1210](https://github.com/github/github-mcp-server/pull/1210) by @tonytrg |
| 43 | + |
| 44 | +## ✨ New Features |
| 45 | + |
| 46 | +- **Optional unknown toolset handling** - Added ability to ignore unknown toolsets rather than raising an error, providing more flexible configuration options. [#1202](https://github.com/github/github-mcp-server/pull/1202) by @omgitsads |
| 47 | + |
| 48 | +## 🔧 Maintenance & Refactoring |
| 49 | + |
| 50 | +- **Consolidated pull request review tools** - Simplified the PR review tool interface by consolidating `create_and_submit_pull_request_review`, `create_pending_pull_request_review`, `submit_pending_pull_request_review`, and `delete_pending_pull_request_review` into a single `pull_request_review_write` tool with method parameters (`create`, `submit_pending`, `delete_pending`). Validated across models with no regressions. [#1192](https://github.com/github/github-mcp-server/pull/1192) by @almaleksia |
| 51 | + |
| 52 | +- **Simplified Registry release pipeline** - Streamlined the registry publication workflow to use version tag triggers instead of repository dispatch, eliminating the need for elevated permissions. Added 5-minute availability check for Docker images before MCP Registry publication to improve reliability. [#1204](https://github.com/github/github-mcp-server/pull/1204) by @MattBabbage |
| 53 | + |
| 54 | +--- |
| 55 | + |
| 56 | +**Full Changelog**: https://github.com/github/github-mcp-server/compare/v0.18.0...v0.19.0 |
| 57 | +``` |
| 58 | + |
| 59 | +## Option 3: GitHub Web UI |
| 60 | + |
| 61 | +1. Go to https://github.com/LadyKerr/github-mcp-server/releases/new |
| 62 | +2. Fill in the form: |
| 63 | + - **Tag**: `v0.19.0` |
| 64 | + - **Target**: Select `main` branch or commit `d216b545e91ca12d6b1bf204e7136aa93254bf82` |
| 65 | + - **Release title**: `GitHub MCP Server v0.19.0` |
| 66 | + - **Release notes**: Copy the markdown content from above |
| 67 | +3. Click "Publish release" |
| 68 | + |
| 69 | +## Verification |
| 70 | + |
| 71 | +After creating the release, verify: |
| 72 | +- Release is published at: https://github.com/LadyKerr/github-mcp-server/releases/tag/v0.19.0 |
| 73 | +- Tag `v0.19.0` exists pointing to commit `d216b545e91ca12d6b1bf204e7136aa93254bf82` |
| 74 | +- Release notes are properly formatted and all links work |
| 75 | +- Release is not marked as draft or pre-release |
| 76 | + |
| 77 | +## Notes |
| 78 | + |
| 79 | +- The release is based on commit `d216b545e91ca12d6b1bf204e7136aa93254bf82` on the `main` branch |
| 80 | +- This release does not trigger goreleaser as it's created directly without pushing a tag first |
| 81 | +- If you want goreleaser to build binaries, you'll need to push the tag first and let goreleaser create a draft, then edit it |
0 commit comments