Skip to content

docs(contributing): document release process#89

Merged
PAMulligan merged 1 commit into
mainfrom
76-reconcile-packagejson-version-with-v100-tag
May 22, 2026
Merged

docs(contributing): document release process#89
PAMulligan merged 1 commit into
mainfrom
76-reconcile-packagejson-version-with-v100-tag

Conversation

@PAMulligan
Copy link
Copy Markdown
Collaborator

Closes #76.

Summary

The first and third acceptance criteria from #76 were already resolved in #86 (chore: versioning hygiene pass):

  • package.json is at 1.0.0, matching the only published tag v1.0.0.
  • pnpm run release is wired to commit-and-tag-version with .versionrc.json (tagPrefix v, conventional-commit types, postchangelog hook that writes RELEASE_NOTES.md).

This PR closes the remaining gap — the release process was undocumented for contributors and maintainers.

Changes

  • CONTRIBUTING.md: new Release Process section between Pull Request Process and Claude Code Agents. Documents:
    • The full pnpm run release command matrix (:patch / :minor / :major / :dry / :first).
    • The five things commit-and-tag-version does on a non-dry run (bump, CHANGELOG regen, postchangelog hook, commit, v-prefixed tag).
    • git push --follow-tags origin main to publish.
    • Conventional-commit rules that drive auto-bump (feat: → minor, fix: → patch, !/BREAKING CHANGE: → major), with a backlink to the existing PR Process examples.

Test plan

  • CONTRIBUTING.md renders correctly (table syntax + fenced code block)
  • All referenced files exist: .versionrc.json, scripts/extract-release-notes.js
  • All referenced pnpm run release* scripts exist in package.json
  • Tag prefix v matches .versionrc.json tagPrefix setting

🤖 Generated with Claude Code

Adds a Release Process section to CONTRIBUTING.md describing the
pnpm run release commands, what commit-and-tag-version does on each
non-dry run, the tag-prefix convention (v), the postchangelog hook
that writes RELEASE_NOTES.md, and the conventional-commit rules that
determine the bump. Closes the last remaining acceptance criterion
from #76 — the package.json/tag alignment and the release wiring
itself were already fixed in #86.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@PAMulligan PAMulligan linked an issue May 22, 2026 that may be closed by this pull request
3 tasks
@PAMulligan PAMulligan self-assigned this May 22, 2026
@PAMulligan PAMulligan added the documentation Improvements or additions to documentation label May 22, 2026
@PAMulligan PAMulligan moved this from Todo to Done in PMDS Open Source Roadmap May 22, 2026
@PAMulligan PAMulligan added this to the v1.1.0 milestone May 22, 2026
@PAMulligan PAMulligan merged commit 340a2f8 into main May 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

Development

Successfully merging this pull request may close these issues.

Reconcile package.json version with v1.0.0 tag

1 participant