Bump openzeppelin-test-helpers from 0.4.3 to 0.5.1
Bumps openzeppelin-test-helpers from 0.4.3 to 0.5.1.
Changelog
Sourced from openzeppelin-test-helpers's changelog.
0.5.1 (2019-10-10)
- Removed check for truffle environments on configure due to issues with truffle migrations.
0.5.0 (2019-10-10)
- Renamed the package to
@openzeppelin/test-helpers. (#78)- Removed hard-dependency on
truffle-contract(#75):
- An
environmentoption was added toconfigure, and can be set to eitherweb3ortruffle(default isweb3, but there is automatic detection of atruffleenvironment)singletonsreturnweb3 Contractinstances whenenvironmentis set toweb3expectEvent.inLogswas deprecated in favor ofexpectEvent, which receives the full receipt object (not just the logs), and supports both web3 and truffle contract receipts- Improved how revert reason checks (
expectRevert) are handled on unsupported environments. (#80)- Breaking:
configure'sweb3argument was removed and replaced byprovider, which can be either a web3 provider or a connection string. The default ishttp://localhost:8545, unless a globalweb3instance is found, in which caseweb3.currentProvideris used.- Add optional
unitargument tobalancefunctions. (#79)How to upgrade from 0.4
The package has been renamed to
@openzeppelin/test-helpers, so please uninstallopenzeppelin-test-helpersand reinstall it with the new name.npm remove openzeppelin-test-helpers npm install --save-dev @openzeppelin/test-helpersIf you are using
openzeppelin-test-helpersin a Truffle environment with automatic configuration, there is nothing you need to do. If you were manually configuring aweb3instance, you will need to configure theproviderinstead. The specifics will depend on your setup, but the following should get you started.-require('openzeppelin-test-helpers/configure')({ web3: myWeb3 }); +require('@openzeppelin/test-helpers/configure')({ provider: myWeb3.currentProvider });Additionally, Truffle migrations require explicit environment configuration, since automatic detection does not work.
require('@openzeppelin/test-helpers/configure')({ provider: web3.currentProvider, environment: 'truffle' });0.4.2 (2019-07-31)
- Upgraded web3-utils and truffle-contract dependencies to use the stable web3 release. (#65)
0.4.1 (2019-07-26)
- Added support for web3 ^1.2.0 (included by truffle v5.0.29). (#63)
0.4.0 (2019-05-23)
- Fixed
shouldFail.reverting.withMessageon non-Ganache chains. (#25)- Fixed
send.transactionnot working on contracts with a fallback function. (#26)- Made
shouldFail.reverting.withMessagefail if no error string was provided. (#28)- Renamed
makeInterfaceIdtomakeInterfaceId.ERC165, and addedmakeInterfaceId.ERC1820. (#21)- Added possibility to configure a custom web3 instance. (#38)
- Replaced
shouldFailwithexpectRevert, with an improved API. (#39)- Fixed detection of Ganache pre-releases (such as those used by Ganache GUI v2.0.1). (#46)
How to upgrade from 0.3
... (truncated)
Commits
-
c59a7d10.5.1 -
5bdd2e6Add changelog entry -
326c3970.5.1-rc.0 -
372b3cbRemove truffle env check -
8e215620.5.0 -
2f1bd410.5.0-rc.3 -
3fc894eAdd notes to readme and changelog re. truffle migrations -
2ad267fUpdate truffle migration config on integration test -
b5ceeffMake @truffle/contract a dependency -
1006e2cAdd singletons check to integration tests - 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.
Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.
You can always request more updates by clicking Bump now in your Dependabot dashboard.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill 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 labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language -
@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot dashboard:
- Update frequency (including time of day and day of week)
- Pull request limits (per update run and/or open at any time)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
We should instead switch to @openzeppelin/test-helpers.