-
-
Notifications
You must be signed in to change notification settings - Fork 624
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
RFE: please start making github releases #2167
Comments
I don't intend to create manual releases, but I understand the need and I'm open to automatic releases (using GH actions, for instance). Can't look at it right now but if someone is willing to look at it, they are very welcome. |
https://github.com/elgohr/Github-Release-Action looks like a nice option if we are only concerned with mirroring the tags as releases. Some of the new release actions promoted by the old official action have options for automatically generating release notes. |
If you are publishing over pypi actions https://pgjones.dev/blog/trusted-plublishing-2023/ contains hint how to add gh release to such process. |
Did you script out these github issues? 😅 I don't really have a strong opinion on this, but I lean towards simplicity in our release pipeline. After all, GH releases are redundant with PyPI releases and git tags. For users who want to automatically get notified about new releases, I'd recommend using an automated dependency upgrade service like renovate or dependabot. Closing for now |
Is it possible next time on release new version make the github release to have entry on https://github.com/marshmallow-code/marshmallow/releases? 🤔
I'm asking because only on make gh release is spread notification about new release to those who have set watch->releases.
More about gh releases is possible to find on
https://pgjones.dev/blog/trusted-plublishing-2023/
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://github.com/marketplace/actions/github-release
The text was updated successfully, but these errors were encountered: