Skip to content

fix: [DevOps] Fix release guide links #1214

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CharlesDuboisSAP merged 1 commit into from
Jul 3, 2026
Merged

fix: [DevOps] Fix release guide links #1214

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/how-to/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,10 +8,10 @@
When the workflow runs successfully, it will have created a `RELEASE-X.Y.Z` branch.
Additionally, the workflow will create a few PRs:

1. One to update our JavaDocs in [the Documentation Repository](https://github.com/sap/cloud-sdk)
2. Another one to update our release notes, also in [the Documentation Repository](https://github.com/sap/cloud-sdk)
1. One to update our JavaDocs in [the Documentation Repository](https://github.com/SAP/cloud-sdk/pulls)
2. Another one to update our release notes, also in [the Documentation Repository](https://github.com/SAP/cloud-sdk/pulls)
* **Note** As we are splitting our release notes every 15 minor versions, some manual adjustment might be needed to both `index.jsx` and `release-notes.mdx`
3. A third one for the actual changes in [the Code Repository](https://github.com/sap/cloud-sdk-java)
3. A third one for the actual changes in [the Code Repository](https://github.com/SAP/cloud-sdk-java/pulls)

Lastly, the workflow also creates a new draft release and an according tag.
All of these things will be linked in the Code PR, so that they can be found easily.
Expand All @@ -20,7 +20,7 @@ All of these things will be linked in the Code PR, so that they can be found eas

As the second to last step, you will trigger the [Perform Release Workflow](https://github.com/SAP/cloud-sdk-java/actions/workflows/perform-release.yml).

This workflow will take care of merging the PRs and creates a **staging release** in [Sonatype](https://oss.sonatype.org/).
This workflow will take care of merging the PRs and creates a **staging release** in [Sonatype](https://central.sonatype.com/publishing/deployments).
As the very last step, once the _Perform Release_ workflow has finished successfully, you need to log into _Sonatype_ and publish the staging release using the `Technical User for Releases` account.

That's it!
Expand Down