Contributing

Creating releases

If you are a maintainer of the repository and would like to tag a new release, follow these steps:

• Send a heads-up in the Slack (#rules_ios) channel or post an issue with plan to tag a new release
• Head over to Actions
• Find the Create release action
• Click on Trigger workflow
• Type in a version number, follow SemVer whenever possible.
• After a few minutes the release should show up in the Releases page.

Publishing new versions to the Bazel Central Registry

We automate publishing to the Bazel Central Registry with the Publish to BCR GitHub app.

It will create a PR like this one whenever a new release is created. As such, there is no extra action required from the maintainers. Simply create a release and let the app publish it to the BCR.

If you need more reviews in the BCR repository you can ask in the #bzlmod channel of the Bazel Slack.

Creating patches to older releases

If you need to create a new release for an older version, follow these steps:

• Create a new branch for the major version of the release you want to patch (e.g. to patch 3.x.x create a branch named v3)
• (Optional) If applicable in the current release, first create a pull request into main with your changes.
• Create a pull request into the branch you just created with the changes you want to include in the new release.
• Merge the pull request into the branch.
• Create a new release as described above, but set the source branch for the action as the branch you created.