fix(ci): Authenticate generated projects with GitHub Packages - #52
Merged
Merged
Conversation
Generated workspaces install private organization packages. Pass the workflow token during pnpm installation and configure the registry. 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
New LVBT projects can install private organization packages in GitHub Actions without a manual CI repair.
Overview of Changes
The basic, Astro, and Vite templates now configure GitHub Packages and pass each workflow's token to pnpm during installation. A repository-structure test keeps the three templates aligned with the setup used by the tooling repository.
Follow-ups
Consumers update their pinned preset through their normal standards-update workflow.