Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update all patch updates (patch) #189

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update all patch updates (patch) #189

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2020 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
bignumber.js 9.0.1 -> 9.0.2 age adoption passing confidence dependencies patch
ganache-cli 6.12.0 -> 6.12.2 age adoption passing confidence devDependencies patch
truffle 5.1.48 -> 5.1.67 age adoption passing confidence devDependencies patch
trufflesuite/ganache-cli v6.12.0 -> v6.12.2 age adoption passing confidence docker patch

Release Notes

MikeMcl/bignumber.js

v9.0.2

Compare Source

  • 12/12/21
  • #​250 [BUGFIX] Allow use of user-defined alphabet for base 10.
  • #​295 Remove bignumber.min.js and amend README.md.
  • Update .travis.yml and LICENCE.md.
trufflesuite/ganache-cli

v6.12.2

Compare Source

v6.12.1

Compare Source

trufflesuite/truffle

v5.1.67: — Five Minute Caramelized Pecans

Compare Source

Happy Friday all! We're back this week with some bug fixes 🦠 and improvements 🔧.

First, when --stacktrace was 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Improvements
  • Upgrade to webpack 5: significantly speed up runtime and reduce bundle size (#​3794 by @​tcoulter)
Bug Fixes
Internal improvements

v5.1.66: — Chocolate Laboratory

Compare 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 --stacktrace wouldn'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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Bug Fixes
Internal improvements
Dependency updates

v5.1.65: — Gummy Snakes

Compare 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-json installed. Now these problems have been fixed. In addition, some of the recent improvements to Vyper compilation also previously required having vyper-json installed. Now, as long as you are using Vyper 0.2.5 or later, you will get the effects of these improvements without needing to install vyper-json.

In short, the effect of this week's update is that you shouldn't need to worry too much about whether it's vyper or vyper-json installed, 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Bug Fixes
  • Fix several Vyper compilation bugs (specific to non-JSON Vyper and prerelease Vyper) (#​3757 by @​haltman-at)
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 mainnet would 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 for truffle 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Fixes
Internal improvements
Dependency updates
  • Update highlightjs-solidity to 1.0.21 (update syntax highlighting for Solidity 0.8.1) (#​3747 by @​haltman-at)

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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Bug Fixes
Internal improvements

v5.1.62

Compare 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Bug Fixes
Internal improvements

v5.1.61: — Take two with chocolate

Compare 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Fixes
Internal improvements

v5.1.60: – Chocolate Babka

Compare 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 byte in Truffle's Assert.sol library (used when writing tests in Solidity), since Solidity v0.8.0 no longer accepts that (you have to do bytes1 now!) 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Fixes

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:

panic

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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
  • Allow debugger to debug Solidity test contracts (also, some other new options) (#​3637 by @​haltman-at)
  • Add support for decoding of panics and fallback return values (and also some other stacktracing improvements) (#​3627 by @​haltman-at)
  • Allow fetch-external to proceed with warning if compile fails (#​3634 by @​haltman-at)
  • Update globally-available variables for 0.8.0; also set _chainId in exposed Ganache instances (#​3623 by @​haltman-at)
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.6 and 0.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:

vyperdebug

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.js or package.json, Truffle will now add it to new contracts created with truffle 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:

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Internal improvements
Bug fixes
Dependency updates

v5.1.57: — Apple Pie Rugelach

Compare Source

Happy Thursday and happy Hanukkah! 🕎 Its time to unwrap another Truffle release! 🍬

This week, we have a smattering of sweet internal improvements. 🔧 The @truffle/source-fetcher package got some love, with an updated type to support the Solidity viaIR option. Further, a specializations field was added to the @truffle/source-fetcher output. @​haltman-at also did the important work of avoiding the combination of distinct compilations in debugger tests. Going forward, debugger tests will run directly off of compiler input.

We also made a couple of changes to the @truffle/db package, with more coming soon! 💻

Enjoy and have a lovely weekend! 👋 As always, please reach out on Gitter or Spectrum if you run into issues or need a hand!

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Internal improvements
Dependency Updates

v5.1.56: — Praline compiler pie

Compare Source

Hello people on the internet! 🖥️I will now unveil the most recent developments on the Truffle front!

This week, there are some tweaks to the compiler infrastructure that take center stage. The Vyper 🐍 compiler package definitely got some love as @​haltman-at went through to add some support for evmVersion and to also enable source maps. A couple of knobs got turned 🎛️ and a switch or two were flipped. Additionally, the way Vyper source maps were handled got an update. Most notably, they are now stored in the artifact (check out the changelog and the respective PRs for more of the nitty gritty).

Some extra support was also added to the Solidity compiler package. Namely, support for the newish viaIR and modelCheckerSettings options was added.

All of that and a a pinch of bug fixes makes this weeks release! ✨ We hope you all have a nice weekend and that you come visit us on Gitter or Spectrum if you run into issues or need a hand!

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Internal improvements
Bug fixes

v5.1.55: – Cranberry sauce (the kind from a can)

Compare Source

Hello all! 👋

Got some updates for you this week. Let's take a quick peek!

Enums in @​truffle/contract

You can now access Solidity-defined enums in @​truffle/contract. Let's say you have a contract like so:

contract PotatoMasher {
  enum PotatoVariety {
    YukonGold,
    RussetBurbank,
    Vitolette
  }
 
  // ...
}

You can now do:

const PotatoMasher = artifacts.require("PotatoMasher");

const variety = PotatoMasher.PotatoVariety.YukonGold;

Pretty useful, right? 😄

Disable confirmation listener

A number of users have reported that Truffle does a lot of polling to eth_getBlockByNumber. This is kind of annoying, especially you're connecting to a node that enforces rate limits! So we've added an option to disable operation.on("confirmation"), since that was the culprit. Just add this to your truffle-config.js:

module.exports = {
  // ... rest of truffle-config
  networks: {
    "<network-name>": {
      // ... rest of config for <network-name>
      disableConfirmationListener: true
    }
  }
}

Hope this helps!

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Internal improvements
Dependency update

v5.1.54: — Cookies and cream cupcake

Compare Source

Howdy everyone, back for another tasty treat? 🎂 "If it's not cake I'm not interested... unless it's a Truffle release!"

This week we have a decent-sized helping of goodness to improve Truffle ( 🆒). We've got a bunch of bug fixes in here, an improvement to debugger output, as well as updated syntax highlighting for Solidity 0.7.5.

And three cheers to @​agonzalezro 🎊🎊🎊 for throwing in a nifty feature for the create command! In the case that you want to create a contract, a test, AND a migration all at once, just throw it "all" for the type of resource you want to create! I bet that'll make you say "Well I'll be!".

So that means that

truffle create all CookiesAndCream

will create all three at once using the name "CookiesAndCream". Thanks for lending a hand @​agonzalezro!

Happy Thursday y'all and we'll see you back next time!

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Internal improvements
Dependency update
Bug fixes

v5.1.53: — Time for dessert 🍬

Compare Source

Post TruffleCon release time! 🎉

Welcome back everyone, we've just finished TruffleCon and had a great time! We hope if you joined us that you did too! 💃

We just wanted to pop in here again to bring you a really quick release in time for the weekend. We have to give a huge thanks to @​bguiz for adding support for configuring the deployment polling interval in Truffle! Hopefully that will come in handy when tweaking parameters during deployments.

Anyways, we hope you enjoy and have a nice weekend. Cheers!

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Internal improvements
  • Redo @truffle/db's project abstraction to work more naturally in batches (#​3513 by @​gnidan)
  • Power-wash @truffle/db's external interface and front-facing modules (#​3511 by @​gnidan)
  • Define project-based abstraction for loading Truffle stuff to @truffle/db (#​3483 by @​gnidan)

v5.1.52: – Waffle bites

Compare Source

Howdy! 👋 Excited for TruffleCon 2020? 🎉 We sure are!

Anyway, let's see what's in store with this week's Truffle release. Looks like a bunch of enhancements and some bug fixes...

First off: thanks to @​bguiz, you can now specify a polling interval for @​truffle/hdwallet-provider! This will come in handy when talking to a node that does rate limiting! ⏱️

This release also brings two other enhancements worth highlighting: importing ABI JSON files and debugging internal Solidity sources.

Importing ABI JSON files

Have you ever written a smart contract to interact with another, already-deployed contract? Did you have to go to GitHub and download that project's whole set of source files and include them in your project? Or write a Solidity interface by hand?

Well, the days of that are over! Stop rewriting UniswapV2Router01's interface by hand and instead just save a .abi.json file to your contracts/ directory. Truffle now allows you to do this in Solidity:

import "./Uniswap.abi.json";

Truffle will go ahead and turn that raw ABI description into a valid Solidity source file, so you don't have to worry about it! Handy, right?

Debugging Solidity internals

You know you're curious what happens when you assign a memory array to storage. Good thing Solidity outputs this information now (in v0.7.2 and above).

Hopefully you won't have to get to the low-level Solidity internals when you're trying to figure out what's going wrong, but if you do (or if you're just curious, like me): Truffle's debugger has you covered! We've just added the debugger g command to turn on a mode to step through these internal sources (G turns it off). This level of inspection has been available for a few Truffle versions now, via stepping instruction by instruction (;), but we're pleased to make it easier for you to get this look under the hood! 👩‍🔧

Check it out:

truffle debug stepping through Solidity internals

Stepping into Solidity internals with Truffle debugger

That about covers the highlights, but check the changelog below because there's a bit we didn't cover. 🔍

Until next time!

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Enhancements
Bug fixes
Internal improvements

v5.1.51: — Trick or Treat

Compare Source

Hello all, we're back with another weekly (and seasonal 🎃) Truffle release!

This week's release fixes a problem that would prevent WebSockets providers 🕷 from working properly. It also fixes a problem that would cause Husky 🐺 to get installed as a dependency of Truffle. How eerie! 👽 Thanks to @​interfect for noticing the problem.

I'm afraid that's all for this week, but we'll be haunting 👻 this space next week as well, and you may want to prepare yourself for that one... it'll be a scream! 😱

How to upgrade

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

npm uninstall -g truffle
npm install -g truffle

Changelog

Bug fix
  • Allow for false value in provider callback ([#​3472](htt

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from 66f52e0 to cf52f64 Compare October 22, 2020 16:58
@renovate renovate bot changed the title Update dependency truffle to v5.1.49 Update dependency truffle to v5.1.50 Oct 22, 2020
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from cf52f64 to 1c221a7 Compare October 26, 2020 17:19
@renovate renovate bot changed the title Update dependency truffle to v5.1.50 Update all patch updates (patch) Oct 26, 2020
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from 1c221a7 to dfee2b1 Compare October 29, 2020 23:09
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch 2 times, most recently from e212bdd to 76adc47 Compare November 12, 2020 22:34
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from 76adc47 to 6088fed Compare November 19, 2020 22:49
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch 2 times, most recently from f19e7c3 to 0b4c325 Compare December 3, 2020 21:30
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch 2 times, most recently from 06eaffa to 7ecdabb Compare December 17, 2020 21:29
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch 2 times, most recently from 213ad33 to fa2c787 Compare January 2, 2021 06:12
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch 3 times, most recently from c01aa23 to 3253e91 Compare January 15, 2021 00:14
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from 3253e91 to eceac95 Compare January 22, 2021 22:18
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch 2 times, most recently from 41f9b86 to 9a0ca47 Compare February 5, 2021 00:50
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from 9a0ca47 to 4dbf86c Compare March 4, 2021 04:43
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from 4dbf86c to f1b559d Compare May 9, 2021 23:06
@renovate renovate bot force-pushed the renovate/patch-all-patch-updates branch from f1b559d to c97e7d6 Compare March 7, 2022 13:05
@renovate
Copy link
Contributor Author

renovate bot commented Mar 23, 2023 •
edited
Loading

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@renovate-bot