-
Notifications
You must be signed in to change notification settings - Fork 10
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
v0.6.5 #866
v0.6.5 #866
Conversation
redone to keep Python 3.9 for now @marscher I have set the testing pipeline to use 3.10 as the main Version from now on until we can look deeper into the |
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!
Codecov Report
@@ Coverage Diff @@
## master #866 +/- ##
==========================================
+ Coverage 96.48% 96.51% +0.02%
==========================================
Files 94 94
Lines 6230 6283 +53
==========================================
+ Hits 6011 6064 +53
Misses 219 219 see 12 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
The cached environment seems a little messed up for today, but without caching Python 3.9 passes: https://github.com/BAMWelDX/weldx/actions/runs/4629167902/jobs/8189100689 |
Changes
scipy
andnetworkx
versionscreate release PR
vX.Y.Z
and add therelease
tag (example here)
CHANGELOG.md
is up-to-date and enter current date to the release versionCITATION.cff
version number and datedeprecated
and remove deprecated codeMerge the Pull Request
add Git(hub) tag
doubt use vX.Y.Z everywhere)
ReadTheDocs updates
latest
,stable
andvX.Y.Z
get triggered on RTD (the tag build can gettriggered twice, resulting in a failed/duplicated build, no need to worry)
pypi release
build
action completes hereconda-forge release
pull-request here
meta.yaml
in the pull request, manually update all changes in the build and run dependencies