:warning: The Truffle Suite is being sunset. For information on ongoing support, migration options and FAQs, visit the Consensys blog. Thank you for all the support over the years.
Welcome back! 👋 Another Truffle release is out in the wild today. Once again it is mostly a maintenance-type release with some bug fixes and internal improvements. We have to give a shout-out 🔈 to @sandakersmann for updating the copyright information in Truffle's LICENSE file. Thanks so much for helping keep everything tidy and up-to-date! We'll see you next time and we wish you all a beautiful weekend!🦚
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
1.2.2 (#5909 by @haltman-at)console.log when presenting BigInts (#5933 by @cds-amal)txLog when an initial state exists (#5919 by @eggplantzzz)5.8.2 to 5.19.1 (#5908 by @dependabot[bot])Hello hello! 👋 It's time for another Truffle release!
This week, we have a little bit of everything for you! Truffle should now properly return an error when it is due to an out of gas exception! 🎉 Previously, these were coming back as custom errors without further information. Additionally, you can now see a link to the Truffle Debugger documentation in the CLI when using it! 👀 Always nice to have more information at your fingertips! ⌨️
Special thanks to @sukanyaparashar for upgrading the solc dependencies to v0.8.18 in contract-schema and compile-solidity packages! 🙏
See below for more detail on the contents of this week's release. Thanks for reading, and we'll see you next week! ✨
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
Develop.connectOrStart()'s signature (#5891 by @cds-amal)contract-schema and compile-solidity packages (#5886 by @sukanyaparashar)Hi folks! Nice seeing you today 🤩
This week's Truffle release brings you fixes to some bugs that got surfaced internally. Hopefully these bugs didn't affect you, or maybe you were too busy dipping pieces of fruit into melted chocolate to open an issue 😮 🍍 🍓. In any case, we recommend reading on and upgrading!
Most notably: you can now switch accounts between transactions in Truffle Dashboard. This wasn't working correctly, which meant problems if (e.g.) your deployment process requires multiple accounts to sign different transactions... not great 🙀! Fortunately, this is now fixed and you can feel free to use Truffle Dashboard for all your CLI-driven signature needs, no matter how many counter-parties you want to involve in your smart contracts. 📄 🖊️
Besides that, Truffle's interactive console (i.e., in truffle develop and truffle console) now properly interprets quoted strings... e.g., now "two words" gets treated as only one string, the way you'd expect! We've also fixed the behavior of our help system inside the interactive console, so now help inside Truffle's console behaves the same as truffle help on the command line. ℹ️
Special shout-out to @sukanyaparashar for updating our truffle init output to the latest Solidity! Thanks for getting that for us 🙏.
Scroll down for all the details if you'd like... regardless, take care and thanks for reading! 👋
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
truffle develop and truffle console (#5871 by @eggplantzzz)--no-compile (#5872 by @kevinbluer)Hey everyone! 🫠 This week we're back with another release that mostly takes care of some good old fashioned housekeeping. 🧹
So Solidity 0.8.18 was recently released and there are a couple of updates here to keep up with them. The one of the two worth mentioning is the new block.prevrandao alias (for block.difficulty). This has been added as a globally available variable in the debugger. Additionally, we bumped highlightjs-solidity (which will yield better syntax highlighting) and web3 (woohoo!🎉). We hope you enjoy and we'll see you next time! 👋
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
block.prevrandao as globally available variable in debugger (#5866 by @haltman-at)appendCBOR field in metadata settings type in source fetcher (#5864 by @haltman-at)1.8.2 (#5862 by @haltman-at)2.0.6 (#5865 by @haltman-at)Hi all, we've got a small release this week but it's got some useful bug 🐛 fixes!
Specifically, there was a problem where, when using abbreviated names of Truffle commands -- for instance, truffle migr instead of truffle migrate -- some command-line options might not get set properly. But this has been fixed now so you may be as terse as you please! 🏎
And -- aside from some internal improvements and dependency updates -- that's it! But we'll be back next week with more, and interesting things are brewing for later... 🫖
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
Hello all! 👋
We hope you're having a great start to 2023 and hanging in there with your New Year's resolutions. 🧘
This week's release offers up a number of quality of life improvements and all round healthy goodness. Firstly, Truffle now ships with Ganache v7.7.3 which adds support for the Merge! ♻️ In addition, Truffle now more robustly handles help requests so truffle help <cmd>, truffle <cmd> --help, and truffle --help <cmd> should all have consistent output when searching for help for a given command. 📖 We've also updated the list of supported networks by Sourcify.
Lastly, Truffle will also now politely ask if you'll be willing to share telemetry when using Truffle Dashboard. 🙏 Note that this will never include any personal data and you can view our analytics policy for more detail.
That's all for this week, but as always, we'll be back next week with more!
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
v7.7.3 (#5824 by @MicaiahReid)Hello all, welcome to 2023!!! 🥂 🥳 🍾 We are back at it again with our weekly releases. 🛼
A big shoutout to @dPreininger for ringing in the ✨ new year 🎉 with a bug fix for Truffle! There was an issue they fixed with Truffle's development console to prevent crashes when interacting with Vyper smart contracts 🐍. Thank you for getting this! Many contributed their time and talent last year, and we are very much looking forward to collaborating more this year with our community. Please feel free to reach out if you find any issues in our backlog exciting. 🙇
🏗️ Please take a moment to complete The Solidity Development Survey 2022. The last day to fill out the survey is January 7th. Thank you! 🙏🏽
See you soon!
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
truffle console crash when metadata is missing in JSON artifact (#5819 by @dPreininger)Hello all! 👋
We want to bring a delicious chocolate 🍫 pavlova with spiced pears 🍐 to celebrate 🎉 this holiday season. Sit down 🪑, relax 🤗, and enjoy 🥳!!!
While Truffle dropped support for Node 12 a while back, we hadn't been enforcing this in our Node version check at startup. We now check this; Truffle will now refuse to run on Node 12 to prevent any problems.
One more thing! Please take a moment to complete The Solidity Development Survey 2022. This helps our community 🧑🏽🤝🧑🏽 to improve. Thanks! 🙏🏽
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
Hey ho, we have a release! Let's go, enjoy it with some treats! 🍫
It's Thursday yet again and we have a Truffle release coming your way! ↔️ This one is pretty exciting because we are finally releasing a console.log for Solidity in Truffle's testing and console environment. Simply use the following import at the top of your contract:
import "truffle/console.sol";
Then you can call console.log() similar to how you would in JavaScript.
console.log("this is logging and here is an address - %o", msg.sender);
Now when you run this code during a Truffle test run or in Truffle's console environment, you will receive logging! Super cool! 🪵
Another change we have this week is an update to the ENS infrastructure. When deploying an ENS dev registry, Truffle will also deploy a reverse registrar to allow for reverse resolution. So happy resolving!
@truffle/provider received a spruce up as well! Remember EIP 1193? This is the one that specifies a request method on providers (in addition to some other things). Now @truffle/provider is 1193 compliant!
Lastly we have a couple improvements that are a bit more internal to Truffle. A bit of code was cleaned up and fixed 🛠️, and an improvement which makes the encoding of contract creations easier was added.
ℹ️ Oh and before we go, we'd like to once again remind you that the Solidity team is conducting a survey to find ways of bettering the language and the compiler. So go complete it here to help improve the ecosystem!
And that should be it for this week! Happy middle of December to everyone and we'll see you again next time!
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle
encodeCreation() method to Encoder (#5777 by @haltman-at)require cache invalidation (#5780 by @eggplantzzz)Hello all! 👋
It seems like everyone is overjoyed 🥳 seeing their favourite players scoring goals. Are you feeling the FOOTBALL WORLD CUP ⚽ fever too? Then enjoy munching on a bucket full of caramel popcorn 🍿 with a new Truffle Release 🎉 to take your excitement to another level!
This week's release includes a 🐛 fix for the type issues with hdwallet-provider in your Typescript projects. Yay! 🎉 We also added support for Boba Goerli network 🕸️ to truffle debug --fetch-external. "More networks = More verification = More fun = More Safety"
One more thing! Please take a moment to complete The Solidity Development Survey 2022. This helps our community 🧑🏽🤝🧑🏽 to improve. Thanks! 🙏🏽
Sit back and cheer for your favourite teams! See you next week with a new Truffle Release! 🥳
We recommend upgrading to the latest version of Truffle by running:
npm uninstall -g truffle
npm install -g truffle