chore: unify the repo on the next branch#1454
Conversation
nuqs.dev deploys from `master` only to keep unreleased-feature docs out of production. Gating that content inline by the published npm version lets `next` become the single deploy source and ends the cherry-pick churn between branches.
franky47
added
documentation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
MDX components are wired through `mdx-components` and resolved at runtime, so Knip can't trace their usage and flags the export as unused. List it alongside the sibling audience and feature-support-matrix entries.
Neither branch sources npm publishes anymore (handled by the draft/validate/finalize workflow dispatched from `next`), so running the CI matrix on pushes to them is dead config. `next` and PRs still run it.
It auto-closed any PR targeting `master`; with `master` retired there are no such PRs left to guard against.
|
Caution Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted. Error details |
franky47
changed the title
1 participant
Why
nuqs.dev deploys from
master, but all development lands onnext. The two branches exist for one reason: keeping docs for unreleased features out of production until they ship on npm. Thebetabranch is a related leftover, no longer used for publishing now that releases run through the draft/validate/finalize workflow.The split is expensive. Every docs-only change (sponsors, dependency bumps, copy fixes) gets cherry-picked between branches. They drift, and we end up maintaining two sources of truth. They've been diverged for about 3.5 months.
This PR removes the reasons to keep
masterandbetaaround, so the repo can run fromnextalone.Docs: gate unreleased content
Wrap unreleased content in
<SinceVersion v="2.9.0">. In production it stays hidden until npm'slatestdist-tag reaches that version. The published version comes from one build-time fetch, frozen per deploy, so revealing GA docs is one redeploy away.Preview and local builds render everything, with a visual cue marking what isn't live yet. So unreleased docs are reviewable on a preview URL before they ship.
The same gate runs over the
llms.txt/.mdoutputs and theFeatureSupportMatrixversion lines, so the HTML docs and the LLM docs stay in sync.Today this gates the React Router v8 adapter and the
historydefault option, both slated for 2.9.0.CI: drop the retired branches
ci-cd.ymlno longer runs on pushes tomasterorbeta, onlynextand PRs. Neither branch sourced npm publishes anymore.pr-base-enforcement.yml, which only existed to close PRs targetingmaster.Out of scope (follow-ups)
master-only docs tweaks tonextbefore the cutover.next, then retiremaster.