Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .changeset/fix-changeset-jsonc-escapes.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
---
---

chore(changesets): unescape backticks in `per-version-badges-stage5-brand-json.md`

The Stage 5 changeset (PR #3604) was committed with `\`\`\`jsonc` (literal
backslash-backticks) for its code fence. Mintlify's MDX pipeline runs
acorn over `.changeset/*.md` files and emits a noisy `Could not parse
expression with acorn` warning on every CI run. Replacing the escaped
fence with a plain ` ```jsonc ` block clears the warning. No content
change.
4 changes: 2 additions & 2 deletions .changeset/per-version-badges-stage5-brand-json.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ backend(verification): brand.json + /verification carry per-version badge detail

`aao_verification` blocks served via brand.json enrichment now include a `badges[]` array — one entry per `(role, adcp_version)` with full per-version detail:

\`\`\`jsonc
```jsonc
"aao_verification": {
"verified": true,
"verified_at": "2026-04-30T...",
Expand All @@ -18,7 +18,7 @@ backend(verification): brand.json + /verification carry per-version badge detail
"roles": ["media-buy"],
"modes_by_role": { "media-buy": ["spec", "live"] }
}
\`\`\`
```

`badges[]` is the canonical forward-compat shape (Q6 of [#3524's resolved decisions](https://github.com/adcontextprotocol/adcp/issues/3524#issuecomment-4348265184)). One entry per parallel-version badge; preserved order matches the API's version-DESC sort. Adding future axes to a badge (e.g. a third verification mode) doesn't change the array shape.

Expand Down
Loading