Repository navigation
chore: publish LVBT template standard v0.7.1 - #14
Merged
Merged
Conversation
Generate the template from the published release and its exact source. Keep setup, validation, audit, contribution and release processes in the shared packages, including uncached required security checks. Co-authored-by: Codex <noreply@openai.com>
Regenerate from the exact merged patch release with resolvable workflow pins and checksum-verified scanner setup. Preserve the complete required validation gate and generated provenance. Co-authored-by: Codex <noreply@openai.com>
WillieCubed
changed the title
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 repositories created from this template start on published LVBT standard v0.7.1.
Overview of Changes
Regenerate the template from the exact release source with the canonical publisher. Shared commands, vendored packages, hooks, dependency pins, contribution guidance and thin workflows follow the organization process. The required gate preserves full-history secret scanning and the existing high advisory threshold as uncached tasks. Fresh setup, repeat setup and read-only preflight passed without cloud credentials; all 5 required tasks passed without cached results.
Follow-ups
None.