Skip to content

fix(release): publish npmjs mirror tarball as a local file - #150

Merged
willgriffin merged 1 commit into
mainfrom
codex/pdf-mirror-local-path
Oct 16, 2026
Merged

willgriffin merged 1 commit into
mainfrom
codex/pdf-mirror-local-path

Conversation

@willgriffin

Copy link
Copy Markdown
Contributor

Fixes the npmjs mirror failure from v0.67.0: npm interpreted mirror-pack/package.tgz as GitHub shorthand. Prefixing the path with ./ makes npm publish the downloaded local tarball.

Closes #149

The existing integrity, registry, credential and main-only environment gates remain in place. The primary release succeeded; this repair lets subsequent releases reach npmjs too.

Validation: npm publish --dry-run using the actual v0.67.0 primary tarball passes; extracted mirror shell passes bash -n; normal commit hooks pass. No source code changed. Both independent reviewers (Claude Opus and Codex Astra) returned CLEAN at ef5bebf. Original cycle 6216025328, user-approved round 7; evidence at /tmp/paddleocr-release-evidence/pdf/coverage.json. PR and merge-queue CI must pass before merge.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-16T16:23:27.004890Z ef5bebf PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@github-actions

Copy link
Copy Markdown
Contributor

Release Preview

When this PR is squash-merged, @happyvertical/pdf will receive a patch version bump based on the PR title's conventional commit format.

What happens on merge?

  1. Tests run on main branch
  2. The squash commit message is validated
  3. Version is bumped automatically
  4. Package is published to npm.happyvertical.com (then mirrored to npmjs)
  5. Git tag is created

No manual intervention needed.

@willgriffin
willgriffin added this pull request to the merge queue Oct 16, 2026
Merged via the queue into main with commit 40bde00 Oct 16, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: publish npmjs mirror tarball as an explicit local path

1 participant