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
We will cut branch release-3.6 at a proper timing after we finish all remaining tasks planned for 3.6. But the release script should also have the ability to release alpha/beta (or RC) versions based on main branch directly.
Bug report criteria
What happened?
While working on using
gh
to automate creating the GitHub releases, I noticed that the release script failed when doing v3.6.0 prereleases.What did you expect to happen?
It should work but fails because it expects a branch
release-3.6
to exist.How can we reproduce it (as minimally and precisely as possible)?
Running the release script with a v3.6.0 version, i.e.:
Anything else we need to know?
No response
Etcd version (please run commands below)
N/A
Etcd configuration (command line flags or environment variables)
N/A
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
N/A
Relevant log output
No response
The text was updated successfully, but these errors were encountered: