You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decide the fate of the pdf-codec.js and pdf-parser.js npm aliases, stranded since the monorepo migration #729
pdf-codec.js and pdf-parser.js are npm aliases for pdf-codec, previously published by the standalone pdf-codec repo's own CI. That repo is now archived as part of the monorepo consolidation (see #664), and this monorepo's release pipeline has no equivalent alias-publishing step, so both aliases are stuck at their last pre-migration version while pdf-codec itself keeps releasing.
Wire alias publishing into this repo's release workflow, so both aliases keep tracking pdf-codec on every release.
Leave them frozen deliberately and mark them deprecated on npm (npm deprecate) pointing users at pdf-codec, so they stop looking like maintained packages.
Either is fine; what's not fine is leaving them silently stale with no decision recorded.
The decision is made and shipped: restore, not deprecate. PR #773 merged the post-release republish machinery back into the monorepo's CI, and this alias is listed in release-republish.json's map, so every future release of its parent package republishes under this name via OIDC trusted publishing.
One activation step remains and it is npm-account-side only (documented in the repo README's Releases section): each alias name's trusted publisher must be registered once against ExaDev/documents.js + workflow ci.yml on npmjs.com, because trusted publishing is registered per package name and this alias's existing registration still names its archived standalone repository. Until then the alias's publish leg skips with a notice rather than failing the job; the first release after registration picks the name up automatically.
Activity
docs: point package release sections at the monorepo root, not stale …
Mearman commentedon Aug 21, 2026
The decision is made and shipped: restore, not deprecate. PR #773 merged the post-release republish machinery back into the monorepo's CI, and this alias is listed in
release-republish.json's map, so every future release of its parent package republishes under this name via OIDC trusted publishing.One activation step remains and it is npm-account-side only (documented in the repo README's Releases section): each alias name's trusted publisher must be registered once against
ExaDev/documents.js+ workflowci.ymlon npmjs.com, because trusted publishing is registered per package name and this alias's existing registration still names its archived standalone repository. Until then the alias's publish leg skips with a notice rather than failing the job; the first release after registration picks the name up automatically.docs: point package release sections at the monorepo root, not stale …
Mearman commentedon Sep 10, 2026
Trusted publishers registered and verified: the backfill run https://github.com/ExaDev/documents.js/actions/runs/34449796133 published pdf-codec.js@4.5.1 and pdf-parser.js@4.5.1 (both legs green, registry confirms).