BAMWelDX / weldx

The welding data exchange format
https://www.bam.de/weldx
BSD 3-Clause "New" or "Revised" License
19 stars 9 forks source link

v0.6.3 #850

Closed CagtayFabry closed 1 year ago

CagtayFabry commented 1 year ago

Changes

prepare v0.6.3 release

Checks

create release PR

Merge the Pull Request

add Git(hub) tag

ReadTheDocs update

pypi release

conda-forge release

github-actions[bot] commented 1 year ago

Test Results

2 187 tests  ±0   2 186 :heavy_check_mark: ±0   2m 35s :stopwatch: -34s        1 suites ±0          1 :zzz: ±0         1 files   ±0          0 :x: ±0 

Results for commit e700520d. ± Comparison against base commit c04bfda0.

:recycle: This comment has been updated with latest results.

codecov[bot] commented 1 year ago

Codecov Report

Merging #850 (e700520) into master (c04bfda) will increase coverage by 0.00%. The diff coverage is 66.66%.

@@           Coverage Diff           @@
##           master     #850   +/-   ##
=======================================
  Coverage   96.59%   96.59%           
=======================================
  Files          95       95           
  Lines        6222     6223    +1     
=======================================
+ Hits         6010     6011    +1     
  Misses        212      212           
Impacted Files Coverage Δ
weldx/transformations/cs_manager.py 98.60% <ø> (ø)
weldx/transformations/local_cs.py 96.35% <50.00%> (+0.01%) :arrow_up:
weldx/asdf/constants.py 100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

marscher commented 1 year ago

Why did you need to bump the manifest/extension version? I remember I was struggeling with adding the media_file schema to manifest and had some chat with Volker to resolve it.

CagtayFabry commented 1 year ago

Why did you need to bump the manifest/extension version? I remember I was struggeling with adding the media_file schema to manifest and had some chat with Volker to resolve it.

The manifest (and weldx extension) with version 0.1.1 have already been released in v0.6.2 (or earlier)

In those cases I prefer to create a new version to avoid any confusion and keep the release versions stable