chore: Update analytics repository standard to v0.4.4 - #13
Merged
Merged
Conversation
Adopt the current vendored standard and organization package scope for consumer configuration, hooks, workflows, and the lockfile. 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 now uses repository-tooling v0.4.4 and the GitHub Packages compatible
@lasvegasfortransit/*scope for its shared tooling.Overview of Changes
The vendored web standard and its provenance move from v0.2.8 to v0.4.4 through the documented updater. The repository's package declarations, imports, hooks, agent configuration, Renovate text, and lockfile use the organization scope that the new standard publishes. The contribution plugin reference is pinned to the same release.
This prepares the analytics package and collector for the current organization standard without changing their public analytics behavior or publishing a package. The repository has no
platform.jsonrequirement in the v0.4.4 validation contract, so production configuration remains in the existing collector runbook and Wrangler file.Validation:
pnpm checkpasses, including package validation, collector dry-run, and browser tests.Follow-ups
Production setup through the new manifest-driven bootstrap can be added when the collector's complete Cloudflare and GitHub resource contract is reviewed. No package publish or release is part of this PR.