Update review-ready changes#4
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (79)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Review rate limit: 0/1 reviews remaining, refill in 58 minutes and 48 seconds.Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 60e0a1d821
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| declare(strict_types=1); | ||
|
|
||
| namespace Semitexa\Update\Contract; | ||
| namespace Semitexa\Update\Domain\Contract; |
There was a problem hiding this comment.
Preserve old patch contract namespace for compatibility
Moving DataPatchInterface to Semitexa\Update\Domain\Contract without keeping a compatibility alias/file for Semitexa\Update\Contract\DataPatchInterface is a breaking runtime change for existing projects: previously valid patch classes that implement/import the old interface will fail discovery/loading after upgrade, and DataPatchDiscovery now validates against only the new symbol. Please keep the legacy namespace as a shim (or equivalent alias) so installed patches continue to run.
Useful? React with 👍 / 👎.
Summary
developtargetingmaster7commit(s) ahead,114changed file(s)Changes
Checks
What to Review
LICENSEREADME.mdcomposer.jsonresources/auto-deployresources/remote-deploysrc/Applicationsrc/Attributesrc/ConsoleWhat to Verify