Repository navigation
chore: set the build identifier for the model integrity release - #14
Merged
Merged
Conversation
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
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.
Summary
Sets
BLOCK_BUILDtobb-model-integrity-20260927, so that after the next deploy the live page's build identifier differs from the current production build (bb-share-copy-20260926) and DEPLOYMENT.md's live verification can confirm the new release is serving. The identifier had not changed since #6. The browser suite reads the value from source, so it checks the new identifier automatically.Validation
npm run verifypasses (775 tests).npm run test:e2epasses against the same tree onmain; only this constant changes.npm audit --audit-level=lowhas been reviewed when dependencies changed. No dependency changes.Data or model changes
Not applicable.
Security
None.