fix(docs): wrap CustomExtensionsRuntime placeholder for VitePress#389
Merged
Conversation
The v1.21.0 release tag tripped the Docs workflow because the #364 changelog entry mentions `{{.CustomExtensionsRuntime}}` verbatim, and Vue's compiler parses interpolations even inside backtick code spans. The leading dot fails JS expression parsing and the build halts with `Unexpected token (1:1)`. Same shape as the previous Resources.Memory case we fixed by wrapping the token in an explicit <code v-pre> element so Vue skips it. Docs CI is gated to non-prerelease tags so the issue never showed up on v1.21.0-beta.1, only surfacing now that stable shipped.
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.
The v1.21.0 tag tripped the Docs workflow because the #364 changelog entry mentions
{{.CustomExtensionsRuntime}}verbatim, and Vue's compiler parses interpolations even inside backtick code spans. The leading dot fails JS expression parsing and the build halts withUnexpected token (1:1). Same shape as the previousResources.Memorycase we fixed by wrapping the token in an explicit<code v-pre>element so Vue skips it.Docs CI is gated to non-prerelease tags so the issue never showed up on v1.21.0-beta.1, only surfacing now that stable shipped. After this merges I'll run
gh workflow run docs.ymlto publish the rebuilt site.