chore: update standard contracts to v2 #269

fadeev · 2025-06-12T08:20:50Z

Summary by CodeRabbit

Chores
- Updated the dependency version for "@zetachain/standard-contracts" in example projects to the stable 2.0.1 release.
- Added .openzeppelin to the ignore list in example projects to prevent tracking of build artifacts.

coderabbitai · 2025-06-12T08:20:56Z

📝 Walkthrough

Walkthrough

The dependency version for "@zetachain/standard-contracts" was updated from the release candidate "2.0.0-rc5" to the stable version "2.0.1" in the package.json files of both the NFT and token example projects. Additionally, the .gitignore files in these examples were modified to include the .openzeppelin directory.

Changes

File(s)	Change Summary
examples/nft/package.json, examples/token/package.json	Updated "@zetachain/standard-contracts" dependency from "2.0.0-rc5" to "2.0.1".
examples/nft/.gitignore, examples/token/.gitignore	Added `.openzeppelin` to ignore patterns; added newline in `examples/nft/.gitignore`.

Sequence Diagram(s)

No sequence diagrams are generated as the changes are limited to dependency version updates and .gitignore modifications, which do not affect control flow or feature logic.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e28a24a and d6c2160.

⛔ Files ignored due to path filters (2)

examples/nft/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
examples/token/yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (4)

examples/nft/.gitignore (1 hunks)
examples/nft/package.json (1 hunks)
examples/token/.gitignore (1 hunks)
examples/token/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (2)

examples/nft/.gitignore
examples/token/.gitignore

🚧 Files skipped from review as they are similar to previous changes (2)

examples/token/package.json
examples/nft/package.json

⏰ Context from checks skipped due to timeout of 90000ms (8)

GitHub Check: test (examples/hello)
GitHub Check: test (examples/swap)
GitHub Check: test (examples/token)
GitHub Check: test (examples/call)
GitHub Check: test (examples/nft)
GitHub Check: slither (examples/call, call.sarif)
GitHub Check: slither (examples/hello, hello.sarif)
GitHub Check: slither (examples/swap, swap.sarif)

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

coderabbitai

Actionable comments posted: 0

🧹 Nitpick comments (1)

examples/token/package.json (1)

60-60: Broadened version constraint for @zetachain/standard-contracts
Switching from a fixed RC to ^2.0.0 allows all future v2.x.x releases. Confirm there are no breaking changes in upcoming minors and regenerate your lockfile to pin the resolved version.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9668a20 and e28a24a.

⛔ Files ignored due to path filters (2)

examples/nft/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
examples/token/yarn.lock is excluded by !**/yarn.lock, !**/*.lock

📒 Files selected for processing (2)

examples/nft/package.json (1 hunks)
examples/token/package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (3)

GitHub Check: slither (examples/hello, hello.sarif)
GitHub Check: slither (examples/swap, swap.sarif)
GitHub Check: slither (examples/call, call.sarif)

🔇 Additional comments (1)

examples/nft/package.json (1)

60-60: Broadened version constraint for @zetachain/standard-contracts
This mirrors the token example’s update—moving to ^2.0.0 widens compatibility. Ensure CI tests pass against the latest patch and minor releases, then update your lockfile accordingly.

s2imonovic

LGTM

fadeev · 2025-06-12T10:24:27Z

I realized we need better gas limit defaults so that mint and transfer don't fail.

zeta-chain/standard-contracts#76

chore: update standard contracts to v2

e28a24a

fadeev marked this pull request as ready for review June 12, 2025 08:25

fadeev requested a review from a team as a code owner June 12, 2025 08:25

coderabbitai bot reviewed Jun 12, 2025

View reviewed changes

fadeev marked this pull request as draft June 12, 2025 09:08

s2imonovic approved these changes Jun 12, 2025

View reviewed changes

fadeev marked this pull request as ready for review June 16, 2025 12:26

fadeev added 2 commits June 16, 2025 15:26

standard-contracts v2.0.1

242f7ae

ignore .openzeppelin dir

d6c2160

s2imonovic approved these changes Jun 16, 2025

View reviewed changes

fadeev merged commit 2b83efb into main Jun 16, 2025
14 checks passed

fadeev deleted the chore-update-standard-contracts-v2 branch June 16, 2025 14:41

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore: update standard contracts to v2 #269

chore: update standard contracts to v2 #269

Uh oh!

fadeev commented Jun 12, 2025 •

edited by coderabbitai bot

Loading

Uh oh!

coderabbitai bot commented Jun 12, 2025 •

edited

Loading

Walkthrough

Changes

Sequence Diagram(s)

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Uh oh!

coderabbitai bot left a comment

Uh oh!

s2imonovic left a comment

Uh oh!

fadeev commented Jun 12, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

chore: update standard contracts to v2 #269

chore: update standard contracts to v2 #269

Uh oh!

Conversation

fadeev commented Jun 12, 2025 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

coderabbitai bot commented Jun 12, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Sequence Diagram(s)

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

s2imonovic left a comment

Choose a reason for hiding this comment

Uh oh!

fadeev commented Jun 12, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

fadeev commented Jun 12, 2025 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Jun 12, 2025 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)