Bump semver and zos

[dependabot]

Bumps semver to 5.7.2 and updates ancestor dependency zos. These dependencies need to be updated together.

Updates semver from 5.7.0 to 5.7.2

Release notes

Sourced from semver's releases.

v5.7.2

5.7.2 (2023-07-10)

Bug Fixes

• 2f8fd41 #585 better handling of whitespace (#585) (@​joaomoreno, @​lukekarrys)

Changelog

Sourced from semver's changelog.

5.7.2 (2023-07-10)

Bug Fixes

• 2f8fd41 #585 better handling of whitespace (#585) (@​joaomoreno, @​lukekarrys)

5.7

• Add minVersion method

5.6

• Move boolean loose param to an options object, with backwards-compatibility protection.
• Add ability to opt out of special prerelease version handling with the includePrerelease option flag.

5.5

• Add version coercion capabilities

5.4

• Add intersection checking

5.3

• Add minSatisfying method

5.2

• Add prerelease(v) that returns prerelease components

5.1

• Add Backus-Naur for ranges
• Remove excessively cute inspection methods

5.0

• Remove AMD/Browserified build artifacts
• Fix ltr and gtr when using the * range
• Fix for range * with a prerelease identifier

Commits

• f8cc313 chore: release 5.7.2
• 2f8fd41 fix: better handling of whitespace (#585)
• deb5ad5 chore: @​npmcli/template-oss@​4.16.0
• c83c18c 5.7.1
• 956e228 Correct typo in README
• See full diff in compare view

Maintainer changes

This version was pushed to npm by lukekarrys, a new releaser for semver since your current version.

Updates zos from 2.2.3 to 2.4.3

Release notes

Sourced from zos's releases.

v2.4.2

This patch for version 2.4 includes several fixes. One of the most important ones is that the zos CLI now plays nice with truffle artifacts by preserving the contract deployment addresses in the build/contracts/Contract.json files when compiling. Also, both the CLI and the js library now work fine when being hoisted, such as when using yarn workspaces or lerna.

Fixed

• The -f flag was used for specifying the --from option in several commands, and at the same time for setting the --force toggle in push and set-admin; now it is only used for --from, and --force only accepts the long form. (#1123) (thanks @​pcowgill for the report!)
• Preserve truffle deployment info stored in contract artifacts when compiling. (#1100)
• Linked EVM packages lookup works properly when dependencies are hoisted. (#1110) (thanks @​PaulRBerg for the report!)
• Do not throw an error if the contracts local folder is missing. (#1107)
• Properly detect when an Ethereum Package is on an older version for pushing it to the local network for development. (#1119)
• Store proxy admin address for the first proxy created in a network. (#1124)
• Fixed errors from logger that occured in verbose mode only when uploading solidity libraries or upgrading instances. (#1112) (thanks @​hickscorp for the report!)
• Add explicit dependency on web3-utils, that could cause issues when checksumming addresses. (#1114) (thanks @​chentschel for the report!)

v2.4.1

This patch fixes issues on the CLI to work on Windows, and when being installed with Yarn. This required us moving to our own fork of resolver-engine, which is used under the hoods by the compiler and verifier, and cutting a new release of the spinnies library.

Fixed

• zos compile now works properly on Windows. (#1066)
• Spinners are now shown properly on Windows. (#1067)
• Installation issues with yarn now fixed. (#1059)

v2.4.0

This release adds some improvements on zos outputs, adds a new zos compile command to compile your contracts, incorporates a new networks.js file to manage your networks, and finally implements a couple of handy commands to interact with your contracts from the command line.

Nicer outputs

While in 2.3 we focused on improving the ZeppelinOS inputs, by implementing friendlier interacting commands, in 2.4 we focused on improving its outputs. We removed much of the verbosity that plagued the CLI, and show you only what actually matters. We also integrated the awesome spinnies library for presenting long-running operations.

If you miss having the CLI filling your terminal with lots of output, you can bring back the old mode (with even more info!) by using the --verbose flag in any command.

Standalone CLI

You can now run ZeppelinOS without depending on truffle. Version 2.4 ships with a new zos compile command that will install and run solcjs on your behalf, and compile your Solidity contracts when needed. As a bonus feature, zos will check if there is a solc on your PATH that matches the requested version, and use it instead of the javascript port - this yields a 6x speed improvement in compile times. It's worth mentioning that the artifacts generated by zos compile follow the same format as truffle's.

Also, zos init will now create a framework-independent networks.js file with the description of the network connections for your project. The format is similar to that of truffle-config.js, with an additional protocol key that allows you to specify whether you want to connect to your node via http(s), ws(s), ipc, etc.

Of course, ZeppelinOS remains fully compatible with truffle. If the CLI detects a truffle(-config).js on your project root, it will still rely on truffle for compiling your contracts, and will load the networks configuration from truffle as usual.

Interacting with your contracts from the command line

We have added new commands for interacting with your contract instances easily. You can now send a transaction or move funds directly from the terminal, without having to spawn a javascript console.

You can try out the following commands:

• zos balance queries the balance of an account, either in ETH or in an ERC20

... (truncated)

Commits

• 32a238b v2.4.3
• 11cc7f6 Update package locks
• 8b21735 Lint
• 824e01a Update repository URL to new one
• 35e8120 v2.4.2
• 0bca235 Update changelogs
• ba8e3bb Set proxy admin on first create
• 06cb6c4 Remove repeated flag -f from push and set-admin (#1122)
• 3b42655 Update changelog
• 3538c50 Check outdated dependencies to push (#1119)
• 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.