chore(dx): update to repository standard v0.4.3 - #18
Merged
Merged
Conversation
The vendored web platform preset moves to v0.4.3. ACCESS_TEAM_DOMAIN and ACCESS_AUD are marked not sensitive: neither is a credential (a domain and an audience tag anyone with dashboard access can read), so setup now asks for them in plain view and shows them back in the report, matching every other non-secret platform value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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
lvwwd.org now uses repository standard v0.4.3, and
ACCESS_TEAM_DOMAINandACCESS_AUDare markedas values that are not credentials, so setup asks for them in plain view and shows them back.
Overview of Changes
pnpm standards:update --release v0.4.3 --applyrefreshed the vendored copy under.lvbt/web-platform. Nothing inapps/sitechanged exceptplatform.json:ACCESS_TEAM_DOMAIN(aCloudflare Access team domain) and
ACCESS_AUD(an Access application's audience tag) are neither ofthem a credential — anyone with dashboard access to the LVBT account can already read both — so each
now carries
"sensitive": false, the same treatment the Discord application ID, the Google OAuthclient ID, and the other non-secret platform values already get.
pnpm bootstrap --productionwilltype them visibly and show them back in its report the next time it runs, instead of hiding them like
a real secret.
pnpm checkpasses.Follow-ups
None.
🤖 Generated with Claude Code