Skip to content

Commit

Permalink
Remove the trigger release, better to do this step manually
Browse files Browse the repository at this point in the history
  • Loading branch information
slinkydeveloper committed Oct 16, 2023
1 parent 3600f42 commit df21b95
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 30 deletions.
28 changes: 0 additions & 28 deletions .github/workflows/trigger-release.yml

This file was deleted.

14 changes: 12 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,8 +54,18 @@ Before releasing the documentation, update schemas and version of Restate artifa
* Automatically by executing the _Pre-release updates_ workflow.
* Manually, as described below.

Once the branch `main` is ready to be released, execute the _Trigger release_ workflow. This will merge `main` into `production` and add a tag.
The `tag` triggers the build of the new `restatedev/documentation:vX.Y.Z` container image and creates a draft [release on Github](https://github.com/restatedev/documentation/releases) that needs manual approval.
Once the branch `main` is ready to be released, merge `main` in `production` and push it, together with the release tag. E.g:

```shell
git checkout production
git merge origin/main
git tag v0.3.0
git push
git push --tags
```

Once pushed the update to the `production` branch, the website deployment will be updated.
The tag triggers the build of the new `restatedev/documentation:vX.Y.Z` container image and creates a draft [release on Github](https://github.com/restatedev/documentation/releases) that needs manual approval.

### Manually update the schemas

Expand Down

0 comments on commit df21b95

Please sign in to comment.