v0.6.3

[CagtayFabry]

Changes

prepare v0.6.3 release

Checks

• updated CHANGELOG.md
• updated doc/
• update manifest file

create release PR

• create a PR that finalizes the code for the next version
  • name the PR according to the version vX.Y.Z and add the release
    tag (example here)
  • make sure CHANGELOG.md is up-to-date and enter current date to the release version
  • add summarized release highlights where appropriate
  • update the CITATION.cff version number and date
  • search the project for deprecated and remove deprecated code
• wait for review and the CI jobs to finish
• check the readthedocs PR build

Merge the Pull Request

• merge normally and wait for all CI actions to finish on the main branch

add Git(hub) tag

• tag and release the current master version on GitHub using the Releases feature
  • name the release git tag according to the version released (e.g. v0.3.3)
  • name the GitHub release accordingly, omitting the v prefix (this can be change later so don't worry, in
    doubt use vX.Y.Z everywhere)
  • copy the changes/release notes of the current version into the description
• wait for all Github Actions to finish

ReadTheDocs update

• check the build processes for latest, stable and vX.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

• check the automatic release to pypi after the build action completes here

conda-forge release

• pypi release should get picked up by the conda-forge bot and create the new
  pull-request here
• carefully check the meta.yaml in the pull request, manually update all changes in the build and run dependencies
• merge with 2 or more approved reviews

[github-actions]

Test Results

2 187 tests  ±0   2 186 ✔️ ±0   2m 35s ⏱️ -34s
       1 suites ±0          1 💤 ±0 
       1 files   ±0          0 ❌ ±0 

Results for commit e700520. ± Comparison against base commit c04bfda.

♻️ This comment has been updated with latest results.

[codecov]

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%)	⬆️
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]

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]

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