search

telosnetwork / telos-evm-docker

Automated Telos EVM development and automated test framework
Apache License 2.0
12 stars 3 forks source link

Bump got, @nomiclabs/truffle-contract, @truffle/contract and solidity-coverage in /tests/test_openzeppelin/openzeppelin-contracts #73

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps got to 12.1.0 and updates ancestor dependencies got, @nomiclabs/truffle-contract, @truffle/contract and solidity-coverage. These dependencies need to be updated together.

Updates got from 7.1.0 to 12.1.0

Release notes

Sourced from got's releases.

v12.1.0

Improvements

Fixes

https://github.com/sindresorhus/got/compare/v12.0.4...v12.1.0

v12.0.4

  • Remove stream lock - unreliable since Node 17.3.0 bb8eca924c338ca12d5b90d6a26aa28dbddb42ee

v12.0.3

  • Allow more types in the json option (#2015) eb045bf

https://github.com/sindresorhus/got/compare/v12.0.2...v12.0.3

v12.0.2

  • Fix encoding option with {responseType: 'json'} (#1996) 0703318

https://github.com/sindresorhus/got/compare/v12.0.1...v12.0.2

v12.0.1

  • Fix nock compatibility (#1959) bf39d2c
  • Fix missing export of Request TypeScript type (#1940) 0f9f2b8

https://github.com/sindresorhus/got/compare/v12.0.0...v12.0.1

v12.0.0

Introducing Got v12.0.0 :tada:

Long time no see! The latest Got version (v11.8.2) was released just in February ❄️ We have been working hard on squashing bugs and improving overall experience.

If you find Got useful, you might want to sponsor the Got maintainers.

This package is now pure ESM

Please read this. Also see sindresorhus/got#1789.

  • Please don't open issues about [ERR_REQUIRE_ESM] and Must use import to load ES Module errors. This is a problem with your setup, not Got.
  • Please don't open issues about using Got with Jest. Jest does not fully support ESM.
  • Pretty much any problem with loading this package is a problem with your bundler, test framework, etc, not Got.
  • If you use TypeScript, you will want to stay on Got v11 until TypeScript 4.6 is out. Why.
  • If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.

... (truncated)

Commits


Updates @nomiclabs/truffle-contract from 4.2.23 to 4.5.10

Release notes

Sourced from @​nomiclabs/truffle-contract's releases.

v5.3.13 – Life is like...

I guess it's true: you never know what you're going to get! 💝

This release fixes a bug to truffle unbox that caused community Truffle Boxes to fail to download. Thanks @​CaleTeeter and @​patrickalphac for identifying this problem.

Apologies to anyone who ran into this bug... hope this fixes things for you! 🙇

How to upgrade

We recommend upgrading to the latest version of Truffle by running:

npm uninstall -g truffle
npm install -g truffle

Changelog

Bug fixes

Internal improvements

  • Allow a few missing values in artifactor/compile-common internals (#4126 by @​bergarces)

v5.3.11 – Mrs. Malinda Russell's Rich Black Cake 🍰

Salutations and happy Friday! 👋🏾

We have another release for you! This week offers a couple of bug fixes, internal improvements and version updates. truffle unbox will now recognize branches that have slashes, like truffle unbox <orgOrName>/repo#branch/with/slashes. In case you didn't know you can create your own Truffle boxes which is a great way to bootstrap your Truffle project: hooray! :tada:

Enjoy, and as always please feel free to reach out through one of these resources.

Changelog

Fixes

Dependency updates

Internal improvements

Commits
  • 0ccf74f Publish
  • 83b7adc contract: bump browserify and exorcist versions
  • 9b5c8f3 Publish
  • ee8331e Merge branch 'develop' of github.com:trufflesuite/truffle into eip155-work
  • e28280c Remove cached chain id invalidation in contract
  • c67bc3c Publish
  • 59e8c2c Remove chainId from web3.eth.sendTransaction
  • 1893747 Upgrade web3 to 1.3.5
  • 677ca39 Publish
  • b626080 Cache chain ID to avoid extra network requests
  • Additional commits viewable in compare view


Updates @truffle/contract from 4.3.20 to 4.6.10

Release notes

Sourced from @​truffle/contract's releases.

v5.3.13 – Life is like...

I guess it's true: you never know what you're going to get! 💝

This release fixes a bug to truffle unbox that caused community Truffle Boxes to fail to download. Thanks @​CaleTeeter and @​patrickalphac for identifying this problem.

Apologies to anyone who ran into this bug... hope this fixes things for you! 🙇

How to upgrade

We recommend upgrading to the latest version of Truffle by running:

npm uninstall -g truffle
npm install -g truffle

Changelog

Bug fixes

Internal improvements

  • Allow a few missing values in artifactor/compile-common internals (#4126 by @​bergarces)

v5.3.11 – Mrs. Malinda Russell's Rich Black Cake 🍰

Salutations and happy Friday! 👋🏾

We have another release for you! This week offers a couple of bug fixes, internal improvements and version updates. truffle unbox will now recognize branches that have slashes, like truffle unbox <orgOrName>/repo#branch/with/slashes. In case you didn't know you can create your own Truffle boxes which is a great way to bootstrap your Truffle project: hooray! :tada:

Enjoy, and as always please feel free to reach out through one of these resources.

Changelog

Fixes

Dependency updates

Internal improvements

Commits
Maintainer changes

This version was pushed to npm by dongming.hwang, a new releaser for @​truffle/contract since your current version.


Updates solidity-coverage from 0.7.16 to 0.8.2

Release notes

Sourced from solidity-coverage's releases.

0.8.2

What's Changed

New Contributors

Full Changelog: https://github.com/sc-forks/solidity-coverage/compare/v0.8.1...v0.8.2

0.8.1

What's Changed

Full Changelog: https://github.com/sc-forks/solidity-coverage/compare/v0.8.0...v0.8.1

0.8.0

Hi!

⚠️ This version requires Hardhat >= 2.11.0 (Ethereum Merge)

New Features

A central focus of the 0.8.0 release is improving the coverage tool's branch detection.

Beginning with this version the following syntax is measured as a branch:

OR conditions

When a logical expression is composed with the || operator, both sides can be considered branches. To test the entire expression

if (a == 1 || a == 2)

... a must equal 1, 2 and neither of those values. (Thanks to Gnosis engineer @​rmeissner for proposing this in #175)

Screen Shot 2021-01-12 at 9 41 09 PM

Ternary Conditionals

Long ago, when Solidity was 0.4, solidity-coverage treated ternary conditionals like regular if/else statements. Some language improvements v0.5 subsequently made this impossible. Now it's back...

Screen Shot 2021-01-12 at 9 47 43 PM

Modifier Invocations

Solidity-coverage already covers the code within modifier definitions. However, each modifier invocation at the function level should really be considered its own branch. Some of the most critical logic in Solidity contracts is handled this way (ex: onlyOwner). Testing the pass/fail cases for each occurrence of these gates protects you from accidentally removing them during a refactor.

Because it's possible to write a modifier which performs a preparatory task and never reverts, there's a new option (modifierWhitelist) which allows you to exclude specific modifiers from branch measurement.

... (truncated)

Changelog

Sourced from solidity-coverage's changelog.

Changelog

0.8.1 / 2022-09-06

0.8.0 / 2022-09-05

0.7.21 / 2022-04-24

0.7.20 / 2022-02-15

0.7.19 / 2022-02-09

0.7.18 2022-01-17

Commits


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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/telosnetwork/telos-evm-docker/network/alerts).
dependabot[bot] commented 1 year ago

Looks like these dependencies are up-to-date now, so this is no longer needed.