docs(readme): update readme with new release information

Author: OliverDudgeon

README.md

@@ -110,25 +110,7 @@ committing it as a image.
 
 ## Releases
 
-This project uses [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). This standardises commits so they can be used to generate changelogs. Use [standard-version](https://github.com/conventional-changelog/standard-version) to do a release (ensure you have no un-committed changes, I.e. a clean workspace).
-
-- **Pre-release**:
-
-A prerelease will update the version in the package.json to an appropriate semver version (based on whether the changes since the last tag are fixes, features and whether they contain breaking changes). In this case the `rc` tag is used in the semver string to mark it as a pre-release. It will then update the [CHANGELOG.md](CHANGELOG.md) file with the relevant changes since the last changelog update. These two changes are then committed with a standardised commit message. At this point, a tag is created with the same version number as the version field of the package.json. The second command then pushes both the new commit as well as the new tag.
-
-```bash
-pnpm dlx standard-version --prerelease rc -t "''" --skip.changelog=true
-git push --follow-tags origin master
-```
-
-- **Release**
-
-This causes the same as above but as a normal release. I.e. no `rc` tag.
-
-```bash
-pnpm dlx standard-version -t "''"
-git push --follow-tags origin master
-```
+This project uses [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). This standardises commits so they can be used to generate changelogs. Release PRs will be created by [Release Please](https://github.com/googleapis/release-please) based on the changes since the last release.
 
 ## Devcontainers