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
When a package is in a prerelease version, there doesn't seem to be a way to "promote" the package to stable with beachball. I could manually edit the package file and logs, of course, but it would be nicer to make the change with beachball! 😄
When a package is in a prerelease version, there doesn't seem to be a way to "promote" the package to stable with beachball. I could manually edit the package file and logs, of course, but it would be nicer to make the change with beachball! 😄
Related discussion
For inspiration, here's how changesets does prereleases.
Example
Expected behavior
When I run
beachball bump
, I expect to see@myorg/myinput
2.0.0 (or perhaps@myorg/myinput
3.0.0).Actual behavior
When I run
beachball bump
, I see@myorg/myinput
2.0.0-rc.1.Alternate approach
Perhaps there could be a
beachball exit-prerelease
command that would remove the-rc
suffix and publish@myorg/myinput
2.0.0.The text was updated successfully, but these errors were encountered: