From a0ddfe97277e8fb71f31b8cbd029abd0e932c1e8 Mon Sep 17 00:00:00 2001
From: LowriJenkins <40766142+LowriJenkins@users.noreply.github.com>
Date: Thu, 1 Aug 2024 09:07:55 +0100
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 6247356..fade0f9 100644
--- a/README.md
+++ b/README.md
@@ -30,6 +30,6 @@ pyright
 
 ### Release Process
 
-Releases are created automatically via a github action, to create a release just create a new git tag on the commit on main (i.e. `git pull`, `git checkout main` `git tag <release.version.number.` `git push origin tag <release.version.number.`) This will start a workflow that will check that all linters and tests pass, and then publish a new release with the version number specified in the tag to [Pypi](https://pypi.org/project/ibex-bluesky-core/0.0.1/) and github. The new release can then be installed via `pip install ibex_bluesky_core`.
+Releases are created automatically via a github action, to create a release just create a new git tag on the commit on main (i.e. `git pull`, `git checkout main` `git tag <release.version.number.` `git push origin tag <release.version.number.`) This will start a workflow that will check that all linters and tests pass, and then publish a new release with the version number specified in the tag to [Pypi](https://pypi.org/project/ibex-bluesky-core/0.0.1/) and github. The new release can then be installed via `pip install ibex_bluesky_core`. The workflow must be approved by someone in the ICP-Write group.
 
 Credentials for Pypi can be found on keeper.