-
Notifications
You must be signed in to change notification settings - Fork 116
Release v2.2.0 #372
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
Release v2.2.0 #372
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #372 +/- ##
========================================
Coverage 83.80% 83.80%
========================================
Files 24 24
Lines 8167 8167
========================================
Hits 6844 6844
Misses 1323 1323
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
@@ -4,7 +4,7 @@ build-backend = "scikit_build_core.build" | |||
|
|||
[project] | |||
name = "spglib" | |||
version = "2.1.0" | |||
version = "2.2.0" | |||
requires-python = ">=3.7" |
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.
python 3.7 is EOL. Should we change it to 3.8? For me, either is fine.
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.
Agree should drop 3.7
. Let's do it the first thing after the release
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.
Also update the version in CMakeLists.txt
I will merge this PR and release |
Thanks @lan496! |
|
Oops, I forgot to revert sphinx-book-theme dependency. |
Oh you're right, forgot about that as well. There is a pre-release out, I can patch the rtd to get it working when I get to work. Do you want to move the tag after that? |
🙏 |
For now, I will create a new branch to release v2.2.0 and revert the commit. |
|
I was concerned that the documentation would not build (and it doesn't), but apparently we caught a bug/race-condition in rtd that it still used the old commit https://readthedocs.org/projects/spglib/builds/22790068/ We can count our blessings and leave it at this, or we force push the tag again PS: No need for a new branch for this since main should have this commit as well. But naming convention should be |
Let me take over that, I'll add the fixes to rtd there as well |
@LecrisUT Thanks. I defer to you for applying patch on top of |
No need for a |
Closes #350
After this PR is merged, I'll put
v2.2.0
tag to the commit.List of merged PRs were generated by