chore(deps): bump @noble/hashes from 2.2.0 to 2.3.0 - #923
Conversation
Bumps [@noble/hashes](https://github.com/paulmillr/noble-hashes) from 2.2.0 to 2.3.0. - [Release notes](https://github.com/paulmillr/noble-hashes/releases) - [Commits](paulmillr/noble-hashes@2.2.0...2.3.0) --- updated-dependencies: - dependency-name: "@noble/hashes" dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a6ea7493bb
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| }, | ||
| "dependencies": { | ||
| "@noble/hashes": "^2.2.0" | ||
| "@noble/hashes": "^2.3.0" |
There was a problem hiding this comment.
Because this narrows @morpho-org/blue-sdk's published runtime dependency range, consumers will not receive the updated manifest unless @morpho-org/blue-sdk is bumped and republished; this commit does not add or update a changeset for that package, and the existing .changeset/fresh-sdks-dependencies.md omits it, so the version workflow would leave the registry package on the old ^2.2.0 range. Add a patch changeset for @morpho-org/blue-sdk or include it in the existing dependency-refresh changeset.
AGENTS.md reference: AGENTS.md:L168-L170
Useful? React with 👍 / 👎.
| }, | ||
| "dependencies": { | ||
| "@noble/hashes": "^2.2.0" | ||
| "@noble/hashes": "^2.3.0" |
There was a problem hiding this comment.
Because this narrows @morpho-org/blue-sdk's published runtime dependency range, consumers will not receive the updated manifest unless @morpho-org/blue-sdk is bumped and republished; this commit does not add or update a changeset for that package, and the existing .changeset/fresh-sdks-dependencies.md omits it, so the version workflow would leave the registry package on the old ^2.2.0 range. Add a patch changeset for @morpho-org/blue-sdk or include it in the existing dependency-refresh changeset.
Useful? React with 👍 / 👎.
Bumps @noble/hashes from 2.2.0 to 2.3.0.
Release notes
Sourced from @noble/hashes's releases.
Commits
8060cc8Release 2.3.0.16f8af9Update workflow and benchmarks734220fUpdate jsbt to 0.6.5fd3d3c3Minor improvements3654405test: use new syntaxe222e2dutils: minor fixesef7ae52Improve speed. Reduce bundle size. Reduce mem usage.26b194aRename npm actione89d6faBump jsbt to v0.6de8098aMove benchmarks top-levelDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)