ci: mirror every published package to GitHub Packages - #917
Merged
Conversation
document-cli and document-mcp were tracked in release-republish.json for their npm alias lists but carried no githubPackages entry, so neither ever got a GitHub Packages mirror. document-compute.js, epub-codec, and excel-number-format were absent from the file entirely -- each joined the monorepo without a prior standalone repository to port a mapping from, and nobody backfilled one. All five are real, published (non-private) packages; this adds a githubPackages entry for each, matching the same-name convention every other package already uses.
Mearman
marked this pull request as ready for review
September 4, 2026 15:22
Mearman
deleted the
ci/mirror-all-published-packages-to-github-packages
branch
September 4, 2026 15:22
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Not all internal packages were actually getting dual-deployed to GitHub Packages.
`.github/release-republish.json`'s `githubPackages` mapping was originally built by porting each package's own historical standalone-repo config, per #732. Two gaps fell out of that:
All five are real, published (non-private) npm packages. This adds a `githubPackages` entry for each, matching the same-name convention every other package already uses (e.g. `"doc-codec": { "githubPackages": "doc-codec", ... }`).
This only affects packages released after this merges — I'll backfill the already-published versions of these five via the existing `backfill_tags` workflow_dispatch input once this lands, rather than waiting for each one's next natural release.