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

Changlog and GitHub releases #225

Closed
MuellerSeb opened this issue Jul 24, 2019 · 4 comments
Closed

Changlog and GitHub releases #225

MuellerSeb opened this issue Jul 24, 2019 · 4 comments

Comments

@MuellerSeb
Copy link
Contributor

Hey there,

just a hint from my side. It would be nice, if the PyPI releases would be triggered by GitHub releases. Sometimes things break due to backward incompatibility and it would be nice to see if there was a new release here and what are the changes.

Since you apparently got a CI via travis this would mean almost no work.

Have a look at a setup of one of my packages:
https://github.com/GeoStat-Framework/ogs5py/blob/master/.travis.yml

It will create wheels with all commits and send them to test.pypi. On a GitHub-tag it will send them to PyPI. The setup uses the package cibuildwheel.

Also you could easily integrate Zenodo, to get a DOI for each GitHub release. It would be nice to be able to cite a certain version of the code.

Keep up the good work!
Sebastian

@MuellerSeb
Copy link
Contributor Author

Oh I forgot the anniversary of this issue! ;-)

This is still important in my opinion, since we don't have a chance as users to track what changes were made at which point in the git-history.

@MuellerSeb
Copy link
Contributor Author

Now, only the Changelog is missing ;-)

@thouska
Copy link
Owner

thouska commented Sep 9, 2020

Sorry for taking so long to work on this issue. You are right, it was indeed an important one! Thanks for the hint!
I included

  • Pypi releases based on Travis
  • Zenodo DOI (will be automatically generated with next release)
  • Changelog.md (so far manually written, conventional-changelog/standard-version might be suitable to do this automatically in the future

@thouska
Copy link
Owner

thouska commented Apr 13, 2021

Ok cool, this seems to work now. Thanks again for your hint :)

@thouska thouska closed this as completed Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants