Repository navigation
[*] Chore: Point package repository links at meta/lexical after the org rename - #9498
Merged
Merged
Conversation
…rg rename ## Description Every published package's `repository.url` (and the few `bugs.url` and `homepage` fields) still say `github.com/facebook/lexical`. GitHub redirects the old URLs, but two things read the npm manifest literally: - pkg.pr.new compact URLs (`https://pkg.pr.new/lexical@<pr>`) take the owner and repo from the `repository` field of the package's npm `latest` manifest. Previews published since the rename are stored under `meta/lexical`, so the compact form 404s for them until a release ships this metadata. The long form (`pkg.pr.new/meta/lexical/lexical@<pr>`) works today. - npm provenance compares the manifest's `repository` with the repository in the build's OIDC claims. This changes those fields in all 36 package manifests. It takes effect for compact pkg.pr.new URLs once a `latest` release with it is published. ## Changeset `.changeset/point-package-repository-bugs-and-homepage-links-at.md` (`[chore]`, all 36 published packages). ## Test plan ### Before ``` $ curl -s -o /dev/null -w '%{http_code}\n' https://pkg.pr.new/lexical@9497 404 $ curl -s -o /dev/null -w '%{http_code}\n' https://pkg.pr.new/meta/lexical/lexical@9497 200 $ npm view lexical repository.url git+https://github.com/facebook/lexical.git ``` ### After ``` $ git grep -c 'github.com/facebook/lexical' -- package.json 'packages/*/package.json' (no output) $ pnpm run check-changesets Changeset check passed: 2 pending changeset(s) valid. ``` The compact URL fix is only observable after the next `latest` release.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
zurfyx
requested review from
acywatson,
etrepum,
ivailop7 and
potatowagon
as code owners
October 28, 2026 19:35
meta-cla
Bot
added
the
CLA Signed
zurfyx
enabled auto-merge
October 28, 2026 20:39
zurfyx
added a commit
that referenced
this pull request
Oct 28, 2026
…he org rename ## Description The repository moved from `facebook/lexical` to `meta/lexical`, but the docs, READMEs, examples and source comments still link to the old path. GitHub redirects most of those, but not everything does: the pkg.pr.new long-form install URLs in the maintainers guide 404 under `facebook/lexical` for previews published since the rename. This rewrites the remaining living references to `github.com/meta/lexical`: issue, pull, blob/tree, discussion and graph links, plus the `facebook/lexical#NNNN` shorthand in source and test comments. In `packages/lexical-website/docusaurus.config.ts`, `GITHUB_REPO_URL` (which feeds the docs `editUrl`s and the TypeDoc source links), the canonical repository fallback used for StackBlitz embeds, and `organizationName` now say `meta`. The playground's welcome content, and the serialization unit and e2e tests that mirror it, use the new URL. Left alone on purpose: - Files changed by #9497 (GitHub Actions and release tooling) and #9498 (package.json metadata and its changeset), so the three PRs do not conflict. - `CHANGELOG.md`, where the links are a historical record and still redirect. - StackBlitz URLs (`stackblitz.com/github/facebook/lexical/...`), the shields.io build badge and the contrib.rocks image. All three still resolve under the old path (checked below), so they are not changed. ## Changeset `.changeset/point-documentation-and-source-comment-links-at.md` (`[docs]`) for the eight published packages whose shipped README or `src/` comments change: `lexical`, `@lexical/markdown`, `@lexical/mdast`, `@lexical/plain-text`, `@lexical/react`, `@lexical/rich-text`, `@lexical/table` and `@lexical/utils`. The website, playground, examples and scripts need none. ## Test plan ### Before ``` $ git grep -lE 'github\.com/facebook/lexical|facebook\.github\.io/lexical|pkg\.pr\.new/facebook|facebook/lexical#[0-9]' -- . ':!CHANGELOG.md' \ | grep -vxFf <(files changed by #9497 and #9498) | wc -l 73 $ curl -s -o /dev/null -w '%{http_code}\n' https://pkg.pr.new/facebook/lexical/lexical@9497 404 $ curl -s -o /dev/null -w '%{http_code}\n' https://pkg.pr.new/meta/lexical/lexical@9497 200 ``` The links that are kept still work under the old path: ``` $ curl -sL https://img.shields.io/github/actions/workflow/status/facebook/lexical/tests.yml | grep -o '<title>[^<]*</title>' <title>build: passing</title> $ curl -sL -o /dev/null -w '%{http_code} %{content_type}\n' 'https://contrib.rocks/image?repo=facebook/lexical' 200 image/svg+xml $ curl -sL https://stackblitz.com/github/facebook/lexical/tree/d99563ccd/examples/vanilla-js | grep -o '<title>[^<]*</title>' <title>Lexical Vanilla Js Example - StackBlitz</title> $ curl -sL https://stackblitz.com/github/nonexistent-org-zz/lexical/tree/main/examples/vanilla-js | grep -o '<title>[^<]*</title>' <title>StackBlitz</title> ``` (d99563c is today's main, so StackBlitz follows the rename rather than serving a cached import.) ### After ``` $ git grep -lE 'github\.com/facebook/lexical|facebook\.github\.io/lexical|pkg\.pr\.new/facebook|facebook/lexical#[0-9]' -- . ':!CHANGELOG.md' \ | grep -vxFf <(files changed by #9497 and #9498) | wc -l 0 $ git grep -lE 'facebook/lexical' -- . ':!CHANGELOG.md' | grep -vxFf <(...) \ | xargs git grep -hoE '[a-z./=?]*facebook/lexical' -- | sort | uniq -c 2 //contrib.rocks/image?repo=facebook/lexical 1 //img.shields.io/github/actions/workflow/status/facebook/lexical 34 //stackblitz.com/github/facebook/lexical ``` Every new `github.com/meta/lexical` URL in the diff (92 unique): ``` $ ... | xargs -P 6 -I{} curl -s -o /dev/null -w '%{http_code} {}\n' {} | awk '{print $1}' | sort | uniq -c 89 200 1 301 2 404 ``` The 301 is `https://github.com/meta/lexical.git` in the maintainers guide's package.json sample; the 404s are `/settings/variables/actions` (needs repo admin) and the synthetic `blob/main/index.ts#L4` fixture in `typedocExternalLinks.test.ts`. ``` $ pnpm run ci-check Changeset check passed: 4 pending changeset(s) valid. Found 0 errors (exit 0: tsc, tsc-test, tsc-scripts, tsc-extension, tsc-website, flow, prettier, lint, check-changesets) $ pnpm exec vitest --project unit --project scripts-unit --no-watch <the 26 changed test files> Test Files 26 passed (26) Tests 1018 passed (1018) $ (cd packages/lexical-website && pnpm run build) [SUCCESS] Generated static files in "build". $ grep -rlE 'github\.com/facebook/lexical' --include='*.html' packages/lexical-website/build | wc -l 0 $ grep -rhoE 'stackblitz\.com/github/[a-z]+/lexical' --include='*.html' packages/lexical-website/build | sort | uniq -c 22 stackblitz.com/github/meta/lexical ``` The playground e2e specs touched here (`Links.spec.mjs`, `Autocomplete.spec.mjs`) were not run; their change is the same URL on both the typed input and the expected `href`.
This branch was successfully 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.
Description
Every published package's
repository.url(and the fewbugs.urlandhomepagefields) still saygithub.com/facebook/lexical. GitHub redirectsthe old URLs, but two things read the npm manifest literally:
https://pkg.pr.new/lexical@<pr>) take the ownerand repo from the
repositoryfield of the package's npmlatestmanifest.Previews published since the rename are stored under
meta/lexical, so thecompact form 404s for them until a release ships this metadata. The long
form (
pkg.pr.new/meta/lexical/lexical@<pr>) works today.whose
repository.urldoes not match the repository in the build's OIDCclaims, which is now
meta/lexical. So the next nightly or release publishneeds this merged, not just the workflow guards in [*] Chore: Point CI, release tooling, docs and links at meta/lexical after the org rename #9497.
This changes those fields in all 36 package manifests. It takes effect for
compact pkg.pr.new URLs once a
latestrelease with it is published.Changeset
.changeset/point-package-repository-bugs-and-homepage-links-at.md([chore],all 36 published packages).
Test plan
Before
After
The compact URL fix is only observable after the next
latestrelease.