From 584c8742cce87a457c17c0cdbde3709d1eb1f023 Mon Sep 17 00:00:00 2001 From: TC Date: Fri, 25 Oct 2024 00:22:17 +0000 Subject: [PATCH] Update RELEASING.md [ci skip] --- RELEASING.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index abe003f3..65726729 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -20,7 +20,7 @@ Releases happen via a CI/CD pipeline. The release process flows as follows: 2.1 Update your local copy of `main` to mirror the newly merged upstream `main` - 2.2 Ensure the [CHANGELOG](./CHANGELOG.md) is updated. + 2.2 Ensure the [CHANGELOG](./CHANGELOG.md) is updated and committed. 2.3 Activate your bumpversion Python venv (see bumpversion setup section for details) @@ -32,11 +32,9 @@ Releases happen via a CI/CD pipeline. The release process flows as follows: 2.7 Create the Git tag `git tag v{new_version}` - 2.8 Push your local 'main' to the upstream origin 'main' `git push` + 2.8 Push your local the tagged code to trigger the release pipeline `git push -o ci.skip && git push --tags` - 2.9 Push the new tag to the upstream origin `git push origin {tag name made in step 2.7}` i.e. `git push origin v0.1.5` - - 2.10 Ensure the package/release/distribute pipeline autostarted in the Gitlab UI + 2.9 Ensure the package/release/distribute pipeline autostarted in the Gitlab UI Git tags serve as a historical record of what repo versions were successfully released at which version numbers.