chore(wizard): refresh bundle hash to unblock CI on main#588
Merged
Conversation
The wizard bundle assets (index.html) and manifest committed in #587 are correct, but the hash committed alongside them was stale -- it didn't match the SHA-256 over the manifest's source closure. CI's wizard_bundle_freshness check (also picked up by cli-test, since the test lives under cli/tests) failed on every push to main. Recompute the hash from the current sources via: npm --prefix frontend run build:wizard Only cli/src/wizard/bundle-meta/index.hash changes; the bundle itself and the manifest match what #587 already committed. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Summary
mainhas been red since chore(branding): refresh README banner and NyxID wordmark lockup #587 was merged — bothCI Gate / CLI TestandCI Gate / CLI Wizard Bundle Freshnessfail on the samewizard_bundle_is_freshassertion.cli/src/wizard/assets/index.html) and manifest, but the committedcli/src/wizard/bundle-meta/index.hashwas stale — it didn't match the SHA-256 over the source closure listed in the manifest.npm --prefix frontend run build:wizard(under the pinned Node 22). Onlyindex.hashchanges; the bundle and manifest from chore(branding): refresh README banner and NyxID wordmark lockup #587 are byte-identical with what the rebuild produces, confirming the bundle itself was correct and only the hash slipped.Why both CI jobs were red on a single failure
Both CI jobs execute the exact same test:
cli-testrunscargo nextest run -p nyxid-cli --profile ci, which sweepscli/tests/and includeswizard_bundle_freshness.rs. CI showed271 passed, 1 failedwith the one failure beingnyxid-cli::wizard_bundle_freshness wizard_bundle_is_fresh.wizard-bundle-freshnessrunscargo test -p nyxid-cli --test wizard_bundle_freshnessdirectly.Fixing the hash unblocks both.
Test plan
cargo test -p nyxid-cli --test wizard_bundle_freshnesspasses locally🤖 Generated with Claude Code