-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V2.2.1 #589
V2.2.1 #589
Conversation
it is pretty outdated considering we don't have the GPU backend anymore and performance is different now.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #589 +/- ##
=======================================
Coverage 91.41% 91.41%
=======================================
Files 35 35
Lines 4496 4496
=======================================
Hits 4110 4110
Misses 386 386
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for putting this together! I'm compiling release notes - I'll paste them in a comment here so you can take a look before I put them in a Github release. Also, do you think we should include any files in the Github release itself? I vaguely recall talking about that one time.
@@ -134,7 +134,7 @@ | |||
# but how should we make it work with other python versions? | |||
manifold3d = with pkgs.python3Packages; buildPythonPackage { | |||
pname = "manifold3d"; | |||
version = "2.2.0"; | |||
version = "2.2.1"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think it would be worthwhile to build a little release script to update all the version numbers and ensure they're consistent?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sounds good
Sure. Maybe we should put this in the repo as well? You can just update this PR I think.
What files? I forgot about this. |
Release notes - I've never seen them checked into a repo; I generally just put them here. I won't worry about files - looks like Github automatically attaches the source code zip file anyway. Do these release notes look decent? We did a lot... This is another significant update, bringing 2D support, lossless roundtrip of Manifolds through glTF, Python bindings published on PyPI, and a whole new triangulator that fixes lots of geometric edge cases in the Boolean. And of course many bug fixes and performance improvements - a huge thank you to all the contributors! New Features
Bindings
Bug Fixes
Performance Improvements
Build/CI Updates
Examples
ManifoldCAD.org
|
You added one more backtick for |
Okay, I did the Github and npm releases. Did you see the failed actions in uploading to PyPI? It looks like it's having trouble with the wheels OS matrix, because the first one succeeds, but the following ones fail to publish because they already exist. Maybe a names thing? I don't know much about Python packaging... FYI I'm going to bed now. |
it seems that it is published, but for some reason the release triggered 3 actions and attempts to publish 3 times. |
* added notes about twistDegree and nDivisions * update version * removed perf comparison figure it is pretty outdated considering we don't have the GPU backend anymore and performance is different now.
V2.2.1 release. I updated the versions, added npm and PyPI badges, and removed the old performance plot because it is too outdated now. I also updated the documentation of extrude to close #563.
This is V2.2.1 because I accidentally published V2.2.0 on PyPI, so V2.2.0 will require removing one version in PyPI which I try not to do.