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
I'm having trouble understanding how you would release a package after it has been published with the --prerelease-prefix option.
I would want all of my pre release changes inside my official release change log. For example, if I were to have several pre releases like 1.1.0-alpha.1 all the way to 1.1.0-alpha.5 and I went to do an official release I would want 1.1.0 to have all changes that the 5 alphas had. But the way beachball works is that is removes all changelogs when pre releasing... so when I go to do an official release, the publish command doesn't detect any changes and won't bump/publish my 1.1.0 version.
Is there something I'm missing here about expected workflow/design? Clarification/documentation on this would be very helpful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm having trouble understanding how you would release a package after it has been published with the
--prerelease-prefix
option.I would want all of my pre release changes inside my official release change log. For example, if I were to have several pre releases like 1.1.0-alpha.1 all the way to 1.1.0-alpha.5 and I went to do an official release I would want 1.1.0 to have all changes that the 5 alphas had. But the way beachball works is that is removes all changelogs when pre releasing... so when I go to do an official release, the
publish
command doesn't detect any changes and won't bump/publish my 1.1.0 version.Is there something I'm missing here about expected workflow/design? Clarification/documentation on this would be very helpful.
Beta Was this translation helpful? Give feedback.
All reactions