Skip to content

Release P5-T1: Prepare 0.4.0 release — CHANGELOG date and quality gate verification#146

Merged
SoundBlaster merged 4 commits intomainfrom
codex/feature/P5-T1-release-0.4.0
Mar 6, 2026
Merged

Release P5-T1: Prepare 0.4.0 release — CHANGELOG date and quality gate verification#146
SoundBlaster merged 4 commits intomainfrom
codex/feature/P5-T1-release-0.4.0

Conversation

@SoundBlaster
Copy link
Owner

Summary

  • Update CHANGELOG.md [0.4.0] date from placeholder 2026-02-20 to actual release date 2026-03-06
  • Verify all quality gates pass on current main HEAD before tag creation
  • Document exact manual release commands for human operator (tag push + CI/CD triggers PyPI and MCP Registry publish)

Quality Gates Verified (all PASS)

Gate Result
make test 785 passed, 5 skipped — 90.91% coverage (≥ 90% required)
make lint 0 ruff errors
make format-check 49 files already formatted
make typecheck mypy: 0 issues in 18 source files
make doccheck-all DocC sync clean across unstaged/staged/branch
make package-assets-check Web UI assets present in wheel + sdist

Release Artifact Status

Artifact Value
pyproject.toml version 0.4.0
server.json version 0.4.0
CHANGELOG.md [0.4.0] date 2026-03-06 (updated)
CI/CD publish trigger push: tags: ["v*"] in publish-mcp.yml

Manual Release Steps (human operator, post-merge)

After merging this PR, the release operator must run:

# 1. Get latest main
git checkout main && git pull origin main

# 2. Tag and push — this triggers publish-mcp.yml automatically
git tag -a v0.4.0 -m "Release 0.4.0 — broker mode, Web UI, auto-restart, tools cache"
git push origin v0.4.0

# 3. Monitor CI/CD at:
#    https://github.com/SoundBlaster/XcodeMCPWrapper/actions
#    (Jobs: "Publish package to PyPI" and "Publish server to MCP Registry")

# 4. Verify after ~5 min:
pip install mcpbridge-wrapper==0.4.0
uvx mcpbridge-wrapper[webui] --version   # should print: 0.4.0

# 5. Check MCP Registry:
#    https://registry.modelcontextprotocol.io/?q=Xcode

What is NOT in this PR (by design)

  • The git tag v0.4.0 push — requires human confirmation and PyPI OIDC credentials active in CI
  • Actual PyPI publish — triggered automatically by the tag push via publish-mcp.yml
  • MCP Registry publish — triggered automatically by the same CI workflow

Test plan

  • make test — 785 tests pass, 90.91% coverage
  • make lint && make format-check — zero ruff issues
  • make typecheck — mypy clean
  • make doccheck-all — DocC mirrors in sync
  • make package-assets-check — Web UI assets in both wheel and sdist
  • grep "[0.4.0]" CHANGELOG.md## [0.4.0] - 2026-03-06

🤖 Generated with Claude Code

SoundBlaster and others added 4 commits March 6, 2026 22:08
Adds Phase 5 (Release) to the workplan with P5-T1 tracking the v0.4.0
publication steps: CHANGELOG date update, git tag, PyPI publish, MCP
Registry update, and badge verification.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…uality gates

- Change CHANGELOG.md [0.4.0] date from 2026-02-20 to 2026-03-06 (actual release date)
- All quality gates verified: 785 tests, 90.91% coverage, ruff clean, mypy clean,
  DocC sync clean, package assets (wheel + sdist) confirmed
- Mark P5-T1 as completed in Workplan.md and next.md
- Add P5-T1_Validation_Report.md with full gate results

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@SoundBlaster SoundBlaster merged commit 9f59a8b into main Mar 6, 2026
10 checks passed
@SoundBlaster SoundBlaster deleted the codex/feature/P5-T1-release-0.4.0 branch March 6, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant