release 0.4.0! #416
release 0.4.0! #416
Conversation
zachschuermann
requested review from
nicklan,
scovich,
hntd187,
rtyler and
OussamaSaoudi-db
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #416 +/- ##
=======================================
Coverage 78.82% 78.82%
=======================================
Files 51 51
Lines 10655 10655
Branches 10655 10655
=======================================
Hits 8399 8399
Misses 1788 1788
Partials 468 468 ☔ View full report in Codecov by Sentry. |
Thanks! And yea, this is generally done as best-effort by me going through every PR that merged since the last release..
Yea good idea, I can try to add more to breaking changes to help migrations. |
| @@ -183,4 +183,4 @@ Some design principles which should be considered: | |||
| [cargo-llvm-cov]: https://github.com/taiki-e/cargo-llvm-cov | |||
| [FFI]: ffi/ | |||
| [Arrow]: https://arrow.apache.org/rust/arrow/index.html | |||
| [Tokio]: https://tokio.rs/ | |||
| [Tokio]: https://tokio.rs/ | |||
There was a problem hiding this comment.
out of curiosity, what changed here?
There was a problem hiding this comment.
I think the newline? idk maybe some editor junk?
There was a problem hiding this comment.
I think the file didn't have a newline at EOF before, and now it does?
zachschuermann
force-pushed
the
prepare-0.4.0
branch
from
f0fa784 to
c05570c
Compare
CHANGELOG.md
Outdated
| 3. new `WriterFeatures` enum variant: `TypeWidening` and `TypeWideningPreview` [\#335] | ||
| 4. new `Error` enum variant: `InvalidLogPath` when kernel is unable to parse the name of a log path [\#347] | ||
| 5. Module moved: `mod delta_kernel::transaction` -> `mod delta_kernel::actions::set_transaction` [\#386] | ||
| 6. output of arrow expression evaluation now applies/validates output schema in default arrow expression handler [\#331] |
There was a problem hiding this comment.
Is this one really a breaking change? Seems like it would just allow previously broken stuff to no longer break?
There was a problem hiding this comment.
Hm yea I had the same question (where we should put those changes to expression evaluation). I agree it "allows previously broken stuff to no longer break" and since the semantics remain the same (just that we are enforcing/implementing it now) perhaps this goes under 'fixes'? WDYT @nicklan @scovich
There was a problem hiding this comment.
Yeah, fixes is probably good. I don't know how critical it is that we get the changelog "just right" at this point, but nothing will break due to this change (i don't think) so fixes or enhancements makes sense.
There was a problem hiding this comment.
thanks! releasing!
zachschuermann
force-pushed
the
prepare-0.4.0
branch
from
de304a0 to
9ef83c6
Compare
Release 0.4.0 of all crates! rendered changelog link