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
Recently, we tried to use changelog to generate a point release. At the time, v0.87.0 was the most recent release. We wanted to make a release the v0.83.x series, the result being v0.83.1. changelog nextver was returning v0.88.0 as the next version. Upon further investigation, it's because the cherry-picked change to v0.83.x was a feat change, so changelog was rightfully trying to say "This can't be a point release." However, it's still incorrect, because v0.88.0 would end up missing changes that were added between v0.83.0 and v0.87.0, so that release would be wrong.
DOD:
When running changelog nextver for a point release, an error should be returned if a non-fix oriented change is detected.
The text was updated successfully, but these errors were encountered:
Recently, we tried to use changelog to generate a point release. At the time,
v0.87.0
was the most recent release. We wanted to make a release thev0.83.x
series, the result beingv0.83.1
.changelog nextver
was returningv0.88.0
as the next version. Upon further investigation, it's because the cherry-picked change tov0.83.x
was afeat
change, sochangelog
was rightfully trying to say "This can't be a point release." However, it's still incorrect, becausev0.88.0
would end up missing changes that were added betweenv0.83.0
andv0.87.0
, so that release would be wrong.DOD:
changelog nextver
for a point release, an error should be returned if a non-fix
oriented change is detected.The text was updated successfully, but these errors were encountered: