Version Packages (next) #1371
Version Packages (next) #1371
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Caution Review failedThe pull request is closed. WalkthroughThe recent changes involve a series of version updates across multiple packages in the TEVM ecosystem, primarily advancing to version Changes
Possibly related issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
packages/evm/CHANGELOG.md (1)
7-7: Update references totevm/base-clientin documentation and TypeScript files.The renaming of
tevm/base-clienttotevm/nodeis not fully reflected in the codebase. Specifically, the following references need to be updated:
- Documentation:
docs/src/content/docs/learn/tevm-node/index.mdcontains a reference totevm/base-client.- TypeScript Declaration:
cli/dist/server/startTevm.d.tsincludes a reference to@tevm/base-client.Please update these references to ensure consistency with the recent changes.
Analysis chain
Verify all references to
tevm/base-clienthave been updated totevm/node.The changelog notes the renaming of
tevm/base-clienttotevm/node. Ensure that all references in the codebase have been updated accordingly.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all references to `tevm/base-client` have been updated to `tevm/node`. # Test: Search for occurrences of `tevm/base-client`. Expect: No remaining references. rg 'tevm/base-client'Length of output: 38719
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (61)
- .changeset/pre.json (2 hunks)
- bundler-packages/tevm-run/CHANGELOG.md (1 hunks)
- bundler-packages/tevm-run/package.json (1 hunks)
- experimental/solc/CHANGELOG.md (1 hunks)
- experimental/solc/package.json (1 hunks)
- extensions/ethers/CHANGELOG.md (1 hunks)
- extensions/ethers/package.json (1 hunks)
- extensions/viem/CHANGELOG.md (1 hunks)
- extensions/viem/package.json (1 hunks)
- packages/actions/CHANGELOG.md (1 hunks)
- packages/actions/package.json (1 hunks)
- packages/address/CHANGELOG.md (1 hunks)
- packages/address/package.json (1 hunks)
- packages/block/CHANGELOG.md (1 hunks)
- packages/block/package.json (1 hunks)
- packages/blockchain/CHANGELOG.md (1 hunks)
- packages/blockchain/package.json (1 hunks)
- packages/client-types/CHANGELOG.md (1 hunks)
- packages/client-types/package.json (1 hunks)
- packages/common/CHANGELOG.md (1 hunks)
- packages/common/package.json (1 hunks)
- packages/contract/CHANGELOG.md (1 hunks)
- packages/contract/package.json (1 hunks)
- packages/decorators/CHANGELOG.md (1 hunks)
- packages/decorators/package.json (1 hunks)
- packages/errors/CHANGELOG.md (1 hunks)
- packages/errors/package.json (1 hunks)
- packages/evm/CHANGELOG.md (1 hunks)
- packages/evm/package.json (1 hunks)
- packages/http-client/CHANGELOG.md (1 hunks)
- packages/http-client/package.json (1 hunks)
- packages/memory-client/CHANGELOG.md (1 hunks)
- packages/memory-client/package.json (1 hunks)
- packages/node/CHANGELOG.md (1 hunks)
- packages/node/package.json (1 hunks)
- packages/precompiles/CHANGELOG.md (1 hunks)
- packages/precompiles/package.json (1 hunks)
- packages/predeploys/CHANGELOG.md (1 hunks)
- packages/predeploys/package.json (1 hunks)
- packages/procedures/CHANGELOG.md (1 hunks)
- packages/procedures/package.json (1 hunks)
- packages/receipt-manager/CHANGELOG.md (1 hunks)
- packages/receipt-manager/package.json (1 hunks)
- packages/server/CHANGELOG.md (1 hunks)
- packages/server/package.json (1 hunks)
- packages/state/CHANGELOG.md (1 hunks)
- packages/state/package.json (1 hunks)
- packages/sync-storage-persister/CHANGELOG.md (1 hunks)
- packages/sync-storage-persister/package.json (1 hunks)
- packages/tx/CHANGELOG.md (1 hunks)
- packages/tx/package.json (1 hunks)
- packages/txpool/CHANGELOG.md (1 hunks)
- packages/txpool/package.json (1 hunks)
- packages/utils/CHANGELOG.md (1 hunks)
- packages/utils/package.json (1 hunks)
- packages/vm/CHANGELOG.md (1 hunks)
- packages/vm/package.json (1 hunks)
- test/test-utils/CHANGELOG.md (1 hunks)
- test/test-utils/package.json (1 hunks)
- tevm/CHANGELOG.md (1 hunks)
- tevm/package.json (1 hunks)
Files skipped from review due to trivial changes (45)
- .changeset/pre.json
- bundler-packages/tevm-run/CHANGELOG.md
- bundler-packages/tevm-run/package.json
- experimental/solc/CHANGELOG.md
- experimental/solc/package.json
- extensions/ethers/package.json
- extensions/viem/CHANGELOG.md
- extensions/viem/package.json
- packages/actions/CHANGELOG.md
- packages/actions/package.json
- packages/address/CHANGELOG.md
- packages/block/CHANGELOG.md
- packages/blockchain/CHANGELOG.md
- packages/client-types/CHANGELOG.md
- packages/common/CHANGELOG.md
- packages/contract/CHANGELOG.md
- packages/decorators/CHANGELOG.md
- packages/decorators/package.json
- packages/errors/CHANGELOG.md
- packages/evm/package.json
- packages/http-client/CHANGELOG.md
- packages/http-client/package.json
- packages/memory-client/CHANGELOG.md
- packages/memory-client/package.json
- packages/node/package.json
- packages/precompiles/CHANGELOG.md
- packages/precompiles/package.json
- packages/predeploys/CHANGELOG.md
- packages/procedures/package.json
- packages/receipt-manager/CHANGELOG.md
- packages/server/CHANGELOG.md
- packages/server/package.json
- packages/state/package.json
- packages/sync-storage-persister/CHANGELOG.md
- packages/sync-storage-persister/package.json
- packages/tx/CHANGELOG.md
- packages/txpool/CHANGELOG.md
- packages/txpool/package.json
- packages/utils/CHANGELOG.md
- packages/vm/CHANGELOG.md
- packages/vm/package.json
- test/test-utils/CHANGELOG.md
- test/test-utils/package.json
- tevm/CHANGELOG.md
- tevm/package.json
Additional comments not posted (21)
packages/client-types/package.json (1)
3-3: Version update approved.The version update to
2.0.0-next.105is consistent with the PR objectives and reflects a significant update.packages/predeploys/package.json (1)
3-3: Version update approved.The version update to
2.0.0-next.105is consistent with the PR objectives and reflects a significant update.packages/utils/package.json (1)
3-3: Version update approved.The version update to
2.0.0-next.105is consistent with the PR objectives and reflects a significant update.packages/common/package.json (1)
3-3: Version update approved.The version update to
2.0.0-next.105is approved. Ensure that this update reflects any breaking changes or major enhancements in the package, in accordance with semantic versioning practices.packages/block/package.json (1)
3-3: Version update approved.The version update to
2.0.0-next.105is approved. Ensure that this update reflects any breaking changes or major enhancements in the package, in accordance with semantic versioning practices.packages/tx/package.json (1)
3-3: Version update approved.The version update to
2.0.0-next.105is approved. Ensure that this update reflects any breaking changes or major enhancements in the package, in accordance with semantic versioning practices.packages/errors/package.json (1)
3-3: Verify the rationale for the major version bump.The version update from
1.1.0-next.100to2.0.0-next.105suggests significant changes. Ensure that all breaking changes or major enhancements are documented and communicated to users.packages/address/package.json (1)
3-3: Verify the rationale for the major version bump.The version update from
1.1.0-next.100to2.0.0-next.105suggests significant changes. Ensure that all breaking changes or major enhancements are documented and communicated to users.packages/receipt-manager/package.json (1)
3-3: Verify the rationale for the major version bump.The version update from
1.1.0-next.100to2.0.0-next.105suggests significant changes. Ensure that all breaking changes or major enhancements are documented and communicated to users.packages/contract/package.json (1)
3-3: Verify the impact of the major version update.The version update to
2.0.0-next.105indicates a major release, which might include breaking changes. Ensure that dependent packages or projects are compatible with this new version.packages/blockchain/package.json (1)
3-3: Verify the impact of the major version update.The version update to
2.0.0-next.105indicates a major release, which might include breaking changes. Ensure that dependent packages or projects are compatible with this new version.packages/state/CHANGELOG.md (3)
3-7: Ensure clarity in module renaming.The changelog entry clearly documents the renaming of
tevm/base-clienttotevm/node. Ensure that all references in the codebase are updated accordingly.
13-18: Check dependency updates.The changelog lists updated dependencies. Ensure these updates are necessary and compatible with the package.
9-11: Verify the bug fix description.The description of the bug fix in the changelog is clear. Ensure that the fix effectively resolves the issue with the state manager setting the code hash.
extensions/ethers/CHANGELOG.md (2)
3-7: Ensure consistency in module renaming.The changelog entry documents the renaming of
tevm/base-clienttotevm/node. Verify that all related code references are updated.
9-17: Verify dependency updates.The changelog lists updated dependencies. Ensure these updates are necessary and that they maintain compatibility across the package ecosystem.
packages/node/CHANGELOG.md (3)
3-8: Ensure clarity in module renaming description.The changelog entry for renaming
tevm/base-clienttotevm/nodeis clear and includes a reference to the relevant pull request and commit. This is helpful for users who want to trace the change.
9-24: List dependency updates clearly.The patch changes section lists updated dependencies with their new versions. This is well-structured and provides users with the necessary information to understand the scope of updates.
25-25: Historical entries are consistent and well-formatted.The previous changelog entries maintain consistency in formatting and provide a clear history of changes.
packages/procedures/CHANGELOG.md (2)
3-7: Verify consistent renaming oftevm/base-clienttotevm/node.Ensure that all references to
tevm/base-clienthave been updated totevm/nodethroughout the codebase to avoid any inconsistencies.Verification successful
Renaming Verified:
tevm/base-clienttotevm/nodeThe codebase has been successfully updated to reflect the renaming of
tevm/base-clienttotevm/node, with no remaining outdated references found.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify that all references to `tevm/base-client` have been updated to `tevm/node`. # Test: Search for any remaining references to `tevm/base-client`. Expect: No results. rg --type python --type javascript 'tevm/base-client'Length of output: 84
Script:
#!/bin/bash # Description: Verify that all references to `tevm/base-client` have been updated to `tevm/node`. # Test: Search for any remaining references to `tevm/base-client`. Expect: No results. rg --type py --type js 'tevm/base-client'Length of output: 41
9-25: Verify dependency updates in package configuration files.Ensure that the listed dependency updates to version
2.0.0-next.105are accurately reflected in the package configuration files, such aspackage.json.
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
ecea831 to
d249b65
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/node@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
#1370
1dcfd69Thanks @roninjin10! - Fixed bug where state manager wouldn't set the code hash when modifying deployedBytecodeUpdated dependencies [
1dcfd69]:@tevm/[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69]:[email protected]
Minor Changes
1dcfd69Thanks @roninjin10! - Renamed tevm/base-client to tevm/nodePatch Changes
1dcfd69,1dcfd69]:[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Patch Changes
1dcfd69,1dcfd69]:@tevm/[email protected]
Patch Changes
Summary by CodeRabbit
New Features
Version Updates
2.0.0-next.105, indicating updates and enhancements.Changelog Updates
tevm/base-clienttotevm/node.