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.1 #762

Merged
merged 1 commit into from
May 19, 2022
Merged

v0.6.1 #762

merged 1 commit into from
May 19, 2022

Conversation

CagtayFabry
Copy link
Member

@CagtayFabry CagtayFabry commented May 19, 2022

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.rst 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
      (this website can be used to convert rST -> MD)
  • 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

@codecov
Copy link

codecov bot commented May 19, 2022

Codecov Report

Merging #762 (e59ed72) into master (95a23ff) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #762   +/-   ##
=======================================
  Coverage   96.83%   96.83%           
=======================================
  Files          88       88           
  Lines        6009     6009           
=======================================
  Hits         5819     5819           
  Misses        190      190           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 95a23ff...e59ed72. Read the comment docs.

@github-actions
Copy link

github-actions bot commented May 19, 2022

Unit Test Results

       1 files  ±0         1 suites  ±0   3m 8s ⏱️ +10s
2 152 tests ±0  2 152 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit e59ed72. ± Comparison against base commit 95a23ff.

♻️ This comment has been updated with latest results.

@CagtayFabry CagtayFabry merged commit 3e307fc into master May 19, 2022
@CagtayFabry CagtayFabry deleted the v0.6.1 branch May 19, 2022 09:46
@CagtayFabry CagtayFabry self-assigned this May 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants