Skip to content

claude: sync zerover release-type guidance; add changelog skill#86

Merged
Liam-DeVoe merged 2 commits into
mainfrom
sync-zerover-release-guidance
Jul 9, 2026
Merged

claude: sync zerover release-type guidance; add changelog skill#86
Liam-DeVoe merged 2 commits into
mainfrom
sync-zerover-release-guidance

Conversation

@Liam-DeVoe

Copy link
Copy Markdown
Member
Claude-written description

Syncs the zerover (0.x.y) release-type guidance into hegel-cpp, part of a cross-repo effort to replace stale classic-semver wording that recently caused a breaking change to be mislabeled RELEASE_TYPE: major.

  • RELEASE-sample.md: replaces the old "minor if visible in the public API, major if breaking" paragraph with the canonical zerover mapping — everything non-breaking is patch, breaking changes are minor, and major is reserved for 1.0.
  • Adds a changelog skill at .claude/skills/changelog/SKILL.md: a style guide for writing RELEASE.md entries (release-type selection, opening-sentence patterns, length calibration, tone), with examples written against real hegel-cpp APIs (text(), integers<uint64_t>(), Settings::report_multiple_failures, vectors()/VectorsParams).
  • .gitignore: whitelists .claude/skills/changelog/ so the skill is tracked, while other local .claude/skills/* content stays ignored.

Docs-only; no source changes, so no RELEASE.md.

Reviewer note (from self-review): the skill's opening-pattern table classifies deprecations as minor, while the zerover section defines minor as "breaking changes only" — a pure deprecation warning arguably doesn't force a caller update. Left as-is because the table is part of the mandated cross-repo template; if it should change, it should change at the template level across all seven repos.

@Liam-DeVoe Liam-DeVoe enabled auto-merge July 9, 2026 22:20
@Liam-DeVoe Liam-DeVoe merged commit 456a4fe into main Jul 9, 2026
14 checks passed
@Liam-DeVoe Liam-DeVoe deleted the sync-zerover-release-guidance branch July 9, 2026 22:50
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.

2 participants