Steps to create a minor release

1. Update recommended version numbers in README files via a pull request against main (i.e. Change existing latest supported minor version to new latest supported version that you are in the process of releasing.):
   • https://github.com/az-digital/az-quickstart-scaffolding/blob/main/README.md?plain=1#L17
   • https://github.com/az-digital/az-quickstart-scaffolding/blob/main/README.md?plain=1#L32

Possibly, just wait for the PR created in step 3.

2. Any pull requests against the main branch for az_quickstart, and az-quickstart-scaffolding, that should also be included in a release branch, are merged.

3. Run the Prepare repository for new minor release GitHub action on the main branch, with the new release branch name as the input. Example 2.8.x

4. Merge all automatically created Pull Requests.

5. Create initial release (e.g. 2.3.0-beta1, 2.3.0-rc1, 2.3.0).

6. Ensure GitHub branch protection rules are enabled for the new release branch (e.g. 2.3.x) for both the az-digital/az_quickstart and az-digital/az-quickstart-scaffolding repos.

7. In the az-digital/az-quickstart-pantheon repository, create a new branch for the next minor release (e.g. 2.9.0).

Note: this new branch serves several functions:

1. It allows the maintainers of the upstream to consolidate all non-essential additions.
2. It creates a target for our repository dispatch Github action to create pull requests against.
3. It streamlines the update process for site owners by enabling less frequent updates.