Skip to content
This repository was archived by the owner on Oct 16, 2026. It is now read-only.

fix(release): publish scoped packages as public - #1431

Merged
christso merged 1 commit into
mainfrom
fix/publish-public-scoped-packages
Jun 19, 2026
Merged

christso merged 1 commit into
mainfrom
fix/publish-public-scoped-packages

Conversation

@christso

Copy link
Copy Markdown
Collaborator

Summary

  • pass --access public for npm publishes
  • keeps the existing idempotent publish behavior while allowing first publish of new scoped packages

Why

The Publish workflow run 27806345794 created v4.41.2-next.1, published @agentv/core@4.41.2-next.1, then failed on the first publish of @agentv/sdk@4.41.2-next.1 with:

npm error Can't generate provenance for new or private package, you must set `access` to public.

Verification

  • bunx biome check scripts/publish.ts
  • bun scripts/publish.ts invalid-tag exits before publish and confirms script parses

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying agentv with  Cloudflare Pages  Cloudflare Pages

Latest commit: 52ad8d7
Status: ✅  Deploy successful!
Preview URL: https://0f820052.agentv.pages.dev
Branch Preview URL: https://fix-publish-public-scoped-pa.agentv.pages.dev

View logs

@christso
christso merged commit 44e9e3b into main Jun 19, 2026
8 checks passed
@christso
christso deleted the fix/publish-public-scoped-packages branch June 19, 2026 05:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant