search

peppersec / thunder_bridge

2 stars 29 forks source link

Bump minimatch, solidity-coverage and truffle-flattener in /contracts #48

Open dependabot[bot] opened 2 years ago

dependabot[bot] commented 2 years ago

Bumps minimatch to 3.0.4 and updates ancestor dependencies minimatch, solidity-coverage and truffle-flattener. These dependencies need to be updated together.

Updates minimatch from 0.3.0 to 3.0.4

Commits
Maintainer changes

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


Updates solidity-coverage from 0.4.15 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

0.7.16 / 2021-03-04

0.7.15 / 2021-02-16

0.7.14 / 2021-01-14

  • Support file scoped function definitions for solc >= 0.7.4
  • Upgrade @​solidity-parser/parser to v0.11.0

0.7.13 / 2020-12-03

  • Use default artifact paths for hardhat >= 2.0.4 (Fixes hardhat-deploy bug)

... (truncated)

Commits


Updates truffle-flattener from 1.2.3 to 1.6.0

Release notes

Sourced from truffle-flattener's releases.

truffle-flattener v1.5.0 released

The new version of truffle-flattener supports Solidity 0.7, and works out of the box with Buidler.

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/peppersec/thunder_bridge/network/alerts).