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

Prepare for release #229

Merged
merged 1 commit into from
Oct 11, 2024
Merged

Prepare for release #229

merged 1 commit into from
Oct 11, 2024

Conversation

CSSFrancis
Copy link
Member

@CSSFrancis CSSFrancis commented Oct 11, 2024

  • Update the version number in release_info.py.
  • Update the CHANGELOG.rst file with the date and new version number and a description of the changes.
  • Update the list of contributors in both the release_info.py and .zenodo.json files. __ Make sure that the Zenodo file is valid JSON __.
  • Commit the changes and push them to the repository.
  • Create a new tag with the “v” + version number (e.g. “v0.16.0”) and make a new release on GitHub.
  • Wait for the CI server to finish the release proces

@CSSFrancis
Copy link
Member Author

This should get us compatible with numpy 2.0.0. @hakonanes Let me know if there is anything else to be done otherwise I will make the release.

Copy link
Member

@hakonanes hakonanes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, go ahead and merge!

@CSSFrancis CSSFrancis merged commit f1d3761 into pyxem:main Oct 11, 2024
12 checks passed
@hakonanes
Copy link
Member

Regarding your points in the top comment:

  • List of contributors: should be the same as for the previous release, v0.6.0
  • The tag is created from an annotated release. Can you make one in the similar vein as before?

@hakonanes hakonanes added the dev label Oct 11, 2024
@hakonanes hakonanes added this to the v0.6.1 milestone Oct 11, 2024
@CSSFrancis
Copy link
Member Author

  • The tag is created from an annotated release. Can you make one in the similar vein as before?

@hakonanes I just have to make a release with a new v0.6.1 tag correct. You have me second guessing myself :)

@hakonanes
Copy link
Member

Sorry about that! I read your comment as suggesting to create one locally and push it, which we don't do.

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.

2 participants