chore(release): cut @jsonbored/gittensory-mcp v0.7.0#4132
Merged
Conversation
Bumps the package version, LATEST_RECOMMENDED_MCP_VERSION, and the CLI's self-reported version in lockstep, regenerates the changelog from the 250 commits since mcp-v0.6.0, and updates the version-pinned test fixtures to match. Also widens the release scripts' git() maxBuffer (default 1MB) — the growing backlog since the last tag now exceeds it and was failing changelog generation with ENOBUFS.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | d391607 | Commit Preview URL Branch Preview URL |
Jul 08 2026, 06:49 AM |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4132 +/- ##
=======================================
Coverage 93.68% 93.68%
=======================================
Files 384 384
Lines 36007 36007
Branches 13213 13213
=======================================
Hits 33733 33733
Misses 1618 1618
Partials 656 656
🚀 New features to boost your workflow:
|
|
Important 🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪 🔍 Gittensory is reviewing…AI analysis is in progress. This comment will update when the review is complete. 🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed · 🟪 Reviewing |
1 task
JSONbored
added a commit
that referenced
this pull request
Jul 8, 2026
#4135 (fix(mcp): build gittensory-engine before the publish gate + switch to workflow_dispatch) merged after PR #4132 originally generated this changelog, and it's classified as a direct MCP-relevant commit (touches .github/workflows/npm-publish.yml), so changelog:check:mcp correctly flagged the committed file as stale relative to the new mcp-v0.6.0..HEAD range. Regenerated -- 251 commits now, one new line.
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
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.
Summary
packages/gittensory-mcpfrom0.6.0to0.7.0(minor — 250 commits sincemcp-v0.6.0, per scripts/check-mcp-release-due.mjs)packages/gittensory-mcp/CHANGELOG.mdfor themcp-v0.7.0sectionLATEST_RECOMMENDED_MCP_VERSION(src/services/mcp-compatibility.ts) and the CLI's self-reportedpackageVersion(packages/gittensory-mcp/bin/gittensory-mcp.js) in lockstep, plus the version-pinned test fixtures that assert on themMCP_PACKAGE_KNOWN_LATEST_VERSIONpin at0.6.0— it lags one release by design until0.7.0is actually live on npm (bumped in a follow-up PR post-publish)git()helpermaxBuffer(was the Node default, 1MB) inscripts/generate-mcp-changelog.mjsandscripts/check-mcp-release-due.mjs— the growing commit backlog since the last tag now exceeds it, failing changelog generation withENOBUFSCloses #629
Next steps (after merge)
mcp-v0.7.0and push the tag to trigger the tokenlessnpm-publish.ymlworkflowMCP_PACKAGE_KNOWN_LATEST_VERSIONto0.7.0in a follow-up PRTest plan
npm run mcp:release-due— confirmsproposedVersion: 0.7.0npm run mcp:release-candidate— all checks PASS, "SAFE to tag"npm run test:release:mcp(fulltest:ci+changelog:check:mcp, mirrors the publish gate) — green