chainx-org / ChainX

Bitcoin's layer2 smart contract network has already supported WASM and EVM, and is supporting MoveVM
https://chainx.org
GNU General Public License v3.0
323 stars 120 forks source link

Bump debug and hardhat in /contracts/uniswap-contracts #688

Closed dependabot[bot] closed 7 months ago

dependabot[bot] commented 9 months ago

Bumps debug to 4.3.4 and updates ancestor dependency hardhat. These dependencies need to be updated together.

Updates debug from 3.2.6 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

New Contributors

Full Changelog: https://github.com/debug-js/debug/compare/4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

Thank you to @​taylor1791 and @​kristofkalocsai for their contributions.


Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@​qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits
  • da66c86 4.3.4
  • 9b33412 replace deprecated String.prototype.substr() (#876)
  • c0805cc add section about configuring JS console to show debug messages (#866)
  • 043d3cd 4.3.3
  • 4079aae update license and more maintainership information
  • 19b36c0 update repository location + maintainership information
  • f851b00 adds README section regarding usage in child procs (#850)
  • d177f2b Remove accidental epizeuxis
  • e47f96d 4.3.2
  • 1e9d38c cache enabled status per-logger (#799)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.


Updates hardhat from 2.1.2 to 2.19.2

Release notes

Sourced from hardhat's releases.

Hardhat v2.19.2

This release adds experimental support for ESM in typescript projects.

In addition to that, the hardhat-shorthand tool (hh) now supports scoped tasks.

Hardhat v2.19.1

This release fixes a couple of issues:

  • A problem in low-traffic chains that resulted in txs using a maxPriorityFeePerGas of 0, which were then rejected by the node.
  • A bug in the compiler downloader that was triggered in big projects that used many different versions of solc.

Besides that, the project initialization now uses the latest version of the Hardhat Toolboxes.

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.

... (truncated)

Commits
  • 9343122 Version Packages
  • 309dc21 Merge pull request #4647 from NomicFoundation/esm-support-hardhat-viem
  • b475fc4 Create dry-moose-draw.md
  • beca2be Exclude artifacts/package.json from artifacts in getArtifactPaths
  • efbcce6 Merge pull request #4586 from NomicFoundation/esm-ts-support
  • c706084 Update .changeset/shaggy-hornets-exercise.md
  • 441415f Merge pull request #4571 from 4rgon4ut/patch-1
  • 70eef0a Update chiado urls
  • 1467d2d Merge pull request #4644 from devmev10/patch-1
  • 1b52aef Merge pull request #4642 from SantiagoDevRel/add-web3-v4-plugin
  • 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/chainx-org/ChainX/network/alerts).
dependabot[bot] commented 7 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available.

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