fix(ci): Publish Analytics with pnpm - #4
Merged
Merged
Conversation
Use the repository's pinned pnpm release for OIDC trusted publishing. Keep the release contract covered before the initial package release. Co-authored-by: Codex <noreply@openai.com>
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.
TL;DR
Analytics package releases now use the repository's pinned pnpm 11.25 release.
Overview of Changes
The release workflow now runs
pnpm publish --access public --no-git-checksthrough npm trusted publishing. Its contract test rejects regressions to a direct npm publication command. The package remains at0.1.0; nothing has been published.Follow-ups
Configure the npm trusted publisher, publish the initial release after this merges, and deploy the Analytics collector with scoped Cloudflare Actions credentials.
Validation passed across all 16 repository tasks, including 60 unit and Worker tests, three Playwright tests, package validation, and Wrangler dry runs.