chore(changelog): regenerate v0.6.0 CHANGELOG to match merged history - #749
Conversation
|
Note Gittensory Gate skippedPR closed before full evaluation. No late first comment was created.
💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →. Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers. |
|
gittensory · advisory review Reviewed 1 changed file(s) — two independent AI reviewers. Suggested action: ✅ Safe to merge — both reviewers found no blocking issues. Reviewer A · Suggestions
Reviewer B · No blocking issues spotted. |
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Why
The
mcp-v0.6.0publish gate (changelog:check:mcp) failed: "CHANGELOG.md is stale." The 0.6.0 changelog was generated on the feature branch, but the squash-merges (#745, #748) rewrote the commit subjects/SHAs since themcp-v0.5.0tag, so regeneration no longer matched the committed file (one line: the #745 entry's subject).Change
Regenerated
packages/gittensory-mcp/CHANGELOG.mdon currentmainvianpm run changelog:mcp(one-line subject update). Committed under scopechangelog, whichmcp-release-core.mjs'sRELEASE_SCOPESexcludes from regeneration — so this commit doesn't itself re-introduce staleness (verified:changelog:check:mcpreports "current" from HEAD).After merge, the
mcp-v0.6.0tag moves here and the publish re-runs. Both prior gate blockers are now resolved (ui:version-auditvia #748,changelog:check:mcphere).Verify
changelog:check:mcp✅ ("current") · changelog content unchanged except the feat(mcp): slop self-check tools + release @jsonbored/gittensory-mcp v0.6.0 #745 subject line