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

Allow releases to be marked as "pre-releases" in deploy_github #273

Open
alexjpwalker opened this issue Dec 16, 2020 · 0 comments
Open

Allow releases to be marked as "pre-releases" in deploy_github #273

alexjpwalker opened this issue Dec 16, 2020 · 0 comments

Comments

@alexjpwalker
Copy link
Member

Problem to Solve

Currently our pre-releases such as client-python 2.0.0-alpha are not marked as pre-release, meaning they show up as the default despite not being "production ready".

Current Workaround

We can manually retag the release.

Proposed Solution

Update deploy_github Bazel rule to allow pre-release to be specified manually, or perhaps even automatically detected from the version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant