Repository navigation
chore(deps): bump substrait packages to 0.102.0 - #290
Conversation
Bumps substrait-protobuf, substrait-extensions, and substrait-antlr to spec v0.102.0. - The integer offset of the Preceding/Following window bounds is deprecated in favour of offset_expr. The migration is consumer-first and nothing here reads window bounds; over(rows=.../range=...) keeps emitting offset, which remains valid. - bounds_type is now required whenever a bound is CurrentRow, Preceding, or Following. over() already sets it whenever a frame is given; without a frame both bounds are left unset, which does not require it. - The new decimal negate overload resolves through the default registry with no change.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughDependency declarations for ChangesSubstrait version update
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to No introduced compatibility or runtime risk was established; the dependency update is mergeable. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 1 system. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 4 | ❓ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
Full details: Linked Issues checkExplanation Issue ✨ 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 |
Closes #255.
Bumps
substrait-protobuf,substrait-extensions, andsubstrait-antlrto spec v0.102.0 (release notes).offsetof thePreceding/Followingwindow bounds is deprecated in favour ofoffset_expr. The migration is consumer-first and nothing here reads window bounds;over(rows=…/range=…)keeps emittingoffset, which remains valid.bounds_typeis now required whenever a bound isCurrentRow,Preceding, orFollowing.over()already sets it whenever a frame is given; without a frame both bounds are left unset, which does not require it.negateoverload resolves through the default registry with no change.🤖 Generated with AI