Bump truffle-plugin-verify from 0.5.20 to 0.6.7 in /examples/truffle

[dependabot]

Bumps truffle-plugin-verify from 0.5.20 to 0.6.7.

Release notes

Sourced from truffle-plugin-verify's releases.

v0.6.7

• ✨ Add support for opBNB (mainnet and testnet) - authored by @​zhangtianhao in #209

v0.6.6

• 🐛 Fix Celo Alfajores Support - authored by @​whyvrafvr in #208

v0.6.5

• 🐛 Fix Base support - authored by @​d10r in #204

v0.6.4

• ✨ Add support for Base and zkEVM (mainnets and testnets) - authored by @​d10r in #202

v0.6.3

• 🐛 Improve error handling / messages when Sourcify verification fails (authored by @​kuzdogan in #199)

v0.6.2

• 🐛 Fix bug where imports like "truffle/console.sol" couldn't be resolved (authored by @​gnidan in #196) - solves #195

v0.6.1

• 🐛 Fix bug where verification didn't work on Node <16

v0.6.0

• 🎉 Add support for Sourcify verififcation
• 💥 BREAKING: truffle-plugin-verify now automatically verifies on both Etherscan and Sourcify; if you only want to verify on one of the two platforms you can use the --verifiers=etherscan or --verifiers=sourcify CLI arguments
• 🛠️ Internal refactoring to support multiple verifiers

v0.5.33

• ✨ Add support for Cronos testnet, CLV, Arbitrum Nova and Celo
• 💥 Remove support for deprecated testnets Ropsten, Rinkeby, Kovan, OP Kovan, Arbi Rinkeby
• 🛠️ Move package to TypeScript and internal refactoring

v0.5.32

• ✨ Add support for Sepolia (authored by @​Applecakeman in #186)

v0.5.31

• 🐛 Fix bug with Optimism Goerli verification (authored by @​d10r in #183)

v0.5.30

• 🐛 Fix issue where contracts from NPM packages could not be found when truffle-plugin-verify was installed globally (see #111)

v0.5.29

• ✨ Add support for Arbitrum Goerli and Optimism Goerli (authored by @​d10r in #179)

v0.5.28

• ✨ Add support for Gnosis Chain verification on Gnosisscan (authored by @​alebanzas in #175)

v0.5.27

• 🐛 Support verification of custom proxies with custom deployment, i.e. without using OpenZeppelin (co-authored with @​akshaydevh & @​d10r)

v0.5.26

... (truncated)

Commits

• b2d8860 Added support for OpBNB (#209)
• bf6b950 Update README.md
• 14ee26c Update README.md
• fe08600 Bump version to 0.6.6
• 3cd69d8 fix celoscan URL (#208)
• 829d160 fix basescan url (#204)
• a3a04cd Bump version to 0.6.4
• 4d296ad Added support for Base & zkEVM (#202)
• 6806b11 Bump version 0.6.3
• f67b8cc yarn lint
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 show <dependency name> 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)

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: ? → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report