revert: roll back client transitive-resolutions (#7557 + #7560) — broke prod client (CSP)#7561
Merged
Merged
Conversation
Reverts the resolutions block to restore the last-known-good build output. #7557's build-tool pins (serialize-javascript v6->v7 etc.) changed the generated inline bootstrap script's bytes, so its sha256 no longer matched the CSP script-src hash allowlist the backend serves -> browser blocked the inline script -> broken client in production (CSP violation). Restores package.json + yarn.lock to 6307520 (pre-#7557). Security pins will be re-applied carefully, excluding the ones that alter build output / CSP hash. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7561 +/- ##
=======================================
Coverage 99.62% 99.62%
=======================================
Files 285 285
Lines 11971 11971
Branches 2920 2920
=======================================
Hits 11926 11926
Misses 45 45 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
🚑 Production rollback. The client is broken in prod with a CSP violation:
Root cause: #7557's
resolutionsbumped build tooling (notablyserialize-javascriptv6→v7) which changed the bytes of the generated inline bootstrap script. Itssha256no longer matches the CSPscript-srchash allowlist the backend serves, so the browser blocks it. Deploy + PR CI passed because neither runs the app under the real CSP.This restores
package.json+yarn.lockto63075201(pre-#7557) — byte-identical to the last-known-good state, so the build output (and its CSP hash) return to normal. Verified locally.Follow-up: re-apply the security pins carefully, excluding any that change build output / the CSP hash (the shipped-bundle-affecting ones), and add a CSP-hash check to catch this class before it ships.
🤖 Generated with Claude Code