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
We have multiple react apps in a Nx Workspace which depend on multiple libs some libs are only app specific like features, state. And some are shared between app like auth, utils, common-ui.
Now our development workflow is
Develop branch to merge all the newly created features/hotfix/chore/fix. (Unstable version of your code). Whenever changes are merged, bump the version, create a changelog for the app we are releasing.
We create a release branch once features are completed from the developer. release/app-a/1.2.3. And deploy the code on QA.
Once the QA sings off and everything seems to be working fine, Now this release branch gets deployed on UAT and eventually promoted to the prod if everything went well on UAT too. If not you create hotfix branches fix things and merge to develop follow the step 2 onwards.
Now if I want to use semver to automatically update the version and create a changelog for our apps if something changes in dependent libs how should I set up this plugin in my workspace? How can I create releases from incremental release branches? I'm open to amend my current workflow but I should be able to isolate release from the develop branch so that we can promote features after QA sings off.
Can I create a release branch automatically as a --postTarget in step 2 for eg if tag is app-a-1.2.0.Then the release branch will be release/app-a/1.2.0?
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
-
We have multiple react apps in a Nx Workspace which depend on multiple libs some libs are only app specific like features, state. And some are shared between app like auth, utils, common-ui.
Now our development workflow is
Develop branch to merge all the newly created features/hotfix/chore/fix. (Unstable version of your code). Whenever changes are merged, bump the version, create a changelog for the app we are releasing.
We create a release branch once features are completed from the developer. release/app-a/1.2.3. And deploy the code on QA.
Once the QA sings off and everything seems to be working fine, Now this release branch gets deployed on UAT and eventually promoted to the prod if everything went well on UAT too. If not you create hotfix branches fix things and merge to develop follow the step 2 onwards.
Now if I want to use semver to automatically update the version and create a changelog for our apps if something changes in dependent libs how should I set up this plugin in my workspace? How can I create releases from incremental release branches? I'm open to amend my current workflow but I should be able to isolate release from the develop branch so that we can promote features after QA sings off.
Can I create a release branch automatically as a --postTarget in step 2 for eg if tag is app-a-1.2.0.Then the release branch will be release/app-a/1.2.0?
Beta Was this translation helpful? Give feedback.
All reactions