You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 versionThe text was updated successfully, but these errors were encountered: