Repository navigation
Restore npm publishing and decide v2/v3 consumer path #3
Description
Problem
v3.0.4 was merged and tagged from main, but the tag publish workflow failed at npm publish with npm E404 Not Found / permission denial for @git-stunts/trailer-codec@3.0.4. npm still reports latest as 2.1.1; GitHub Release v3.0.4 was not created because publish failed.
Evidence:
- PR fix(trailer-codec): publish type declarations #2 merged: fix(trailer-codec): publish type declarations #2
- Tag pushed:
v3.0.4->95ba0fba1d1ad06beb73b76470b12e71e495b2b6 - Failed workflow: https://github.com/git-stunts/trailer-codec/actions/runs/28131804750
- npm registry latest observed after failure:
@git-stunts/trailer-codec@2.1.1
Why this matters
git-warp currently depends on @git-stunts/trailer-codec@^2.1.1, uses the synchronous v2 facade, and imports TrailerCodecFacade from the package declarations supplied by a local patch. The v3 mainline is async and is not a drop-in replacement for that consumer.
Required decision
Choose and execute one path:
- Configure npm trusted publishing / token access for this repo, then publish the tagged v3 line and plan a git-warp async migration separately.
- Cut a v2-compatible
2.1.2backport that only adds TypeScript declarations for the existing sync API, then publish it so git-warp can remove its local patch without an async migration.
Do not remove git-warp's trailer-codec patch until one of those paths produces a consumable package version.
Activity
flyingrobots commentedon Jun 24, 2026
Recovery update after PR #4:
npm publish --access public --provenance, and a manual recover workflow.v3.0.4still failed: https://github.com/git-stunts/trailer-codec/actions/runs/28132250097E404 Not Found - PUT https://registry.npmjs.org/@git-stunts%2ftrailer-codec.Conclusion: this is now an npm registry authorization/trusted-publisher configuration blocker, not a package contents blocker. To recover
v3.0.4, configure npm publishing for@git-stunts/trailer-codecfrom this GitHub repo/workflow (or provide an npm token with publish rights), then rerun theRecover Releaseworkflow withtag=v3.0.4.flyingrobots commentedon Jul 30, 2026
Closed as Path 1 has been completed: npm OIDC trust/trusted publishing is now configured, and v3.0.4 has been successfully published to npm. The git-warp async migration will be planned and tracked separately.