Bump hardhat from 2.14.0 to 2.19.0

[dependabot[bot]]

Bumps hardhat from 2.14.0 to 2.19.0.

Release notes

Sourced from hardhat's releases.

Hardhat v2.19.0

This new version of Hardhat introduces a new feature: Configuration Variables!

Configuration variables let you use values in a configuration file without making them part of your project. They work as a replacement for environment variables and dotenv, but are more flexible and powerful. Read our guide to learn more.

This version also adds support for solc v0.8.22.

Hardhat v2.18.3

This release adds ignition deploy to our telemetry-reported tasks.

Hardhat v2.18.2

This releases fixes a problem with Hardhat's compiler download caused by a fix in the latest version of undici.

Hardhat v2.18.1

This new version of Hardhat includes a new option when initializing a project: you can now start a project that uses Viem instead of ethers. To learn more about this, check our announcement.

This version also makes a small change to the logs shown during compilation: now the targeted EVM version (or versions) is shown.

Hardhat v2.18.0

This version of Hardhat adds support for scoped tasks.

You can now create scopes to group multiple tasks that are related in some way:

const myScope = scope("my-scope", "Scope description");
myScope.task("my-task", "Do something")
.setAction(async () => { ... });
myScope.task("my-other-task", "Do something else")
.setAction(async () => { ... });

Thanks to @​zemse, who kickstarted the work on this!

Hardhat v2.17.4

This version of Hardhat adds support for the debug_traceCall method.

Besides that, Hardhat projects are now initialized with npx hardhat init instead of npx hardhat. The latter command still works but it will produce a warning. See NomicFoundation/hardhat#2594 for the rationale behind this change.

Hardhat v2.17.3

This version of Hardhat changes the default evmVersion to paris for solc versions newer than or equal to 0.8.20.

Starting from version 0.8.20, solc changed the default target EVM version to Shanghai. Among other things, this meant that the generated bytecode could (and most likely would) contain the new PUSH0 opcode.

Up until this point, Hardhat always delegated to solc the decision of which EVM version to target. But there are two things that are different today: many users develop for non-mainnet chains, and not every chain has adopted the Shanghai hardfork yet. This means it's possible that you develop a contract which works locally (Hardhat's default hardfork is still Shanghai, because we follow the current mainnet hardfork) but that then doesn't work after deploying it.

If you are sure you are going to deploy in a network that supports the Shanghai hardfork, you can change the target EVM like this:

</tr></table> 

... (truncated)

Commits

• d8c4f5a Version Packages
• 5dccf36 Merge pull request #4538 from NomicFoundation/feature/4501-add-support-for-so...
• c8609f8 Merge pull request #4446 from NomicFoundation/feature/2265-add-a-better-mecha...
• 4628bc6 Merge pull request #4552 from NomicFoundation/fix-vyper-downloader
• 2f73386 Create tough-geese-tie.md
• 2257ae6 add error code in switch
• ebc0f61 Fix vyper downloader
• 8b0aa99 PR feedback fixes
• 145de04 add curly brackets in if condition
• 7e741a0 implement PR feedback
• Additional commits viewable in compare view

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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@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)

[openzeppelin-code[bot]]

Bump hardhat from 2.14.0 to 2.19.0

Generated at commit: b270873b5438a68403208ae4377edeac5a0de4a4

🚨 Vulnerabilities Summary

Process	Issues	Results
Contract Inspector	note low critical Total	35 12 1 48
Dependency Checker	Total	0

---

For more details view the full report in OpenZeppelin Code

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.