chore: support only the last three Elixir and OTP releases - #16
Conversation
Carrying releases that upstream no longer patches costs CI time and blocks adopting anything newer than Elixir 1.11, while leaving us on a Postgrex with two open SQL injection advisories. The `fsm` dependency is vendored because it has had no release since 2017 and its generated code cannot pass the current type checker from inside `deps/`. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryMedium Risk Overview Postgrex The unmaintained Tests and CI hygiene fixes include descending ranges ( Reviewed by Cursor Bugbot for commit f60cadc. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Warning Review limit reachedNext included review available in 15 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (16)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe project updates Elixir and OTP support, replaces the external FSM dependency with ChangesElixir and FSM modernization
Priority: ➖ Normal Estimated code review effort: 4 (Complex) | ~45 minutes Change: Other Merge Risk: ⚪ Minimal · up to The supported Elixir/OTP matrix is updated without an established requirement to block newer Elixir releases, so no actionable merge risk remains. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 14 functions across 12 files. (3 skipped: 3 unsupported.) ✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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. A rabbit checks the newer state Comment |
A single flaky row cancelled the other two, so a red build said nothing about whether the other Elixir and OTP pairs actually work. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
`mix test.all` exercises the migration environment, but only StorageCase created that database, so any seed that scheduled EventStore.ConfigTest first failed on a database that did not exist yet. The flake predates the matrix change and hit a different row on each run. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
mix.exspinned at~> 1.11, so nothing newer could be adopted.~> 0.17left two open SQL injection advisories againstPostgrex.Notificationsunaddressed (CVE-2026-32687, HIGH, and CVE-2026-58225, LOW).fsmdependency is vendored rather than patched because it has had no release since 2017 and its__using__expands into our module, so the warnings it generates cannot be suppressed fromdeps/.decimal2 to 3.