feat(changelog-release): release 時に manifest version を同期 + タグ規約明文化 (#441/#442 follow-up)#443
Merged
Merged
Conversation
…on も同期 release script が CHANGELOG だけ書き換えて manifest version を触らないため、 0.7.0 で package-lock が 0.6.0 のまま残り CI の version-drift guard が落ちた (#442)。bumpManifestVersion を追加し、release version を package.json と package-lock.json (root + packages[""]) に byte-stable な text 置換で同期する。 --dry-run/preview は would-bump を表示するのみ。 .changelog/README.md の release 手順を更新し、annotated な vX.Y.Z タグ規約 (1 release 1 tag) を明文化。#441/#442 follow-up。 Claude-Session: https://claude.ai/code/session_01GFvSe4z4aD7qZxPvJuWC72
eris-ths
added a commit
that referenced
this pull request
Jun 23, 2026
Folds three fragments into CHANGELOG.md and bumps package.json + package-lock.json (root + packages[""]) to 0.7.1: - Added: ctx supersede (#444) — the first phase-2 ctx verb. - Changed: changelog-release now bumps the manifests (#441/#442) and refuses orphan fragments (#441). Alpha patch bump (minor reserved while ctx is still phase-2). This also re-aligns the released version with main: v0.7.0 predated #443/#444, so the bin was reporting 0.7.0 while carrying unreleased verbs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
なぜ
#442 の 0.7.0 dogfood で、release 手順が
package.jsonを bump してもpackage-lock.jsonを同期せず、CI の version-drift guard が落ちた。真因はrelease script が CHANGELOG しか書き換えないこと——version bump は手作業
任せで、抜けが構造的に起こりうる状態だった。
何を
bumpManifestVersionを追加。changelog-releaseが CHANGELOG 折込と同じ一手で
package.jsonとpackage-lock.json（root +packages[""]）のversionを release version に同期する。byte-stable な text 置換でversion 行だけを動かす（JSON 再シリアライズしない＝差分最小）。
--dry-run/changelog:previewは would-bump を表示するのみ（無書込）。.changelog/README.mdの release 手順を更新し、**annotated なvX.Y.Zタグ規約（1 release 1 tag）**を明文化。検証
のみ（package.json 1 行 / package-lock 2 行）。bump 後に version-drift
guard 相当チェックが consistent を返すことを確認。
補足（環境制約・要 follow-up）
refs/tags/*の push を一律に弾く（branch ref は通る、annotated/lightweightとも
send-pack: unexpected disconnect）。GitHub MCP にもタグ/release 作成tool が無い。→ v0.7.0 タグは tag-push 可能な環境 or GitHub UI から手動で
打つ必要がある（規約は本 PR で確定済み）。
🤖 Generated with Claude Code
Generated by Claude Code