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
Hey
I thinking about migrating to uplift, this looks very cool 🚀
I've used Semmantic Release in the past, but unfortunately it is very slow, due to the nature of node package restoration.
We've used a flow where we have a develop and a main branch. The commits merged into the develop branch generates beta releases like v1.0.3-beta.2.
After testing the develop branch is merged into the main branch which then generates the appropriate v1.0.3 release.
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hey
I thinking about migrating to uplift, this looks very cool 🚀
I've used Semmantic Release in the past, but unfortunately it is very slow, due to the nature of node package restoration.
We've used a flow where we have a develop and a main branch. The commits merged into the develop branch generates beta releases like v1.0.3-beta.2.
After testing the develop branch is merged into the main branch which then generates the appropriate v1.0.3 release.
See Publishing pre-releases for more information.
Is it somehow possible to configure such a scenario with uplift?
All reactions