Contentrain/ai

v@contentrain/[email protected] Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1mo Developer Productivity

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ai-agents claude-code content-governance contentrain cursor developer-tools

+8 more

git i18n mcp mcp-server model-context-protocol sdk typescript windsurf

Affected surfaces

breaking_upgrade

ReleasePort's take

Light signal

editorial:auto 1mo

The remote write path in @contentrain/[email protected] no longer commits `.contentrain/context.json` to feature branches, eliminating permanent merge conflicts and preventing silent content loss.

Why it matters: Fixes a bug that caused irreversible merge conflicts when committing `.contentrain/context.json`, ensuring reliable remote write operations.

Summary

AI summary

Remote write path no longer commits .contentrain/context.json to feature branches, eliminating permanent merge conflicts.

Changes in this release

Type	Severity	Summary	CVE
Bugfix	Medium	Remote write path no longer commits `.contentrain/context.json` to feature branches, preventing permanent merge conflicts and silent content loss. Remote write path no longer commits `.contentrain/context.json` to feature branches, preventing permanent merge conflicts and silent content loss. Source: llm_adapter@2026-06-12 Confidence: low	—

Full changelog

Patch Changes

61dcd1a: Remote write path no longer commits .contentrain/context.json to feature branches

commitThroughProvider (used by content/model save/delete over GitHub and GitLab providers) bundled a freshly built context.json into every feature-branch commit. Because the file embeds new Date() timestamps, two parallel cr/* branches forked from the same contentrain commit always diverged on it — after the first branch merged and context was regenerated on contentrain, the second branch's merge hit a permanent conflict on context.json and 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 regenerating context.json on the contentrain branch post-merge — buildContextChange is exported from @contentrain/mcp/core/context for that purpose.

Breaking Changes

Removed automatic inclusion of `.contentrain/context.json` in every remote write commit to feature branches.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track Contentrain/ai

Get notified when new releases ship.

About Contentrain/ai

Local-first MCP server for AI content governance — 13 tools for model/content CRUD, validation, normalization, and i18n across any framework.

All releases →

Related context

Related tools

Earlier breaking changes

v@contentrain/[email protected] `validateModelDefinition` now returns `{ errors, warnings }` instead of a string array.
v@contentrain/[email protected] `model_save` rejects models with unknown keys, `min > max`, invalid constraints, and `unique` on singletons.
v@contentrain/[email protected] `content_save` now validates before committing and rejects invalid content.
v@contentrain/[email protected] `validateModelDefinition` now returns `{ errors, warnings }` instead of a string array.
v@contentrain/[email protected] `model_save` rejects models with unknown keys, `min > max`, invalid constraints, and `unique` on singletons.