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 we run the release pipeline, it pushes up the tags to github, but the commits that increase the version number in the package.json file are not part of the main branch. Cherry-picking them won't change the link of the tags.
I imagine what we would need to do in the release pipeline is to open a branch, where the pipeline can commit and push it up, and then open a PR to the main branch that we can merge automatically.
The text was updated successfully, but these errors were encountered:
When we run the release pipeline, it pushes up the tags to github, but the commits that increase the version number in the package.json file are not part of the main branch. Cherry-picking them won't change the link of the tags.
I imagine what we would need to do in the release pipeline is to open a branch, where the pipeline can commit and push it up, and then open a PR to the main branch that we can merge automatically.
The text was updated successfully, but these errors were encountered: