Repository navigation
Conversation
slorber
added
the
pr: maintenance
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
✅ [V2]
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Size Change: -160 B (0%) Total Size: 12.1 MB 📦 View Changed
ℹ️ View Unchanged
|
⚡️ Lighthouse report for the deploy preview of this PR
|
|
Size Change: -160 B (0%) Total Size: 12.1 MB 📦 View Changed
ℹ️ View Unchanged
|
…sted) npm provenance (generated by Trusted Publishing) rejects a package whose `repository.url` doesn't match the repository the workflow runs in. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
History is left unchanged: changelogs, blog posts, versioned docs, generated examples and test fixtures. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
slorber
force-pushed
the
claude/meta-docusaurus-references
branch
from
October 30, 2026 15:57
2de9c10 to
a0e1dcb
Compare
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.
Motivation
Follow-up of #12817 after the repository moved from
facebook/docusaurustometa/docusaurus. Draft until we know the move is permanent.The first commit is a fix: npm provenance, generated by Trusted Publishing, rejects a package whose
package.jsonrepository.urldoesn't match the repository the publish workflow runs in. All@docusaurus/*packages still point tofacebook/docusaurus, so the canary release that #12817 re-enables will likely fail without it.The second commit is cosmetic: GitHub redirects the old links, but new sites (
create-docusaurustemplates), runtime warnings, the website and our docs keep pointing to the old name.facebook/docusaurus→meta/docusaurus, including the URL-encoded Vercel deploy button of the READMEfacebook.github.io/docusaurus→meta.github.io/docusaurus: the hash router GitHub Pages deployment moved there, the old URL is a 404organizationName: 'facebook'→'meta'in the website config and the init templatesLeft unchanged on purpose, as history or placeholder data:
CHANGELOG.md,CHANGELOG-v2.md,website/blog,website/versioned_docsexamples/, regenerated from the templates at release timevalidate-package-jsontest and the 2 snapshots of the unused directives warningTest Plan
Mechanical replacement, CI. Binary assets (PDF dogfooding files) matched the pattern and were left unchanged.
After merging: the next canary publish on
mainmust pass npm provenance validation.Test links
Deploy preview: https://deploy-preview-12818--docusaurus-2.netlify.app/
Related issues/PRs
🤖 Generated with Claude Code (AI-assisted)