chore(release): version packages#54
Merged
Merged
Conversation
✅ Deploy Preview for contentrain-ai ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
contentrain@0.5.3
Patch Changes
@contentrain/mcp@1.5.1
Patch Changes
61dcd1a: Remote write path no longer commits
.contentrain/context.jsonto feature branchescommitThroughProvider(used by content/model save/delete over GitHub and GitLab providers) bundled a freshly builtcontext.jsoninto every feature-branch commit. Because the file embedsnew Date()timestamps, two parallelcr/*branches forked from the samecontentraincommit always diverged on it — after the first branch merged and context was regenerated oncontentrain, the second branch's merge hit a permanent conflict oncontext.jsonand stayed pending forever (silent content loss in auto-merge setups).Remote commits now carry only the plan's own changes, matching the local transaction flow where feature branches intentionally never include
context.json. The orchestrator that owns the merge (e.g. Studio) is responsible for regeneratingcontext.jsonon thecontentrainbranch post-merge —buildContextChangeis exported from@contentrain/mcp/core/contextfor that purpose.@contentrain/rules@0.5.1
Patch Changes
34c9cf1: Fix stale context.json documentation: the file is never committed on feature branches
Rules and skills docs still described the pre-1.x behavior ("context.json is committed together with content changes"). Since the dedicated-branch transaction flow landed, context.json is regenerated on the
contentrainbranch after merge and feature branches never carry it — parallel writes therefore cannot conflict on it. Updated workflow-rules, mcp-usage, contentrain-essentials, context-bridge, and the contentrain skill references to state the current contract.@contentrain/skills@0.5.1
Patch Changes
34c9cf1: Fix stale context.json documentation: the file is never committed on feature branches
Rules and skills docs still described the pre-1.x behavior ("context.json is committed together with content changes"). Since the dedicated-branch transaction flow landed, context.json is regenerated on the
contentrainbranch after merge and feature branches never carry it — parallel writes therefore cannot conflict on it. Updated workflow-rules, mcp-usage, contentrain-essentials, context-bridge, and the contentrain skill references to state the current contract.