Repository navigation
Docs: unfreeze five React pages stuck on live since 22 September - #594
Open
amitthacker-maker wants to merge 1 commit into
Open
amitthacker-maker wants to merge 1 commit into
amitthacker-maker wants to merge 1 commit into
Conversation
Five React pages have been serving pre-22-September content on live since 412df50, and the cause is four missing backticks per line. The version range sat outside the code span: `react` >=18 <21 so `<21,` is bare MDX and parses as a JSX tag open. The five pages still return 200 on live, which is why no check caught it, but they render the state of the file before the break. Live tells a React developer the SDK peer dependency is `^4`, which permits 4.0.x; the real floor for UI Kit 7.2.x is 4.2.0, so following the published page produces a broken install. The same text already appears correctly elsewhere, inside backticks, on ui-kit/react/overview.mdx:97-98 and ui-kit/react/migration-overview.mdx:53. migration-overview builds and serves normally, which is what isolates the cause to the code span rather than to the text. This also unblocks three commits of corrections that have been stuck behind the break: v7 API errors and SSR guidance (3f8bc8c) and overlay containment (8cd8e5a, 4dcfda3). Found by raj-dubey1 in review of cometchat#585. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Preview approval requiredThis pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit |
Author
|
This can be closed. Main already carries the fix, reached a different way. The problem was that Main now writes it as two spans instead, the name and then the range: No objection to the branch, it is just no longer needed, and it conflicts because both sides edited the same line. |
This branch has not been deployed
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
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.
Five React pages have been serving pre-22-September content on live for six weeks. The cause is four missing backtick characters per line.
Found by @raj-dubey1 while reviewing #585. This is not a #585 problem, it is already on
main, and it should merge before #585.The bug
The version range sat outside its code span:
<21,is bare MDX, so it parses as a JSX tag open. Affected, all at line 12 onmain:ui-kit/react/overview.mdxui-kit/react/integration-react.mdxui-kit/react/integration-nextjs.mdxui-kit/react/integration-astro.mdxui-kit/react/integration-react-router.mdxWhy it went unnoticed
All five return HTTP 200 on live. They serve the last build that succeeded, so nothing looks broken from the outside and neither the Mintlify Deployment check nor link-rot catches it.
The cause is isolated, not inferred
On the #585 preview, a real Mintlify build, the five pages 308-redirect to Home while controls return 200:
/ui-kit/react/components/conversationsui-kit/react/migration-overviewfundamentals/pin-messagemigration-overviewis the control that settles it. It carries the same>=18 <21text at line 53, but inside backticks, and it builds and serves normally. Same text, same page family, only the code span differs.What live is serving
main4.1.9occurrences4.2.0occurrencesdompurifyLive tells a React developer the SDK peer dependency is
^4, which permits 4.0.x. The real floor for UI Kit 7.2.x is 4.2.0, so following the published page produces a broken install. The per-release floors (7.0.3 needs 4.1.12, 7.1.0 needs 4.1.13, 7.2.x needs 4.2.0) were written on 22 September and have never reached a reader.The served
.mdoutput carries the same stale table, so coding agents and answer engines are being given the wrong dependency facts too.Scope
Exactly five lines. A repo-wide grep for
<followed by a digit in.mdxreturns 10 hits; the other five are safe inside backticks or a ```swift fence (calls/flutter/overview.mdx:18, `ui-kit/react-native/upgrading-from-v4.mdx:646`, `ui-kit/react-native/property-changes.mdx:438`, `ui-kit/react/migration-overview.mdx:12,53`, `sdk/ios/3.0/send-a-message.mdx:426`).Also unblocks
Three commits of corrections have been stuck behind this: v7 API errors and SSR guidance (3f8bc8c), and overlay containment (8cd8e5a, 4dcfda3).
Worth checking after merge
Live is probably still serving only because of a cached last-good build. Please confirm the five pages render current content once this deploys, rather than redirecting to Home.
Introduced by 412df50, merged via #518.
🤖 Generated with Claude Code