chore(deps): bump @contentrain/mcp 3.1.8, types 1.9.1, query 7.0.14 - #228
Merged
Conversation
Studio pinned types 1.2.0 / mcp 3.1.0 / query 7.0.6, seven releases behind. The gap is narrower than it looks: between mcp 3.1.0 and 3.1.7 the package source did not change (types bumps only), and types 1.3 through 1.9 added the WordPress migration contracts without touching FieldDef, ModelDefinition, PATH_PATTERNS or any symbol Studio imports. The substantive change is 3.1.8 / 1.9.1: the generic `api_key = …` secret rule now checks what it captured before it fires. Studio's validateContent comes from the MCP validator and calls detectSecrets, so until now a setup guide that said `api_key = your_project_api_key_here` was refused by every Studio write path — UI, agent, Conversation API. The new test pins that the fix reaches Studio, and that an issued key is still refused. Also in 3.1.8, for the next PRs: publish_at/expire_at ride on ContentEntry (meta only, null clears), legacy field names are grandfathered by the MCP validator, and title_field inference matches Studio's resolver.
This was referenced Sep 2, 2026
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
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.
Summary
Studio pinned
@contentrain/types1.2.0 /mcp3.1.0 /query^7.0.6 — seven releases behind npm. Verified against theContentrain/aicheckout:packages/mcp/srcdid not change between 3.1.0 and 3.1.7 (dependency bumps only).migration.ts);FieldDef,ModelDefinition,PATH_PATTERNS, the 27-tool list and every symbol Studio imports are unchanged. Nolocalizedflag yet.What reaches Studio with this bump:
validateContentis the MCP validator and callsdetectSecrets, soapi_key = your_project_api_key_herein ordinary content was refused by every Studio write path. New test incontent-validation.test.tspins both directions (placeholders pass, an issued key is still refused).ContentEntry.publish_at/expire_at(meta only,nullclears),legacyFieldNames/collectFieldPathsfrom@contentrain/mcp/core/model-manager, title inference parity.Write-path check per the bump rule: the only engine-facing change is
mergeEntryMeta(prior, entry)reading scheduling from the entry instead ofentry.data; Studio's entries carry neither, so planned meta is unchanged.planModelSaveandGitHubProviderare identical.Test plan
contentrain-query generate,pnpm lint(0 errors),nuxt typecheck, fullpnpm test(160 files / 1446 tests)content-validation.test.tscases for the secret ruleapi_key = your_key_here🤖 Generated with Claude Code
https://claude.ai/code/session_01Chid3TnLdPHjsKip4n63Ky