Conversation
|
@elalish I'm thinking if we should still put ManifoldCAD stuff in the release notes, since that is not really part of the release? |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1605 +/- ##
=======================================
Coverage 95.16% 95.16%
=======================================
Files 34 34
Lines 7659 7659
=======================================
Hits 7289 7289
Misses 370 370 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
elalish
left a comment
There was a problem hiding this comment.
Sounds good. As for ManifoldCAD - well, it's in the monorepo, and if it's not in these notes, where would it be? I suppose we could have a little "what's new" pop-up when the service worker gets a new version (once we restrict it to published release versions), but until then it can stay here.
|
Weird, looks like our npm publish action is still failing: https://github.com/elalish/manifold/actions/runs/23474959650/job/68305685392 Oddly it says it's trying to publish 3.4.0 instead of 3.4.1? |
This version reverts the lazy collider change (which causes numerical issues in some cases), fixes npm publish failure, fixes some minor bugs and improves ManifoldCAD.
Notable Bug Fixes
manifold_cross_section_warp_contextC binding by @swaparup36 in fix: implement manifold_cross_section_warp_context C binding #1597.ManifoldCAD Updates
Documentation Changes
Miscellaneous
New Contributors