PolarionMcpServers: Command for Claude Code

Release Process

You are performing a release from develop to main. Follow these steps exactly:

Step 1: Verify Clean State

• Check out develop and fast-forward it to origin/develop
• Ensure there are no uncommitted changes (except appsettings.Development.json)
• Ensure gh auth status shows the account with push rights to peakflames/PolarionMcpServers as active

Step 2: Get Current Version

• Read the <Version> tag from PolarionRemoteMcpServer/PolarionRemoteMcpServer.csproj
• This is the version being released (e.g., 0.12.0)
• Confirm PolarionMcpServer/PolarionMcpServer.csproj <Version> and the Remote project's <ContainerImageTag> match it

Step 3: Verify the Build

Per the project CLAUDE.md verification rule:

python build.py start
python build.py mcp ping
python build.py mcp tools
python build.py log --level error
python build.py stop

Step 4: Promote the CHANGELOG

Follow docs/changelog-generation-rules.md:

• Review ## [Unreleased] against git diff v{PREVIOUS_VERSION}..develop. Entries must describe the net change since the last release only — drop or rewrite any entry that describes an intermediate state introduced and changed again within the same release cycle
• Insert ## [{VERSION}] - YYYY-MM-DD directly below ## [Unreleased], leaving [Unreleased] empty (never delete it)
• Update the link references at the bottom of the file:

  [Unreleased]: https://github.com/peakflames/PolarionMcpServers/compare/v{VERSION}...HEAD
  [{VERSION}]: https://github.com/peakflames/PolarionMcpServers/compare/v{PREVIOUS_VERSION}...v{VERSION}
  

git add CHANGELOG.md
git commit -m "chore(release): version {VERSION} and promote CHANGELOG Unreleased entries"
git push origin develop

Step 5: Merge to Main

git checkout main
git pull origin main
git merge develop --no-ff -m "Merge branch 'develop' into main for v{VERSION} release"

Step 6: Tag the Release

git tag -a v{VERSION} -m "Release v{VERSION}"