Repository navigation
chore: update LVBT repository standard to v0.4.5 - #8
Merged
Merged
Conversation
Apply the reviewed v0.4.5 release with its own updater.
WillieCubed
enabled auto-merge (rebase)
September 28, 2026 03:57
The package-scope rename in the v0.4.5 update made one assertion longer than Prettier's line width. 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
Moves this repository to LVBT repository standard v0.4.5.
Overview of Changes
The vendored standard in
.lvbt/web-platform/is replaced by v0.4.5, and the release's own migrations update the files it manages. The v0.4.5 release describes what changed.This pull request was opened by the
Publish standardworkflow when the release was tagged, and it merges itself onceValidatepasses. IfValidatefails, fix the repository on this branch; a newer release closes this pull request and opens its own.Follow-ups
None.