Repository navigation
Publish Vercel bundles daily without rebuilding on data commits - #107
Merged
Merged
Conversation
1 of 10 tasks
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.
Complete the public-host preparation from #103/#101 on top of the independent product release #106. The 15-minute collector stays intact. A disabled-by-default GitHub workflow builds the existing Vite app in Actions and uploads prebuilt output daily at 08:17 UTC, on app changes, or manually. Data-only commits are excluded. Activation defaults to preview and requires an approved deployment credential; production/domain changes remain separate.
Publication validates current CBP data, crossing identities/counts, 30-day history coverage and its current observation, and USD/MXN data. A public manifest records source SHA and timestamps. Failed data/tests never replace the deployed site. The live-CBP client rejects malformed timestamps, times out requests, and retains newer browser data instead of downgrading to an older static fallback. npm audit now fails when the registry report is unavailable.
Verified preview: https://borderpulse-1aclctmdc-sbc1-codes-projects.vercel.app (protected, not public production). Deployment dpl_4dt2z2rNsmkrEsTw3VJv1WX8WTLx is Ready with no production alias; its log confirms prebuilt artifacts. Manifest runtime source is ba320b1; deployment metadata is b65c6f8, a later documentation/audit-only commit. Current head adds only verification documentation. Browser readback confirmed 42 live CBP crossings fetched at 2026-09-30T05:02:02.700Z, comparison history, canonical sharing, FX and automatic Adsterra. Bundled history has 403 snapshots.
Validation: Vercel packaging succeeded; 406 route navigations plus EN/ES desktop/mobile interactions passed; 18 publication/function tests and 4 refresh tests passed; real registry audit has zero high/critical and two previously accepted moderate advisories. GitHub release checks passed at b65c6f8. The operations runbook includes exact project-specific proposed DNS, captured Pages rollback, failure handling and activation steps.
No new application dependency, provider, credential, DNS or production change. Target $0 new monthly spend. Observed BorderPulse usage remains $0.27 and team credit consumption $2.46/$20, with up to one hour reporting delay: no production capacity claim. Two scheduled observations remain pending activation. Merge #106 first, retarget this PR to main, then wait for one matching collector/history run before enabling preview publication with an approved token. Preserve #87 separately.