The release.yml
workflow implements and performs release procedures for the Eclipse Che Documentation, using the make-release.sh
script.
The publication is decoupled. See Publishing Eclipse Che documentation.
-
Docs being released as part of the Eclipse Che Release cycle must have all previous steps to be completed.
-
All pending issues/PRs that must be included before the release must be resolved/merged.
make-release.sh
script)-
From the
main
branch, open and merge a PR tomain
to update the Che version values inantora.yml
:TipYou can proceed to step 2 without waiting for this PR to be merged. -
Update the
prod-…
version values to the just released Che version:prod-ver-major: "7" # update this only if there is a major version change prod-ver-patch: "7.62.0" prod-ver: "7.62"
-
Add a commit message and PR title like
chore: update product version values in antora.yml to Che 7.62
and explain the changes:## What does this pull request change? Bump up the Che version to the latest release for the main branch. ## Specify the version of the product this pull request applies to Merge to `main`
-
-
From the
main
branch, create a release branch with a branch name in the format<major>.<minor>.x
.NoteThe name of the release branch differs from the number of the release in the trailing x
. -
In the
<major>.<minor>.x
branch, update the following product-version-related values inantora.yml
:prerelease: false version: <major>.<minor>.x # name of release branch asciidoc: attributes: prod-ver-patch: "<major>.<minor>.0" prod-ver: "<major>.<minor>" prod-ver-major: "<major>"
-
In the
publication-builder
branch, update the firstbranches
value to the latest release branch (from step 2) inpublication-builder-antora-playbook.yml
.content: sources: - url: https://github.com/eclipse-che/che-docs branches: - 7.62.x - che-7-redirections - main
WarningDo not remove the other branches like main
!