oz 5.5.0

[thedavidmeister]

Motivation

Solution

Checks

By submitting this for review, I'm confirming I've done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Summary by CodeRabbit

• Chores
  • Updated a dependency submodule reference to a newer version.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated the lib/openzeppelin-contracts submodule reference from one commit to another. No code, API, or control flow changes introduced. This is a pointer update only.

Changes

Cohort / File(s)	Summary
Submodule Update lib/openzeppelin-contracts	Updated submodule commit reference from dc44c9f to fcbae53

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'oz 5.5.0' is related to the changeset's main objective of updating the OpenZeppelin Contracts library submodule to version 5.5.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 2025-11-28-oz

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e286c7 and 7b4b992.

⛔ Files ignored due to path filters (1)

• foundry.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• lib/openzeppelin-contracts (1 hunks)

🔇 Additional comments (2)

lib/openzeppelin-contracts (2)

1-1: Ensure PR checklist is completed and document testing against OpenZeppelin v5.5.0.

OpenZeppelin Contracts v5.5.0 includes a documented breaking change to the Account module's _validateUserOp function signature (added bytes signature parameter). While this codebase does not appear to use the affected Account module, the PR process remains incomplete:

• All four checklist items remain unchecked
• No description documenting testing or compatibility verification for v5.5.0
• No linked issues or migration notes

Before merging, please complete the PR checklist and confirm that the codebase has been tested against v5.5.0. If there are other OZ dependencies or future usage of the Account module, ensure any necessary updates are completed.

---

1-1: No compatibility issues found with OpenZeppelin v5.5.0 upgrade.

The v5.5.0 breaking change affects Account._validateUserOp signature, but this repository only imports Clones from OpenZeppelin (used in CloneFactory.sol). The Clones library has no breaking changes in v5.5.0, and no Account contracts are implemented or used in this codebase. Tests should pass without any migration steps.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}