Skip to content
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.9 #953

Merged
merged 2 commits into from
Nov 19, 2024
Merged

v0.6.9 #953

merged 2 commits into from
Nov 19, 2024

Conversation

CagtayFabry
Copy link
Member

@CagtayFabry CagtayFabry commented Nov 19, 2024

How to release

A short primer in the steps needed to release a new version of the weldx package

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 and change the GitHub PR links to GitHub markdown
  • wait for all Github Actions to finish

ReadTheDocs updates

  • 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

@CagtayFabry CagtayFabry self-assigned this Nov 19, 2024
@CagtayFabry CagtayFabry added dependencies changes in package dependencies no-changelog-entry-needed labels Nov 19, 2024
Copy link

codecov bot commented Nov 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.16%. Comparing base (5ad2929) to head (caf1642).
Report is 30 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #953      +/-   ##
==========================================
- Coverage   96.48%   96.16%   -0.33%     
==========================================
  Files          95       95              
  Lines        6293     6340      +47     
==========================================
+ Hits         6072     6097      +25     
- Misses        221      243      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

Copy link

github-actions bot commented Nov 19, 2024

Test Results

2 188 tests  ±0   2 187 ✅ ±0   1m 59s ⏱️ ±0s
    1 suites ±0       1 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit caf1642. ± Comparison against base commit 548d4c8.

♻️ This comment has been updated with latest results.

@CagtayFabry CagtayFabry merged commit c8457bf into BAMWelDX:master Nov 19, 2024
22 checks passed
@CagtayFabry CagtayFabry deleted the v0.6.9 branch November 19, 2024 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant