Repository navigation
fix(chatgpt): pin browser targets for reproducible bundles - #3220
Merged
Merged
Conversation
|
This was referenced Oct 9, 2026
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.
The embedded ChatGPT app changed according to browser configuration outside the checkout. A developer-directory
.browserslistrctargeting Chrome 51 / Safari 10 was inherited locally, while CI used Rsbuild 2's default targets. That changed both CSS lowering and JavaScript output and caused the byte-for-byte freshness failure in #3219.Pin the extension's browser targets to the existing Rsbuild 2 defaults (Chrome/Edge 107, Firefox 104, Safari 16), and regenerate the self-contained app through the maintained build script. The generated app is byte-identical to the independent Linux regeneration in #3200; the server bundle is unchanged. The external browser configuration remains untouched.
Verification through the Bazel-managed Node runtime:
check:embeddedwith the ancestor configuration present.CI=true.8fb719178d012702fe07f1f3894e45b02bb218f89c51857533bb72ca90e2e9b7).Fixes #3219. This completes the cause investigation behind #3200's generated-file refresh and prevents a developer's ancestor configuration from reintroducing it.