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
Fix unbox to remove repo name restriction (#4145 by @cds-amal)
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:
Back at it with our weekly Truffle release. Celebrate the enhancements and bug fixes with a jiggly peanut panna cotta.
To start, let's put our hands 👏 🎊 together for the new e command in Debugger CLI. This command prints recently emitted events, including what emitted them and whether they've been reverted. By default, it prints three events, but it also allows printing more.
Next up, good news for Layer 2 builders; we've added Arbitrum Nova support in truffle debug --fetch-external. There's no stopping us from debugging those verified contracts on the growing L2 networks. 🚀 Bonus tip, in case you didn't know, you can also use the Truffle debugger with Arbitrum Nitro and Optimism!
And thank you so much @eltociear, for helping us catch and fix a typo! 🙇 Your contributions are much appreciated.
That's all for now. See you next week and always happy building!! 🍂
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
This version was pushed to npm by lsqproduction, a new releaser for truffle since your current version.
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/gongbell/ContractFuzzer/network/alerts).
Bumps minimatch to 3.0.4 and updates ancestor dependencies minimatch, truffle-compile and truffle. These dependencies need to be updated together.
Updates
minimatchfrom 0.3.0 to 3.0.4Commits
e46989av3.0.4ddfacbdupdate brace-expansion55ed736update package scripts and depseed8949v3.0.3ecabc57Do not throw on unfinished !( extglob patterns81edb7cv3.0.26944abfHandle extremely long and terrible patterns more gracefully8ac560ev3.0.14f3a8bcupdate tap9cf2d88Remove mentions of cache from readmeMaintainer changes
This version was pushed to npm by isaacs, a new releaser for minimatch since your current version.
Updates
truffle-compilefrom 1.1.2 to 4.2.3Release notes
Sourced from truffle-compile's releases.
Commits
22c8978Publish1c0d3d5Update yarn.lock6f78745Merge pull request #2341 from trufflesuite/update-packagesf96f2b4Rename truffle-require to@truffle/required867f6fRename truffle-workflow-compile to@truffle/workflow-compilea5b121eMerge pull request #2331 from trufflesuite/update-packagesd0b177dMerge pull request #2335 from trufflesuite/distReleaseScript433ae41Merge pull request #2320 from trufflesuite/console-updatef0c98bbMerge in develop branch4945973Merge pull request #2332 from trufflesuite/more-update-packagesUpdates
trufflefrom 2.1.2 to 5.6.4Release notes
Sourced from truffle's releases.
... (truncated)
Commits
495e923Publish0a16e15remove db from dev deps in trufflebbafe36bump some truffle packages47249b6add another test and prevent db integration test from running when running CI...63fd9cbonly start Ganache when not testing using Gethbce7533revert changes to server utility and manually manage ganache in testsab9f9fdtake first crack at rewriting db testab76f31wip - make first attempt at moving db integration test into truffle scenario ...d8f27f3truffle: instrument commandRunner6fa0a2cUpdate ganache to 7.5.0Maintainer changes
This version was pushed to npm by lsqproduction, a new releaser for truffle since your current version.
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/gongbell/ContractFuzzer/network/alerts).