-
Notifications
You must be signed in to change notification settings - Fork 11
Release 2025.05.24 #217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2025.05.24 #217
Conversation
WalkthroughThe changes update the Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Paymaster
participant Blockchain
User->>Paymaster: Request transaction (with chainId)
Paymaster->>Paymaster: Convert chainId to string
Paymaster->>Paymaster: Check if chainId in skipType2Txns
alt chainId in skipType2Txns
Paymaster->>Blockchain: Send legacy (type 0) transaction
else chainId not in skipType2Txns
Paymaster->>Blockchain: Send EIP-1559 (type 2) transaction
end
Blockchain-->>Paymaster: Transaction result
Paymaster-->>User: Return result
Possibly related PRs
Suggested reviewers
Poem
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. ✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (3)
backend/CHANGELOG.md(1 hunks)backend/package.json(1 hunks)backend/src/paymaster/index.ts(7 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
backend/CHANGELOG.md
2-2: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Above
(MD022, blanks-around-headings)
2-2: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
3-3: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
3-3: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Cloudflare Pages
🔇 Additional comments (5)
backend/package.json (1)
3-3: LGTM! Correct semantic versioning for bugfix.The patch version bump from
4.1.0to4.1.1correctly follows semantic versioning conventions for a bugfix release.backend/src/paymaster/index.ts (4)
64-64: LGTM! Correct type definition for string-based chain ID handling.The interface change from
number[]tostring[]properly reflects the intended usage of chain IDs as strings in the configuration.
82-82: LGTM! Property type updated consistently.The class property type correctly matches the interface definition.
96-96: LGTM! Simplified constructor assignment.The constructor now directly assigns the string array without unnecessary number conversion, which aligns with the corrected type definition.
1133-1133: LGTM! Consistent string comparison fix applied across all usage sites.All five locations where
skipType2Txnsis checked now correctly convertchainIdto string before comparison usingchainId.toString(). This ensures consistent behavior and fixes the type mismatch that was causing the bug.The fix is comprehensive and addresses:
whitelistAddressesmethod (line 1133)removeWhitelistAddressmethod (line 1186)depositmethod (line 1250)deployVpmethod (line 1313)addStakemethod (line 1360)Also applies to: 1186-1186, 1250-1250, 1313-1313, 1360-1360
| ## [4.1.1] - 2025-05-24 | ||
| - Fixed bug of comparing chainId as string for skipping type2 to legacy txn | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick (assertive)
Fix markdown formatting issues.
The changelog entry correctly documents the bugfix, but there are formatting issues that should be addressed:
Apply this diff to fix the markdown formatting:
+
## [4.1.1] - 2025-05-24
+
-- Fixed bug of comparing chainId as string for skipping type2 to legacy txn
+- Fixed bug of comparing chainId as string for skipping type2 to legacy txn
+📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## [4.1.1] - 2025-05-24 | |
| - Fixed bug of comparing chainId as string for skipping type2 to legacy txn | |
| ## [4.1.1] - 2025-05-24 | |
| - Fixed bug of comparing chainId as string for skipping type2 to legacy txn | |
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
2-2: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Above
(MD022, blanks-around-headings)
2-2: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below
(MD022, blanks-around-headings)
3-3: Trailing spaces
Expected: 0 or 2; Actual: 1
(MD009, no-trailing-spaces)
3-3: Lists should be surrounded by blank lines
null
(MD032, blanks-around-lists)
🤖 Prompt for AI Agents
In backend/CHANGELOG.md around lines 2 to 4, the markdown formatting of the
changelog entry is incorrect. Fix the formatting by ensuring the version header
is properly formatted as a markdown heading (e.g., starting with ## and a
space), and the bullet point describing the fix is correctly indented and uses a
hyphen followed by a space. Remove any trailing spaces or formatting
inconsistencies to comply with standard markdown syntax.
Description
Types of changes
What types of changes does your code introduce?
Further comments (optional)
Summary by CodeRabbit
Bug Fixes
Documentation
Chores