How to tell what is causing the version range to be constricted? #2455
Unanswered
pat-son
asked this question in
Release workflow
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to make a maintenance release on a past version. It's current version is
v1.3
, and I'm trying to make av1.4
release. However, I get an error message saying "Based on the releases published on other branches, only versions within the range>=1.3.0 <1.4.0-beta.1
can be published". How can I tell what is causing1.4.0-beta.1
to be my upper bound?For some context, we did a beta release for 1.4, but then we had a breaking change and the version that ended up being released was version 2. Is the mismatch between the commits on
1.4.0-beta.1
and1.3.0
the source of the issue?Beta Was this translation helpful? Give feedback.
All reactions