Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency socks to v2 #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 7, 2019

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
socks ^1.1.10 -> ^2.0.0 age adoption passing confidence

Release Notes

JoshGlazebrook/socks

v2.7.1

Compare Source

v2.7.0

Compare Source

v2.6.2

Compare Source

v2.6.1

Compare Source

v2.6.0

Compare Source

Adds support for custom auth methods.

v2.5.1

Compare Source

v2.5.0

Compare Source

Changed behavior of createConnection/createConnectionChain option validation to where errors are surfaced via callback (if provided), or through promise rejection.

v2.4.4

Compare Source

v2.4.3

Compare Source

v2.4.2

Compare Source

v2.4.1

Compare Source

v2.4.0

Compare Source

v2.3.3

Compare Source

v2.3.2

Compare Source

v2.3.1

Compare Source

  • When creating connections, 'ipaddress' can now be a hostname (proxyserver1.com for example)
  • 'host' property added to proxy config, this is intended to replace 'ipaddress'. (ipaddress remains for backwards compatibility)

The following are equivalent:

Using 'ipaddress':

const options = {
  proxy: {
    ipaddress: '159.203.75.200', // ipv4 or ipv6 or hostname
    port: 1080,
    type: 5 // Proxy version (4 or 5)
  },

  command: 'connect', // SOCKS command (createConnection factory function only supports the connect command)

  destination: {
    host: '192.30.253.113', // github.com (hostname lookups are supported with SOCKS v4a and 5)
    port: 80
  }
};

Using 'host'

const options = {
  proxy: {
    host: '159.203.75.200', // ipv4 or ipv6 or hostname
    port: 1080,
    type: 5 // Proxy version (4 or 5)
  },

  command: 'connect', // SOCKS command (createConnection factory function only supports the connect command)

  destination: {
    host: '192.30.253.113', // github.com (hostname lookups are supported with SOCKS v4a and 5)
    port: 80
  }
};

Hostnames are now allowed:

const options = {
  proxy: {
    host: 'proxy1.proxyservers.com', // ipv4 or ipv6 or hostname
    port: 1080,
    type: 5 // Proxy version (4 or 5)
  },

  command: 'connect', // SOCKS command (createConnection factory function only supports the connect command)

  destination: {
    host: '192.30.253.113', // github.com (hostname lookups are supported with SOCKS v4a and 5)
    port: 80
  }
};

v2.3.0

Compare Source

v2.2.3

Compare Source

v2.2.2

Compare Source

This release fixes an issue where socks would throw an error on Electron.

v2.2.1

Compare Source

v2.2.0

Compare Source

Changes

  • Internally we now reference the socket as a duplex stream. Since (Socket instanceof Duplex === true) this shouldn't break anything, but you can now pass in a Duplex as existing_socket (if you're using this for some reason).

v2.1.6

Compare Source

This fixes an issue with the 'receivebuffer' import.

v2.1.5

Compare Source

Fixes incoming data flow issues. It's highly recommended to upgrade to this version if you're using 2.x.x

v2.1.4

Compare Source

v2.1.3

Compare Source

v2.1.2

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

v2.0.5

Compare Source

v2.0.4

Compare Source

v2.0.3

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented Mar 25, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant