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.
Made expectEvent return the event that was found. (#129)
Fix expectEvent.inTransaction when there are conflicting events. (#133)
Breaking change
The fix to expectEvent.inTransaction may break some tests that were not using the API as intended, or which were causing a false positive assertion. If the emitter argument was a contract instance, the event that the assertion found in the transaction was not guaranteed to have originated in that particular contract instance at that address, it could also have generated in a different instance of the same contract. This is no longer the case, and may be the cause of a test breaking after the update.
0.5.6 (2020-06-01)
Deprecated expectEvent.not in favor of expectEvent.notEmitted. (#121)
Added expectEvent.notEmitted() for asserting absence of events in Truffle or Web3 receipts. (#121)
How to upgrade from 0.5.5
These changes are only necessary to get rid of the new deprecation warning.
If you have a receipt:
await expectEvent.not.inTransaction(receipt.tx, contract, event)
⚠️ 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)
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...
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.
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](https://github.com/omgnetwork/plasma-contracts/network/alerts).
Bumps got to 12.1.0 and updates ancestor dependencies got, web3, openzeppelin-test-helpers and solidity-coverage. These dependencies need to be updated together.
Updates
got
from 7.1.0 to 12.1.0Release notes
Sourced from got's releases.
... (truncated)
Commits
ad92afa
12.1.0861ccd9
Disable redirects to UNIX sockets (#2047)4cdcca3
Check error instance for arguments test (#2044)22d58fb
Addresponse.ok
(#2043)c25af09
Meta tweaks62455f5
Meta tweaks6f5c7ce
Test Node.js 18c693422
12.0.498ca618
Fix accidental test deletionbb8eca9
Remove stream lock - unreliable since Node 17.3.0Updates
web3
from 1.2.1 to 1.9.0Release notes
Sourced from web3's releases.
Changelog
Sourced from web3's changelog.
... (truncated)
Commits
db5f505
Build for 1.9.0908604b
v1.9.0c564ebe
Build commit for 1.9.0-rc.08ae1e23
v1.9.0-rc.0da51334
npm i and changelog update2b3fb3a
Nikos/5835/websocket provider keeps important error message back (#5884)ef23642
dependencies updates (#5885)8d369a9
Nikos/5821/transaction type fix (#5856)afa2943
fix types default export (#5852) (#5866)e4b25bf
Add optional paramhex
togetTransaction
andgetBlock
. (#5845)Maintainer changes
This version was pushed to npm by jdevcs, a new releaser for web3 since your current version.
Updates
openzeppelin-test-helpers
from 0.4.3 to 0.5.1Changelog
Sourced from openzeppelin-test-helpers's changelog.
... (truncated)
Commits
c59a7d1
0.5.15bdd2e6
Add changelog entry326c397
0.5.1-rc.0372b3cb
Remove truffle env check8e21562
0.5.02f1bd41
0.5.0-rc.33fc894e
Add notes to readme and changelog re. truffle migrations2ad267f
Update truffle migration config on integration testb5ceeff
Make@truffle/contract
a dependency1006e2c
Add singletons check to integration testsUpdates
solidity-coverage
from 0.7.12 to 0.8.2Release notes
Sourced from solidity-coverage's releases.
... (truncated)
Changelog
Sourced from solidity-coverage's changelog.
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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/omgnetwork/plasma-contracts/network/alerts).