Repository navigation
build: complete website recovery deploy and standard update - #95
Merged
Merged
Conversation
Apply the reviewed v0.6.3 release with its own updater. Co-Authored-By: Codex <noreply@openai.com>
Manual recovery bundles match the current production and preview routes, runtime settings, and separate databases. Stored credentials are retained in both environments, including optional and preview test credentials. Co-authored-by: Codex <noreply@openai.com>
This was referenced Oct 7, 2026
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
Complete the pending website recovery deploy and LVBT standard updates on the current site baseline. This replaces #71 and #74 while preserving linear history and the existing staging-to-production release process.
Overview of Changes
The vendored LVBT standard is updated to v0.6.3 using the original reviewed update. Manual recovery deployments use a separate typed
cfpackage that bundles the compiled site Worker and assets. Production and preview retain their separate databases, current routes, and deployment environment settings. Every stored secret is preserved, including optional production credentials and preview test credentials; the recovery command does not create credentials or change domains.Parity tests reproduced the older configuration's missing press routes and preview settings, then passed with the current contract.
pnpm checkand production and previewcf deploy --dry-runpass. Generated output includes secret-preservation metadata in both modes. Local dry runs used the supported no-Docker path because this project has no containers and the machine's Docker image inventory hangs. No provider changes were made by those checks.The fresh full scheduled audit on current main also passes internal and external links, production Lighthouse, and production dependency auditing: https://github.com/LasVegasForTransit/website/actions/runs/37660413444. The historical audit issues were resolved separately using that evidence.
Follow-ups
The reviewed-version release workflow continues to use Wrangler. Moving its upload and promotion steps to
cfrequires separate live receipt and exact-version acceptance.