This repository uses 🦋 Changesets to manage releases.
- To create a release from your PR, switch to your feature branch, and execute the following command from the identity-apps root.
🗒️ Note:
Changeset identifies the changed packages by comparing your feature branch with the
master
branch. If these branches are not properly synced with remote, you'll some irrelevant packages listed under changed packages. Therefore, it is recommended to rebase your feature branch on the up-to-datemaster
branch before executingpnpm changeset
.
# from the root of the project
pnpm changeset
- This will open a prompt to select the packages that have changed. Select the changed packages, and press Enter.
- Then, it will open a prompt to select the type of change. Select the type of change and press
Enter
.
- MAJOR version when you make incompatible API changes
- MINOR version when you add functionality in a backward compatible manner
- PATCH version when you make backward compatible bug fixes
- Lastly, it will open a prompt to enter a summary of the changes. Enter a summary and press
Enter
. (Additionally, if you want to have an editor view to enter a long summary with line breaks, pressEnter
without typing anything.)
🗒️ Note
Please enter a meaningful summary of the changes. This will be used in the changelog.
- Then commit the generated changeset file with the following commit message.
Add changeset 🦋
- After your PR is merged, Changesets Github Action will version the packages that have changed and create a PR with the version bump. You can find the PR in the pull requests tab.
💡 Sample PR title: [Release] [GitHub Action] Update package versions.
-
Approve and merge the PR.
⚠️ WarningDo not choose
squash and merge
option to merge the version bump PR.
- That's it! A release build will be automatically triggered after the version bump PR is merged. The changed apps and package artifacts will be released to GitHub and Nexus.