Skip to content

build(deps): bump proxy-from-env from 1.1.0 to 2.0.0#2725

Merged
sjinks merged 1 commit intotrunkfrom
dependabot/npm_and_yarn/proxy-from-env-2.0.0
Feb 10, 2026
Merged

build(deps): bump proxy-from-env from 1.1.0 to 2.0.0#2725
sjinks merged 1 commit intotrunkfrom
dependabot/npm_and_yarn/proxy-from-env-2.0.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 9, 2026

Bumps proxy-from-env from 1.1.0 to 2.0.0.

Release notes

Sourced from proxy-from-env's releases.

v2.0.0

What's Changed

  • Remove url.parse usage to avoid DEP0169 DeprecationWarning (#30).

  • Use WHATWG URL constructor to parse strings instead of url.parse. This may cause getProxyForUrl to return an empty string instead of a proxy URL when the input is an invalid URL.

  • Switch from CJS to ESM. When import syntax is used, the minimum compatible Node.js version is v12.17.0. When require is used, the minimum compatible Node.js version is v20.19.0, because that version introduced require(esm) support.

  • Drop detection of npm_config_-prefixed environment variables, which was introduced in 1.1.0. Now the behavior is back to version 1.0.0. This should not affect users in practice, because the npn ecosystem dropped support for these environment variables many years ago (#13).

Full Changelog: Rob--W/proxy-from-env@v1.1.0...v2.0.0

Commits
  • f4d1be8 2.0.0
  • 83cb866 Update README
  • e32b37e Replace url.parse with WHATWG URL API
  • 00ac7ff Drop support for npm_config_* prefixes
  • abefaff Add sideEffects:false to package.json for easier tree shaking
  • 3549220 test: simplify testProxyUrl
  • 2f8948f CI: Run tests with all supported Node.js versions
  • 582fa7f Add test for difference between url.parse and WHATWG URL
  • 7c0264e Migrate from CommonJS to ESM
  • 520d25a Upgrade to eslint 9 with flat config
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/proxy-from-env ^2.0.0 🟢 4.5
Details
CheckScoreReason
Code-Review⚠️ 1Found 4/30 approved changesets -- score normalized to 1
Binary-Artifacts🟢 10no binaries found in the repo
Maintained🟢 1015 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
License🟢 10license file detected
Fuzzing⚠️ 0project is not fuzzed
Vulnerabilities🟢 100 existing vulnerabilities detected
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0

Scanned Files

  • package.json

Bumps [proxy-from-env](https://github.com/Rob--W/proxy-from-env) from 1.1.0 to 2.0.0.
- [Release notes](https://github.com/Rob--W/proxy-from-env/releases)
- [Commits](Rob--W/proxy-from-env@v1.1.0...v2.0.0)

---
updated-dependencies:
- dependency-name: proxy-from-env
  dependency-version: 2.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/proxy-from-env-2.0.0 branch from 7a078d1 to b89729e Compare February 10, 2026 20:17
@sonarqubecloud
Copy link

@sjinks sjinks self-assigned this Feb 10, 2026
@sjinks sjinks merged commit 79b0c9b into trunk Feb 10, 2026
19 checks passed
@sjinks sjinks deleted the dependabot/npm_and_yarn/proxy-from-env-2.0.0 branch February 10, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant