Update dependency truffle to v5.1.47 #555
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.1.46
->5.1.47
Release Notes
trufflesuite/truffle
v5.1.47
Compare Source
Hello all! 👋
This week features two enhancements to Truffle's capabilities. Firstly, there is now a
--compile-none
option totruffle test
, which will force Truffle to skip the compilation step at the start. Use this with caution ⚠, as skipping the compile can of course lead to tests running outdated code! Secondly, thanks to @coeniebeyers, it's now possible to set the maximum buffer when using a Dockerized ⚓ version of solc, by setting the optioncompilers.solc.spawn.maxBuffer
.Now, you may have noticed that Solidity 0.7.2 released recently. Well, we've fixed a bug 🐛 that prevented Truffle from properly downloading Solidity 0.7.2. But there's something more.
If you take a transaction passing through a contract compiled with Solidity 0.7.2 or later, and open it up for inspection 🕵 with Truffle Debugger, you'll find that you can now step into the Yul (assembly) code for Solidity's internal routines while debugging! The debugger won't step into these by default; you'll have to advance step-by-step 👣 with
;
to enter such internal routines. Once inside them, however, you can step forward withn
,i
,o
, andu
as usual, or set breakpoints there withb
, or pressl
to show additional source context, or do all the usual debugger things. So, hopefully you find this extra insight 💡 into your contracts' workings helpful!Technically, this capability already existed in Truffle prior to this release (added earlier in anticipation of Solidity 0.7.2 💪), but due to a bug it previously didn't always work properly. But now you should be able to inspect internal Solidity routines without problem!
That's all for now, but as always, we'll be back next week with more! 🏎
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Enhancements
compileNone
option for Truffle Test (#3335 by @eggplantzzz)maxBuffer
for Docker loading strategy via configuration value (#3381 by @coeniebeyers)Bug fixes
generatedSources
anddeployedGeneratedSources
to shims (#3407 by @haltman-at)Internal Improvements
externalSolidity
flag (#3401 by @haltman-at)Dependency Updates
eslint
to v7.9.0 (#3399 by @haltman-at)Renovate configuration
📅 Schedule: "on sunday" in timezone America/Los_Angeles.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.