chore(release): version packages#87
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.
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]
Patch Changes
@contentrain/[email protected]
Patch Changes
a0d5bfe: fix(mcp): make i18n:false delete and meta cleanup safe
Two bugs a project hit while cleaning up an
i18n: falsecollection, plus asource-hygiene fix surfaced along the way.
content_deleteno longer destroys content when handed a locale. On ani18n: falsemodel, passing a non-defaultlocalewas destructive: the localemapped onto
data.jsonand the default-locale meta, so the call emptied theshared content and deleted the wrong meta file while the locale actually named
kept its stray meta — the opposite of the request. Content is locale-agnostic
here, so a locale-scoped delete is now rejected with a clear error (both in the
plan API and the legacy path). Omit
localeto delete the entry.contentrain_validatewithfix: truenow clears the meta layout mismatch itwarns about. The "Meta layout mismatch" warning had no remediation, so
fixedstayed
0. The fix is deterministic and never decides a status: when thedefault-locale meta is authoritative the redundant strays are pruned; when only
a stray exists it is migrated to the default path so the record is preserved;
several strays with no default is left for the author to resolve. Consolidation
runs before the orphan-content pass and gates that pass's draft fabrication, so
a real published record is never replaced by a fabricated draft and then deleted
on a later run.
Also replaced two raw NUL bytes in the validator source (a Map-key separator)
with a
\u0000escape — identical at runtime, but the source is now plain textinstead of being classified as binary by grep/diff/editors.