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

[FEAT]: Update _reusable-package-release.yml to allow creating prerelease versions #248

Open
nfelt14 opened this issue Nov 26, 2024 · 4 comments
Labels
enhancement New feature or request reusable-workflows

Comments

@nfelt14
Copy link
Collaborator

nfelt14 commented Nov 26, 2024

Description

It would be nice to be able to use this automation tool to create a prerelease version. It would need to create a prerelease version and upload it to pypi and testpypi as well as create a prerelease in GitHub. The testpypi upload workflow would also need to be updated to properly handle the postN versions that are uploaded (it may need to include the release candidate info in the custom version)

Additional Information

No response

@nfelt14 nfelt14 added the enhancement New feature or request label Nov 26, 2024
@nfelt14 nfelt14 self-assigned this Nov 26, 2024
@nfelt14
Copy link
Collaborator Author

nfelt14 commented Nov 26, 2024

@nfelt14
Copy link
Collaborator Author

nfelt14 commented Nov 26, 2024

Will also require updating to use https://python-semantic-release.readthedocs.io/en/stable/automatic-releases/github-actions.html#python-semantic-release-publish-action instead of https://github.com/python-semantic-release/upload-to-gh-release. This is just a simple replacement of the currently used action with the new, renamed action.

@nfelt14
Copy link
Collaborator Author

nfelt14 commented Nov 26, 2024

Relates to #141, #107, #91

@nfelt14
Copy link
Collaborator Author

nfelt14 commented Jan 4, 2025

Some more notes:

  • The reusable workflow may need to be updated to allow other branches besides main to run the workflow
    • Maybe something like a prerelease branch
  • Documentation will need to be added explaining that the first prerelease would need to be run with a specific version increment forced (e.g. release-level=major, but subsequent releases would just need release-level=prerelease

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request reusable-workflows
Projects
None yet
Development

No branches or pull requests

1 participant