smartcontractkit / truffle-starter-kit

An example smart contract utilizing Chainlink
MIT License
264 stars 102 forks source link

Bump truffle from 5.1.65 to 5.3.1 #80

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps truffle from 5.1.65 to 5.3.1.

Release notes

Sourced from truffle's releases.

v5.3.1 – Sütlaç (Turkish rice pudding)🍮

Does it feel like spring time? A new truffle release has bloomed! :tulip: This week we have a showering of small improvements and bug fixes to Truffle DB. Remember, if you want to try out Truffle DB you have to enable it in your truffle-config.js as:

db: {
  enabled: true
}

More information about Truffle DB can be found here.

You'll also notice we updated our web3 dependency to v1.3.5.

Happy coding! :heart:

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements

  • Add initial truffle db query <query> command (#3966 by @gnidan)

Bug fixes

  • Fix problem when adding non-null resources alongside null resources in @truffle/db (#3967 by @gnidan)
  • Stop populating network for undeployed artifacts in @truffle/db (#3970 by @gnidan)

Internal improvements

Dependency updates

v5.3.0 – Preserves 🍓

Another feature release, so soon! Hi everyone! 👋. We're excited to bring you Truffle v5.3.0 today, officially adding the new truffle preserve command.🥫

Have you ever needed to come up with a creative solution to manage your dapp assets? Well, good news: Truffle now introduces a mechanism to manage these assets for you, allowing you to focus on building your application instead of configuring new tools.

This means: you can now use Truffle to upload your static assets to IPFS, Filecoin, and/or Textile Buckets. To get started, please see the new Filecoin box and corresponding announcement blogpost to learn more, or just run truffle unbox filecoin after upgrading Truffle 😄. For detailed information, refer to the corresponding truffle preserve documentation.

Beyond just the functionality above, this new command expands Truffle's plugin system entirely: the services listed above are themselves just Truffle plugins that we're including by default. (Heck, even the "arbitrary files and directories" functionality is provided by a plugin!) We'll be documenting how to create a truffle preserve plugin in the coming weeks, so stay tuned there. We're excited that this release brings support for this foundational use case, and we can't wait to see this same system get used for others (verify contracts on Etherscan, anyone? 😉).

... (truncated)

Commits
  • c67bc3c Publish
  • da5f1ec Merge pull request #3966 from trufflesuite/db/query
  • 41cf885 Merge pull request #3970 from trufflesuite/db/fix-extraneous-networks
  • f98320d Stop populating network for undeployed artifacts
  • f9d5f51 Merge pull request #3967 from trufflesuite/db/fix-null-add
  • d7c4675 Fix support for nully adds
  • 7e8d74b Add initial truffle db query \<query> command
  • 6d656b5 Merge pull request #3955 from trufflesuite/db-kit-custom-config
  • 9eeee57 Merge pull request #3965 from trufflesuite/upgrade-web3-finally
  • 43d3393 Update test for new abi-coder location
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by cds-amal, a new releaser for truffle since your current version.


Dependabot compatibility score

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 - `@dependabot badge me` will 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](https://app.dependabot.com): - 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)