chore(main): release 2.3.3 - #178
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
5abf5d7 to
048e9c5
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe release metadata updates the project and manifest versions from 2.3.2 to 2.3.3. The changelog adds the 2.3.3 release entry with SimpleFIN fixes and a lockfile regeneration note. ChangesRelease metadata
Estimated code review effort: 1 (Trivial) | ~5 minutes Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to This release synchronizes version metadata and documents the 2.3.3 fixes. The versions and release date are consistent, with no remaining merge-blocking risk. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ 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. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5abf5d7b8b
ℹ️ 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".
| [project] | ||
| name = "family-office" | ||
| version = "2.3.2" | ||
| version = "2.3.3" |
There was a problem hiding this comment.
Regenerate uv.lock with the release version
Bumping the project to 2.3.3 leaves the editable family-office entry in uv.lock at 2.3.2. In the checked .pre-commit-config.yaml hook, uv run pytest performs its default sync (uv run --help describes --no-sync as the option that avoids it), so the next commit attempt rewrites the tracked lockfile and fails because the hook modified files; locked consumers also reject the stale lock. Include the corresponding uv.lock update in this release commit.
AGENTS.md reference: AGENTS.md:L45-L52
Useful? React with 👍 / 👎.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
2.3.3 (2026-09-10)
Fixed
Changed
This PR was generated with Release Please. See documentation.
Summary by CodeRabbit
Bug Fixes
Chores