Releasing

Versioning

This project follows semver.

Major and minor versions follow the versioning in the Echoes Design System. Patches may diverge.

For more details, refer to the internal versioning strategy (Sonar employees only)

Create a new branch for the release and maintenance following the name convention branch-x.y
Publish a new GitHub release targeting the release branch
- Tag version: x.y.z-build_number
  - find it in the repox-main Github check, where it says Latest promoted build of '0.13.0-2686' from branch 'main'
- Release title: @sonarsource/echoes-react - x.y.z
- Find the relevant Jira release from the releases page and after ensuring the correct tickets are in there, release it, generating release notes in Jira at the same time.
- Populate the Github release notes section (copied as markdown from Jira).
  - Example: https://github.com/SonarSource/echoes-react/releases/tag/v0.5.0
- click Publish Release
On the main branch, bump the package version for the next development iteration with yarn version major|minor and commit with message Prepare for version x.y.

Check out the version branch branch-x.y (create it if it doesn't exist yet)
Bump the package version with yarn version patch and commit with message Prepare for version x.y.z.
Cherry-pick the commits from the main branch that need to be in this patch release
Create a PR on the version branch with the changes
Create a new version in the Echoes Design System project like this one
Tag the relevant tickets with this new version
Once the PR is merged, follow the same procedure as for Major/Minor versions, skipping the version bump at the end