Update all patch updates (patch) #564
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
2 times, most recently
from
330f7dc
to
d47b88c
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
5 times, most recently
from
7045403
to
f84a603
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
3 times, most recently
from
2779eaf
to
06c309d
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
2 times, most recently
from
ee3d840
to
fbeef0b
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
4 times, most recently
from
940f2b6
to
4e6cc96
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
3 times, most recently
from
ca267f7
to
953824a
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
2 times, most recently
from
cb336e1
to
91833fd
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
2 times, most recently
from
e9123cc
to
11dd6b7
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
3 times, most recently
from
2bdc32c
to
46b7dc5
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
3 times, most recently
from
4d5ea53
to
9a1dfa0
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
9a1dfa0
to
f1bc345
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
3 times, most recently
from
2de3822
to
9a1677e
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
9a1677e
to
aa4f213
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
2 times, most recently
from
e649241
to
06860bb
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
06860bb
to
d9b5638
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
d9b5638
to
7a95a73
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
7a95a73
to
3ef54b5
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
3ef54b5
to
52dde11
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
52dde11
to
0ea3636
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
0ea3636
to
d04c05c
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
d04c05c
to
fdee1cd
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
fdee1cd
to
74749f3
Compare
renovate
bot
force-pushed
the
renovate/patch-all-patch-updates
branch
from
74749f3
to
8b8eef0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
0.1.10->0.1.120.5.6->0.5.169.0.1->9.0.23.1.0->3.1.114.2.0->14.2.10.2.17->0.2.277.0.6->7.0.106.12.0->6.12.25.3.0->5.3.20.7.11->0.7.225.1.48->5.1.67v6.12.0->v6.12.21.3.0->1.3.6Release Notes
OpenZeppelin/openzeppelin-test-helpers (@openzeppelin/test-helpers)
v0.5.16Compare Source
v0.5.15Compare Source
snapshot.restorewhen used multiple times.v0.5.14Compare Source
snapshotmodule.v0.5.13Compare Source
send.etherso it no longer forcesgasPrice: 0.NOTE: This may break some tests but gas price 0 is no longer valid since the London hard fork.
tracker.deltaWithFees.v0.5.12Compare Source
snapshotmodule to capture and revert blockchain state.v0.5.11Compare Source
expectRevertfor latest versions of Hardhat.v0.5.10Compare Source
@truffle/contractdependency.v0.5.9Compare Source
@openzeppelin/contract-loaderdependency.v0.5.8Compare Source
expectRevertfor Hardhat. (#131)v0.5.7Compare Source
expectEventreturn the event that was found. (#129)expectEvent.inTransactionwhen there are conflicting events. (#133)Breaking change
The fix to
expectEvent.inTransactionmay break some tests that were not using the API as intended, or which were causing a false positive assertion. If theemitterargument 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.MikeMcl/bignumber.js (bignumber.js)
v9.0.2Compare Source
nickmerwin/node-coveralls (coveralls)
v3.1.1: Maintenance / Security updatesCompare Source
execforexecFile. Credit: Adar Zandberg from the CxSCA AppSec team at Checkmarx.devDependenciesairbnb/javascript (eslint-config-airbnb-base)
v14.2.1Compare Source
cgewecke/eth-gas-reporter (eth-gas-reporter)
v0.2.27Compare Source
v0.2.26Compare Source
v0.2.25Compare Source
v0.2.24Compare Source
v0.2.23Compare Source
v0.2.22Compare Source
v0.2.21Compare Source
v0.2.20Compare Source
v0.2.19Compare Source
v0.2.18Compare Source
ethereumjs/ethereumjs-monorepo (ethereumjs-util)
v7.0.10: ethereumjs-util v7.0.10Compare Source
Address.isPrecompileOrSystemAddress()method which returnstrueif address is in the address range defined by EIP-1352, PR #1170false(instead of throwing) for non-hex-string values in account moduleisValidAddress,isValidChecksumAddress,isZeroAddressmethods (it now gets enough to just handle thefalsecase on function usage), PR #1173v7.0.9Compare Source
v7.0.8Compare Source
v7.0.7Compare Source
trufflesuite/ganache-cli (ganache-cli)
v6.12.2Compare Source
v6.12.1Compare Source
mholt/PapaParse (papaparse)
v5.3.2Compare Source
v5.3.1Compare Source
sc-forks/solidity-coverage (solidity-coverage)
v0.7.22Compare Source
v0.7.21Compare Source
===================
v0.7.20Compare Source
===================
v0.7.19Compare Source
===================
v0.7.18Compare Source
=================
v0.7.17Compare Source
v0.7.16Compare Source
===================
v0.7.15Compare Source
===================
v0.7.14Compare Source
===================
v0.7.13Compare Source
===================
v0.7.12Compare Source
===================
https://github.com/sc-forks/solidity-coverage/issues/570/570)
trufflesuite/truffle (truffle)
v5.1.67: — Five Minute Caramelized PecansCompare Source
Happy Friday all! We're back this week with some bug fixes 🦠 and improvements 🔧.
First, when
--stacktracewas used with Truffle test,contract.method()wouldn't return a receipt in the proper format. 🧾 This is fixed now!Second, Truffle v5.1.66 broke compilation because of an erroneously removed dependency. We re-introduced the missing dependency and your compilations should go swimmingly 🏊 now!
Finally, we made a significant improvement to Truffle's build speed! 🏎️ We upgraded to webpack 5, which along with configuration changes, shaved off 62% of the overhead required to run the bundled truffle command. As a bonus,, the total size of the build directory is reduced significantly. 🎉
That's all for this week. See you next week for a new version of Truffle! 🍫
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Improvements
Bug Fixes
--stacktrace(#3816 by @haltman-at)Internal improvements
txlogfrom being confused by unmapped code in function startup (#3814 by @haltman-at)v5.1.66: — Chocolate LaboratoryCompare Source
Hello all, we're back this week with some bug fixes for Truffle Test! 🦠
First off, the exit code wasn't being set properly when there were failed tests. Now Truffle Test will properly exit with a status equal to the number of failed tests. 🧪
Secondly, events weren't decoding properly for upgradeable contracts (or when other manual delegatecalls were involved); now events should decode properly in this case. 🔬
Finally,
truffle test --stacktracewouldn't work properly when run with Ethereum clients other than Ganache; now this incompatibility has been fixed. 📡That's all for this week, but we'll be back once again with a new version of Truffle for next week! ⚗
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Bug Fixes
Internal improvements
Dependency updates
typescriptto 3.9.8 and 4.1.4 (#3789 by @haltman-at)v5.1.65: — Gummy SnakesCompare Source
Hello all! 👋
This week brings some fixes and enhancements to Vyper compilation. 🐍 There were some problems with Vyper compilation if you were using Vyper 0.2.x but didn't have
vyper-jsoninstalled. Now these problems have been fixed. In addition, some of the recent improvements to Vyper compilation also previously required havingvyper-jsoninstalled. Now, as long as you are using Vyper 0.2.5 or later, you will get the effects of these improvements without needing to installvyper-json.In short, the effect of this week's update is that you shouldn't need to worry too much about whether it's
vyperorvyper-jsoninstalled, as Truffle will automatically handle things in the best way available to it! 🦾We'll be back next week with further improvements, so stay tuned! 📻
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Enhancements
vyper --standard-jsonif vyper-json not available (#3759 by @haltman-at)Bug Fixes
Internal improvements
v5.1.64: – 🌨️ It's a cold day for eating ice cream 🍦Compare Source
Hi folks! 👋
This week we've been getting prepped for a couple upcoming features that have been in the works for awhile, so we've been hard at work improving some internal systems and whatnot. What's that mean for you? Well, a few neat enhancements! ⚙️
Vyper compiler support got a whole lot of love! When developing Vyper contracts, Truffle will now detect which source files have changed and compile only which ones are necessary. This means not only reduced build times, but also...
Better support for importing ABI JSON files! Vyper supports importing ABI JSON files directly in the compiler, and now Truffle lets you take advantage of that. In addition, we've made improvements to Truffle's experimental support for doing this in Solidity. Writing contracts that interoperate with other projects should now be a much smoother experience.
You can now use Truffle for read-only use cases without configuring a mnemonic. It's been a bit annoying that (e.g.)
truffle debug --network mainnetwould require you to hook up @truffle/hdwallet-provider, just because Truffle's configuration required a way to sign transactions. Why would you want to sign a transaction when debugging? You wouldn't, and now you don't have to! (Of course, you'll still need that configuration fortruffle migrate;)We hope you enjoy this release and look forward to what's to come. We're thrilled to continue cleaning house in the codebase and making even more capabilities and performance improvements possible.
Until next time!
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Enhancements
truffle debugwithout a mnemonic (#3659 by @gnidan)Fixes
Internal improvements
allDocsmethod for workspace.all() in @truffle/db (#3732 by @gnidan)Dependency updates
v5.1.63: — Banana Cream Pie 🍌Compare Source
Hello there fellow Trufflers! 👋
We have a few internal improvements for you in this week's release. Our very own @eggplantzzz has removed callbacks from the main run method for top-level command files. If you use these you'll notice they now return Promises! We also shored up some query issues in @truffle/db to ensure larger queries can be effectively handled. 🔧 💪
A special shout-out to @araskachoi for finding and fixing a typo bug and submitting a fix. External contributions are so important and we really appreciate it! 🙏
Enjoy this week's release, and please reach out with any questions or issues!
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Bug Fixes
Internal improvements
v5.1.62Compare Source
Hello once again! 👋
We've got a small morsel 🍬 of a bugfix release this week. Our new system for allowing importing ABI JSON files as interfaces in Solidity wasn't working quite right; this should fix it up. 🔧 We'll have a lot more to say about that soon. In the meantime, enjoy this!
That's all for this week, 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
Bug Fixes
Internal improvements
v5.1.61: — Take two with chocolateCompare Source
A bug fix for you, and a bug fix for you and you and YOU! 😮
Yes ladies and gentlemen, we've decided to deliver you with a giant, heaping shovel-load of everyone's favorite New Years gift or present on a blind date: bug fixes! Yay! Now don't worry, I know what you're thinking and there are absolutely no strings attached here. And believe me when I say that I can attest first-hand that they are of the choicest quality and bestest of flavors 🥮! Please enjoy, and don't forget to share with your friends... or pets.
So you've already heard the good news and I'm sure you are just chomping at the bit 🐴 to sink your teeth in, but let me just also say that the Truffle team didn't do this alone. We have to say a big "THANK YOU" to @EdwardJSantos who has been watching our back and cleaning up our mistakes in documentation (💪). It feels good to know that people are keeping a look out, so thanks!
For best results, enjoy this release with chocolate 🍫 and as always check the changelog if you want to dig into the nitty gritty.
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Fixes
compile-vyper'snecessarycallsourcesWithDependencies, removecompilationTargetslogic (#3665 by @haltman-at)0.1.0-beta.17(#3653 by @haltman-at)README.md(#3662 by @EdwardJSantos)RangeUtilsmethod (#3664 by @eggplantzzz)Assertlibraries for Solidity 0.8.0 (#3669 by @haltman-at)Internal improvements
v5.1.60: – Chocolate BabkaCompare Source
Happy new year, everyone! 🎆 🍾
The Truffle team's off this week, so we almost didn't have anything new to publish, but @minaminao came to the rescue with a PR to unalias
bytein Truffle'sAssert.sollibrary (used when writing tests in Solidity), since Solidity v0.8.0 no longer accepts that (you have to dobytes1now!) So we have a release — thanks @minaminao!I'll keep this short. Here's to 2021!
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Fixes
bytetobytes1(#3648 by @minaminao)v5.1.59: – Pangalactic Gargleblaster (Don't panic!)Compare Source
Happy Boxing Day, everyone! 🥊 (Wait that's not right, is it? Can anyone please tell this American what "Boxing Day" is? 🎁 )
Let's see what we have for you this week... not bad for a holiday week! Looks like the biggest change is the new enhancement to support Solidity v0.8.0's panics! (See their release blog post). This means that failed assertions and other runtime errors now provide more context. Check it out:
Apart from that, we have a couple fixes related to Vyper compilation and similar. Thanks to @PetarKirov, we've also upgraded the ethereumjs-wallet dependency in @truffle/hdwallet-provider!
Hope you enjoy!
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Enhancements
Fixes
Internal improvements
Dependency updates
v5.1.58: — Schwarzwälder Kirschtorte (~Black Forest cake)Compare Source
Hello friends, rabbits, robots, and leprechauns 🍀, strap yourself in to hear about the newest Truffle! 🌈
This week's release has quite the helping of PRs. 🍜 There are too many to mention individually but we can check out a couple of highlights!
First off, we've been trying to keep up with the Solidity folks who have this week gifted us an early Christmas present of versions
0.7.6and0.8.0. @haltman-at has been busy updating Truffle to be compatible just in time for the holidays!Another really exciting thing found in this release is rudimentary support for using the debugger with Vyper. It is still in its experimental phase but you can now step through your Vyper code. Check it out:
Neat! We hope you Vyper folks (err, Vyperistas?) enjoy that one!
There are a bunch more and you can check out the changelog 📒 if you want to get into the dirty details. We have to give a shoutout to @agonzalezro who spent some time adding some functionality to Truffle's create command. If you have a license field in your
truffle-config.jsorpackage.json, Truffle will now add it to new contracts created withtruffle create. Thanks for the good work!We hope the year is finishing up well for you all and we look forward to seeing you next time!
How to upgrade
We recommend upgrading to the latest version of Truffle by running:
Changelog
Enhancements
Configuration
📅 Schedule: Branch creation - "on sunday" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.