Then when automated process runs a release for appone, it:
uses @changesets/cli to compute what the next version should be: 0.2.3
renames the appone@next to appone@0.2.3
marks it as released.
So either rename a release (which i think might not be possible), or an action that lets us move all jira tickets in appone@next to a newly created version appone@0.2.3
Would be good to be able to use this workflow:
Then when automated process runs a release for
appone
, it:@changesets/cli
to compute what the next version should be:0.2.3
appone@next
toappone@0.2.3
So either rename a release (which i think might not be possible), or an action that lets us move all jira tickets in
appone@next
to a newly created versionappone@0.2.3