-
Notifications
You must be signed in to change notification settings - Fork 51
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
prepare release 2.4.0 #398
Conversation
orbeckst
commented
Sep 17, 2024
- towards new release 2.4.0 for JOSS paper #396
- fix switch from setup.py to pyproject.toml #385 (modernize build system)
- finalize CHANGES
84887a8
to
ce93898
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #398 +/- ##
==========================================
- Coverage 98.78% 98.78% -0.01%
==========================================
Files 28 28
Lines 1980 1978 -2
Branches 435 435
==========================================
- Hits 1956 1954 -2
Misses 2 2
Partials 22 22 ☔ View full report in Codecov by Sentry. |
ce93898
to
0283a22
Compare
0283a22
to
398d431
Compare
Note: needs to be merged (not squashed) because the blackify-commit should be on its own so that .git-ignore-revs correctly works. |
398d431
to
ee8b769
Compare
- fix #385 - use pyproject.toml instead of setup.py (note: may need to change README for PyPi to exclude banners) - remove versioneer and use versioningit (use alchemlyb.__version__ directly where the version is needed, e.g., for sphinx docs) - updated CHANGES for 2.4.0
- gitignore _version - ignore commits for blame that contain black-reformatting (in particular we forgot to include #280)
ee8b769
to
dadd845
Compare
Later on if I have time, I think |
Might be good to squash merge next time. |
Thanks for the review.
This needed to be merged so that commit IDs remained intact for the black-only commit or how would you have done the .git-ignore-revs? |
I see. Sorry I don't quite know how |