Bump vintage_net from 0.11.1 to 0.13.1

[dependabot]

Bumps vintage_net from 0.11.1 to 0.13.1.

Release notes

Sourced from vintage_net's releases.

v0.13.0

This release has a breaking change if you're using the UdhcpcHandler behaviour. This should be a rare use case. Use the "dhcp_options" property now.

• Changed
  • Add "dhcp_options" to interface properties. This lets applications use information provided by DHCP servers in an easy way. It removes the need to process events from udhcpc directly, and therefore, the UdhcpcHandler behaviour is now a private API and may be removed in the future.
  • Fix some references to iodata that should have been chardata.

v0.12.2

• Changed
  • Add VintageNet.info_as_ansidata/1. This lets you get the same results as VintageNet.info, but in a way that's easy to put on a web page or send to a server, etc.
  • Support updating network configuration even when it can't be persisted. Previously if there was an error saving the configuration and persist: true (the default), the configuration wouldn't be applied. This turned out to be problematic when trying to get some devices fixed. Now the device won't have the right config on reboot, but it can be reached over the network to be fixed.

v0.12.1

• Changed
  • The list of name servers that VintageNet uses when configuring the name resolve is now available by running VintageNet.get(["name_servers"]).

v0.12.0

This release has two potentially breaking changes:

1. Elixir 1.11 is now the minimum supported Elixir version.
2. VintageNet.PropertyTable has been extracted to its own library and is now just PropertyTable. Most users did not use VintageNet.PropertyTable directly, but if you did, you'll need to update the references.

• Changed
  • Extract VintageNet.PropertyTable to its own library. Note that many improvements were made to PropertyTable including renaming functions for consistency and changing the events. Code was added to VintageNet to hide these changes for now. Longer term, we'll be making things more consistent, but the hope is that the PropertyTable changes are transparent to VintageNet users in this release.
  • Support specifying absolute paths to network configuration commands. While this is not preferred, it's useful in some scenarios.
  • Redact more kinds of secrets in VintageNet.info

v0.11.5

... (truncated)

Changelog

Sourced from vintage_net's changelog.

[v0.13.1] - 2023-03-15

This release fixes deprecation warnings when using Elixir 1.15.

[v0.13.0] - 2023-01-22

This release has a breaking change if you're using the UdhcpcHandler behaviour. This should be a rare use case. Use the "dhcp_options" property now.

• Changed
  • Add "dhcp_options" to interface properties. This lets applications use information provided by DHCP servers in an easy way. It removes the need to process events from udhcpc directly, and therefore, the UdhcpcHandler behaviour is now a private API and may be removed in the future.
  • Fix some references to iodata that should have been chardata.

[v0.12.2] - 2022-08-04

• Changed
  • Add VintageNet.info_as_ansidata/1. This lets you get the same results as VintageNet.info, but in a way that's easy to put on a web page or send to a server, etc.
  • Support updating network configuration even when it can't be persisted. Previously if there was an error saving the configuration and persist: true (the default), the configuration wouldn't be applied. This turned out to be problematic when trying to get some devices fixed. Now the device won't have the right config on reboot, but it can be reached over the network to be fixed.

[v0.12.1] - 2022-06-01

• Changed
  • The list of name servers that VintageNet uses when configuring the name resolve is now available by running VintageNet.get(["name_servers"]).

[v0.12.0] - 2022-04-27

This release has two potentially breaking changes:

1. Elixir 1.11 is now the minimum supported Elixir version.
2. VintageNet.PropertyTable has been extracted to its own library and is now just PropertyTable. Most users did not use VintageNet.PropertyTable directly, but if you did, you'll need to update the references.

• Changed
  • Extract VintageNet.PropertyTable to its own library. Note that many improvements were made to PropertyTable including renaming functions for consistency and changing the events. Code was added to VintageNet to hide these changes for now. Longer term, we'll be making things more consistent,

... (truncated)

Commits

• 0e48d73 v0.13.1 release
• ca57cf8 Update CircleCI script to new style
• 909791d Bump beam_notify to fix warnings
• 65256a3 Fix Elixir 1.5 deprecation warning
• 2b17359 Bump ex_doc and excoveralls
• a14dff6 FIx some years in changeling
• 393a60d Remove State modules
• 68f30e2 Bump elixir_make from 0.7.3 to 0.7.5
• 8c9faff Fix Elixir 1.15 Logger warning
• 80183fe Bump deps
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)