fix: Publish analytics through GitHub Packages - #6
Merged
Merged
Conversation
WillieCubed
force-pushed
the
codex/github-packages
branch
from
September 20, 2026 03:23
2687470 to
484084e
Compare
Use the organization package registry and GitHub Actions token for the existing 0.1.0 release without changing its version. Co-authored-by: Codex <noreply@openai.com>
WillieCubed
force-pushed
the
codex/github-packages
branch
from
September 20, 2026 03:25
484084e to
73e63cc
Compare
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
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
Publishes
@lasvegasfortransit/analyticsthrough GitHub Packages with pnpm instead of the public npm registry.Overview of Changes
The package uses the GitHub organization scope required by GitHub Packages and declares
npm.pkg.github.comas its restricted registry. The release workflow receivespackages: write, authenticates with the repositoryGITHUB_TOKEN, and supports a manual run so the existing0.1.0release can be established without another version bump.The publishing contract test now verifies the GitHub Packages registry, restricted access, pnpm command, and workflow permissions.
pnpm checkpasses.Follow-ups
Consumer repositories need
packages: readand an authenticated@lvbtregistry configuration before replacing the temporary release artifact.