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
The release process currently considers any running release as the "latest". During the 0.33.4, it inherited the the "latest" tag away from the 0.34.3 release. Ideally, the highest version should keep the "latest" tag. It's probably worthwhile to have a way for the release manager to control whether any given release inherits "latest" or not. In this regard, it may be worthwhile to move from a release branch based workflow to a workflow_dispatch release workflow.
The text was updated successfully, but these errors were encountered:
The release process currently considers any running release as the "latest". During the
0.33.4
, it inherited the the "latest" tag away from the0.34.3
release. Ideally, the highest version should keep the "latest" tag. It's probably worthwhile to have a way for the release manager to control whether any given release inherits "latest" or not. In this regard, it may be worthwhile to move from a release branch based workflow to a workflow_dispatch release workflow.The text was updated successfully, but these errors were encountered: