Settled to use independent mode to projects to increment package versions independently.
Lerna allows target versions of local dependent packages to be written as a git remote url, this allows packages to be distributed via git repositories
Version track starts from v1.0.0 at main branch.
npm run bootstrapnpm run buildnpm run devfor running local dev server
To add dependency to all packages.
$ lerna add @konturio/module3To add module3 as dependency to module2.
$ lerna add @konturio/module3 --scope=@konturio/module2For every feature you must create new branch in format
{fibery-task-id}-{tas-title}
Currently correct branch name generated in fibery
To build automation on top of lerna and packages version management we have to follow Conventional commits specification.
Commit message format:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
Must be one of the following:
- build: Changes that affect the build system or external dependencies (example scopes: webpack, babel, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: .env, Docker, Ansible, configs)
- docs: Documentation only changes
- feat: A new feature
- fix: A bug fix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- test: Adding missing tests or correcting existing tests
After you have finished working with the branch:
-
Push and publish it into the git:
git push --set-upstream origin <branch_name> -
Open Merge Request (MR) into dev
- Select
Delete source branch - Select
Squash commits - Write changelog in description of MR (it will be added in change log of all modules that depend on your MR)
-
Make sure that all CI pipelines passed successfully and reviewer was assigned
-
Make sure that all issues identified in the review process closed, and request have at least one :like: (not yours). If CI/CD pipeline without errors - accept MR.
If you need release modules in NPM nexus repo, you need some extra steps:
- Clone fresh
mainbranch with merged request npm run release6.1 for Windows OS: powershell terminal may not let you log in and push new versions. Try using git bash terminal- Wait until pipeline task 'release' was success
- Rebuild the app where you want to use the new modules
is something wrong in CI as workaround you can run
npm run publishmanually
If you need to release major version of module:
- Create new branch from the current
vNbranch, whereNis the current major version - Change the version num from
vNtovN+1inleran.jsonand.github/workflows/deploy.ymlfiles - Push the branch
- Run
npm run release