Skip to content

Clarify release steps after sonatype migration #4442

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Clarify release steps after sonatype migration #4442

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
12 changes: 12 additions & 0 deletions RELEASES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,6 +60,18 @@ will also be packed on the tag.

In the end, don't forget to clarify the release notes on the GITHUB release.

### Publish the staging artifacts on Sonatype webconsole
Copy link
Contributor

@brendandburns brendandburns Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any way to automate this?


Login to the following website to browse all the releases under `io.kubernetes` namespace:

> https://central.sonatype.com/

Click into "Publish" -> "Deployments", you will see a list containg all the history releases
as well as the pending release waiting for you to confirm manually and publish. Click the
pending deployment the above github workflow created then click on "Publish" button, and then
the new release should be present in maven central in ~1 day.


## One time setup

You will need to have the following in place:
Expand Down
Loading