From 88c9f64749d5c09c2c1b8eb72dd6ea4b7827e15f Mon Sep 17 00:00:00 2001 From: Andy Mills Date: Mon, 7 Oct 2024 14:09:38 +0000 Subject: [PATCH] fix markdown spacing --- docs/community-and-contribution/release-process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/community-and-contribution/release-process.md b/docs/community-and-contribution/release-process.md index 0d89ed1d..c9da4204 100644 --- a/docs/community-and-contribution/release-process.md +++ b/docs/community-and-contribution/release-process.md @@ -20,7 +20,7 @@ The most important prefixes you should have in mind are: ### How can I influence the version number for a release? -PR titles should also follow this pattern and are linted using [commitlint](https://commitlint.js.org/). The PR title will determine the version bump. When a PR is merged (squashed) release-please will kick off a release PR. When that release PR is approved and merged, release-please will create a draft release. Once that draft release is published go-releaser with build and publish the assets,including creating a release in our Homebrew tap repository: [https://github.com/defenseunicorns/homebrew-tap](https://github.com/defenseunicorns/homebrew-tap) +PR titles should also follow this pattern and are linted using [commitlint](https://commitlint.js.org/). The PR title will determine the version bump. When a PR is merged (squashed) release-please will kick off a release PR. When that release PR is approved and merged, release-please will create a draft release. Once that draft release is published go-releaser with build and publish the assets, including creating a release in our Homebrew tap repository: [https://github.com/defenseunicorns/homebrew-tap](https://github.com/defenseunicorns/homebrew-tap) - Pre-v1.0.0 release-please is configured to bump minors on breaking changes and patches otherwise. per [release-please-config](https://github.com/defenseunicorns/lula/blob/main/release-please-config.json)