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.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
Requests using proxy settings from env - jjyr, pull/1438
This enables ureq to use proxy settings from env, it solves lots of pain in network restricted environments.
🤕 Fixes
Update binary-install to v0.4.1 - drager, pull/1407
Release v0.4.0 of binary-install introduced a regression that caused failures on some platforms. This release fixes that regression.
Allow npm binary upgrades - net, pull/1439
Fixes an issue where upgrading
wasm-pack
via NPM would not update the underlying binary.Previously, the binary was stored in the
binary-install
package's directory without versioning, causing version upgrades to silently fail as the old binary continued to be used.The binary is now stored in
node_modules/wasm-pack/binary/
, ensuring proper version updates when upgrading the package.Before: Upgrading from
0.12.1
to0.13.0
would continue using the0.12.1
binaryAfter: Each
wasm-pack
version manages its own binary, enabling proper version upgrades🛠️ Maintenance