chore: Adopt organization package scope across Labs - #31
Merged
Merged
Conversation
Use the published organization scope for workspace packages and their consumers. Keep deployment planning compatible with older base commits. Clarify Cloudflare provisioning for account-owned tokens. Co-authored-by: Codex <noreply@openai.com>
Preview deployments
|
This branch was successfully deployed
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
Labs now uses the organization package scope throughout its workspace, generated labs, and deployment workflows. This keeps package names compatible with GitHub Packages and lets migrations and deployments work across the rename.
Overview of Changes
The internal brand, UI, runtime, CLI, and app packages use
@lasvegasfortransit/*. Imports, filters, CI, Renovate, lockfile entries, and documentation follow the same names. Deployment planning accepts the old scope only when reading a base commit, so a PR that crosses the rename can still calculate affected labs while new commits must use the current scope.The home app's Astro lint task now waits for
astro syncthrough Turbo. The Cloudflare provisioning guide identifies account-owned tokens, narrows their account and zone resources, gives direct GitHub secret commands, and treats account and zone IDs as visible variables.Validation:
pnpm check,pnpm build, andpnpm test:e2epass on the committed branch.Follow-ups
The current Labs provisioner creates a Web Analytics property for
labs.lasvegasfortransit.org. The organization guidance now prefers the existing apex-domain property for alllasvegasfortransit.orgsubdomains; that shared provisioning contract needs an upstream repository-tooling change before Labs can adopt it without patching the vendored standard.