chore(release): version packages#61
Merged
Merged
Conversation
✅ Deploy Preview for contentrain-ai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 9, 2026 08:59
686e377 to
2c9da25
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
[email protected]
Minor Changes
ee8da2d: Delete remote cr/* branches on merge/delete and harden merged-branch detection
Every review-mode save pushed its
cr/*branch to origin, but nothing ever deleted the remote copy after a merge — stale branches accumulated monotonically (one per save+merge cycle) and rendered as phantom pending reviews in Studio.mergeBranch(and thereforecontentrain_merge,contentrain merge,contentrain diff, the Serve UI approve endpoints, andLocalProvider.mergeBranch) now deletes the merged branch's remote copy — best-effort: failures surface as aremote.warning, never as a failed merge. Default on; opt out withremoteBranchCleanup: falseinconfig.json. Note: deleting a pushed branch closes any open PR/MR on it.contentrain_branch_delete, the Serve UI reject endpoint,contentrain diff's delete action, andLocalProvider.deleteBranchremove the remote copy too.contentrain_branch_deletealso supports remote-only deletion when the local ref is already gone.mergeBranch(..., { removeSourceBranch: false })).isMerged,cleanupMergedBranches,checkBranchHealth) now falls back to patch-id equivalence (git cherry) when ancestry breaks — merged branches no longer flip to "unmerged" after a base-history rewrite. Also fixes the fast-forward guard in the transaction layer, which previously never fired (merge-base --is-ancestorsignals via exit code with empty stderr, which simple-git reports as success).contentrain_doctorgains a "Remote branches" check (authoritativels-remotecount, offline-safe);contentrain_branch_listacceptsremote: truefor a remote view.contentrain pruneCLI command drains already-leaked merged remote branches (--dry-run/--yes/--json), andcontentrain_submitlazily prunes up to 20 merged remote leftovers per run.@contentrain/mcp/git/branch-lifecycle:deleteRemoteBranch,listRemoteCrBranches,pruneMergedRemoteBranches,isRefMerged,classifyMergedBranches.Patch Changes
@contentrain/[email protected]
Minor Changes
ee8da2d: Delete remote cr/* branches on merge/delete and harden merged-branch detection
Every review-mode save pushed its
cr/*branch to origin, but nothing ever deleted the remote copy after a merge — stale branches accumulated monotonically (one per save+merge cycle) and rendered as phantom pending reviews in Studio.mergeBranch(and thereforecontentrain_merge,contentrain merge,contentrain diff, the Serve UI approve endpoints, andLocalProvider.mergeBranch) now deletes the merged branch's remote copy — best-effort: failures surface as aremote.warning, never as a failed merge. Default on; opt out withremoteBranchCleanup: falseinconfig.json. Note: deleting a pushed branch closes any open PR/MR on it.contentrain_branch_delete, the Serve UI reject endpoint,contentrain diff's delete action, andLocalProvider.deleteBranchremove the remote copy too.contentrain_branch_deletealso supports remote-only deletion when the local ref is already gone.mergeBranch(..., { removeSourceBranch: false })).isMerged,cleanupMergedBranches,checkBranchHealth) now falls back to patch-id equivalence (git cherry) when ancestry breaks — merged branches no longer flip to "unmerged" after a base-history rewrite. Also fixes the fast-forward guard in the transaction layer, which previously never fired (merge-base --is-ancestorsignals via exit code with empty stderr, which simple-git reports as success).contentrain_doctorgains a "Remote branches" check (authoritativels-remotecount, offline-safe);contentrain_branch_listacceptsremote: truefor a remote view.contentrain pruneCLI command drains already-leaked merged remote branches (--dry-run/--yes/--json), andcontentrain_submitlazily prunes up to 20 merged remote leftovers per run.@contentrain/mcp/git/branch-lifecycle:deleteRemoteBranch,listRemoteCrBranches,pruneMergedRemoteBranches,isRefMerged,classifyMergedBranches.Patch Changes
@contentrain/[email protected]
Minor Changes
ee8da2d: Delete remote cr/* branches on merge/delete and harden merged-branch detection
Every review-mode save pushed its
cr/*branch to origin, but nothing ever deleted the remote copy after a merge — stale branches accumulated monotonically (one per save+merge cycle) and rendered as phantom pending reviews in Studio.mergeBranch(and thereforecontentrain_merge,contentrain merge,contentrain diff, the Serve UI approve endpoints, andLocalProvider.mergeBranch) now deletes the merged branch's remote copy — best-effort: failures surface as aremote.warning, never as a failed merge. Default on; opt out withremoteBranchCleanup: falseinconfig.json. Note: deleting a pushed branch closes any open PR/MR on it.contentrain_branch_delete, the Serve UI reject endpoint,contentrain diff's delete action, andLocalProvider.deleteBranchremove the remote copy too.contentrain_branch_deletealso supports remote-only deletion when the local ref is already gone.mergeBranch(..., { removeSourceBranch: false })).isMerged,cleanupMergedBranches,checkBranchHealth) now falls back to patch-id equivalence (git cherry) when ancestry breaks — merged branches no longer flip to "unmerged" after a base-history rewrite. Also fixes the fast-forward guard in the transaction layer, which previously never fired (merge-base --is-ancestorsignals via exit code with empty stderr, which simple-git reports as success).contentrain_doctorgains a "Remote branches" check (authoritativels-remotecount, offline-safe);contentrain_branch_listacceptsremote: truefor a remote view.contentrain pruneCLI command drains already-leaked merged remote branches (--dry-run/--yes/--json), andcontentrain_submitlazily prunes up to 20 merged remote leftovers per run.@contentrain/mcp/git/branch-lifecycle:deleteRemoteBranch,listRemoteCrBranches,pruneMergedRemoteBranches,isRefMerged,classifyMergedBranches.@contentrain/[email protected]
Patch Changes