-
Notifications
You must be signed in to change notification settings - Fork 105
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.3.0 #404
Release v2.3.0 #404
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #404 +/- ##
========================================
Coverage 83.71% 83.71%
========================================
Files 24 24
Lines 8205 8205
========================================
Hits 6869 6869
Misses 1336 1336
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ 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.
LGTM. Was just confirming that rc tags are working: https://github.com/LecrisUT/spglib/actions/runs/7676699614
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.
LGTM.
Let me try TestPyPI for practice. gco develop
git pull upstream develop
git tag v2.3.0-rc1
git push upstream v2.3.0-rc1 |
successfully uploaded to TestPyPI |
git tag v2.3.0
git push upstream v2.3.0 |
🤔 never tested with 2 tags on same commit |
It is rather my practice for the current CI 😌 |
v2.3.0 is released! |
Release note on GitHub |
The latest docs still point to v2.1.1.****? |
Indeed, but stable points to the new tag. Maybe we can rename stable to latest and latest to develop, wdyt? |
I've opened an issue for this. |
Closes #384
After this PR is merged, I'll put
v2.3.0-rc1
tag to the commit first. Thenv2.3.0
tag.List of merged PRs were generated by