fix: integrity in http-url test#19954
Merged
alexander-akait merged 3 commits intomainfrom Sep 29, 2025
Merged
Conversation
Member
Author
|
Ideally, we should change those http url paths to the file which are infrequently updated. It can mostly prevent impacting out tests. :) |
CodSpeed Performance ReportMerging #19954 will degrade performances by 36.33%Comparing Summary
Benchmarks breakdown
|
alexander-akait
approved these changes
Sep 29, 2025
Member
Feel free to do it 👍 |
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
2 participants
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
What kind of change does this PR introduce?
Fixes https://github.com/webpack/webpack/actions/runs/18043508600/job/51348453106.
After
SHA-512hashing and Base64 encoding toREADME.mdfile, the result should be0ZvAGT9BNo7wDRzhVolbFzyjKiO77AZnNMcuIrOFrk5DIlwLa0QTz48mERI9Z5KhoIIUBNIMMTi10ZI8aWeMnQ==Did you add tests for your changes?
Existing
Does this PR introduce a breaking change?
No
If relevant, what needs to be documented once your changes are merged or what have you already documented?
No