Skip to content

Commit ddebbf8

Browse files
committed
docs: clarification in MAINTENANCE.md
JIRA: TRIVIAL risk: low
1 parent 590b8fb commit ddebbf8

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

Diff for: MAINTENANCE.md

+4-5
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,16 @@
22

33
## How to release
44
* manually run [Bump version & trigger release](.github/workflows/bump-version.yaml) workflow
5-
* after the previous workflow finishes, dispatch the GitHub workflow `netlify-deploy` on the `master` branch (takes ~15 minutes)
6-
* The styling of the documentation is taken from the `master` branch. For more details see [./scripts/generate.sh](scripts/generate.sh) and [netlify-deploy](.github/workflows/netlify-deploy.yaml) workflow.
5+
* after the previous workflow finishes, dispatch the GitHub workflow [Netlify Deploy](.github/workflows/netlify-deploy.yaml) on the `master` branch (takes ~15 minutes)
6+
* The styling of the documentation is taken from the `master` branch. For more details see [generate.sh](scripts/generate.sh).
77
* after the previous workflow finishes, push tag
88
* the version should be the same as the one in [Bump version & trigger release](.github/workflows/bump-version.yaml) workflow log
99
* checkout latest master branch and tag it `vX.Y.Z`
1010
* push the tag to the gooddata/gooddata-python-sdk repository (e.g. `git push <remote> vX.Y.Z`)
1111

1212

13-
### Releasing Alpha versions
14-
To publish current master as an alpha version, use `Release master as alpha` github workflow where you need to specify
15-
desired alpha version. **No validity checks are performed**.
13+
### How-to dev release
14+
To publish current master as a dev release version, use [Dev release from master](.github/workflows/dev-release.yaml) GitHub workflow.
1615

1716
### Errors that may appear
1817

0 commit comments

Comments
 (0)