Closed CagtayFabry closed 1 year ago
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 fs
issue
2 189 tests ±0 2 188 :heavy_check_mark: ±0 2m 43s :stopwatch: -57s 1 suites ±0 1 :zzz: ±0 1 files ±0 0 :x: ±0
Results for commit 0d34c82f. ± Comparison against base commit 4ac203ef.
:recycle: This comment has been updated with latest results.
Merging #866 (0d34c82) into master (4ac203e) will increase coverage by
0.02%
. The diff coverage isn/a
.
@@ 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
ReadTheDocs updates
latest
,stable
andvX.Y.Z
get triggered on RTD (the tag build can get triggered twice, resulting in a failed/duplicated build, no need to worry)pypi release
build
action completes hereconda-forge release
meta.yaml
in the pull request, manually update all changes in the build and run dependencies