Repository navigation
docs: the 2.7.0 changelog, and the branch the release workflow requires - #235
Merged
Merged
Conversation
The generated entry would name almost nothing: four of the six syncs this release carries predate #186 and are committed as `chore`, which the angular preset drops, and those four hold the tool changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y4EZAEvxLfXuMeNz5ZgCMz
`requireBranch` in .release-it.json is `release/*`, so a run from main fails the branch check the guide told the operator to satisfy. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Y4EZAEvxLfXuMeNz5ZgCMz
|
| Topic | Details | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Release Branch Guide | Correct the release guide and troubleshooting instructions to require a release/* branch instead of main.Modified files (1)
Latest Contributors(2)
| |||||||||
| 2.7.0 Changelog | Document the 2.7.0 tool changes, breaking renames and removed feature-selection options, new skills and extensions, plugin integrations, validation, and supporting fixes.Modified files (1)
Latest Contributors(2)
|
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.
Two docs changes ahead of the 2.7.0 release.
The 2.7.0 changelog
conventional-changelogwould name almost nothing for this release. Four of the six syncs it carries predate #186 and are committed aschore, which the angular preset drops, and those four hold the tool changes — the same problem the 2.6.1 entry was hand-written to fix.The entry covers what changed for anything calling these tools: three new tools (
currents-create-share-link,currents-add-attachments,currents-create-evidence-links), thefix-failing-testsskill, the Skills extension, the rewritten instructions, and the plugin and registry listings.Two breaking items, both of which
release-itcannot see because no commit carries aBREAKING CHANGE:footer:currents-create-trace-linkno longer exists;currents-create-evidence-linksreplaces it and returns more than the trace. There is no alias.--features,CURRENTS_MCP_FEATURESand theorgFeaturesoption onstartMcpServerare gone. Nothing reads argv for tool selection now, so a launcher still passing the flag starts normally and the flag is ignored — checked rather than assumed.autocomputes 2.7.0 from these commits (12feat:, no breaking footer), which matches 2.6.0: a minor carrying a tool rename under a ⚠ Breaking heading. Pickmajoron the Create Release workflow instead if you want 3.0.0, and the heading and compare link here need editing to match.This entry carries its own
# [2.7.0](…)heading, whichrelease-itwill duplicate. The release run prepends a generated heading plus a thin body above it. Keep the generated heading, drop this one, keep this body — the same two-step as 2.6.1.mcp-server/CHANGELOG.mdis in.prettierignore, so it is left unformatted; running Prettier over it rewrites every past entry's bullets.RELEASE.md
The guide says the release workflow must run from
main, butrequireBranchin.release-it.jsonisrelease/*. Following the guide fails the branch check. Both the requirement and the troubleshooting entry now namerelease/*.🤖 Generated with Claude Code
https://claude.ai/code/session_01Y4EZAEvxLfXuMeNz5ZgCMz
Generated by Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.