chore(changesets): unescape jsonc fence in stage-5 changeset#3682
Merged
chore(changesets): unescape jsonc fence in stage-5 changeset#3682
Conversation
The Stage 5 brand.json changeset (PR #3604) was committed with `\`\`\`jsonc` (literal backslash-backticks) for its code fence, which trips Mintlify's acorn parser on every CI run: parsing error ./.changeset/per-version-badges-stage5-brand-json.md:15:13 - Could not parse expression with acorn Replacing the escaped fence with a plain `\`\`\`jsonc` block clears the warning. Documentation/content unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
The Stage 5 brand.json changeset (added in #3604) was committed with
\``jsonc(literal backslash-backticks) for its code fence. Mintlify's MDX pipeline runs acorn over.changeset/*.md` files and emits this warning on every CI run:The
Check for Broken Linksjob continues past the warning (thesuccess no broken links foundline follows it), so this is not blocking — just noise on every PR.Replacing the escaped fence with a plain
```jsoncblock clears the warning. Documentation content unchanged.Test plan
git diffshows only fence-character changesCheck for Broken LinksCI passes without the acorn warning