Release workflow 4: drop SVN release-area writes, document manual dev -> release move#4650
Open
jbonofre wants to merge 2 commits into
Open
Release workflow 4: drop SVN release-area writes, document manual dev -> release move#4650jbonofre wants to merge 2 commits into
jbonofre wants to merge 2 commits into
Conversation
… → release move The credentials used by the release workflow do not have write access to the dist release SVN area, so the dev → release move, the helm index transfer, and the cleanup of superseded versions must be performed manually by a PMC member after the workflow completes. The remaining workflow steps (final tag, GitHub release, Docker push, Nexus release) now read artifacts from dist dev via `svn export`, leaving them in place for the manual move. * Remove the three steps that wrote to `release/polaris` (artifact `svn mv`, old-version `svn rm`, and helm index `svn mv`). * Switch the GitHub release and Python-client `svn export` sources from `release/polaris` to `dev/polaris`; non-destructive so the manual move remains possible. * Update the workflow summary, releasey README, and the release process flowchart to describe the new manual step. * Add a "Manual steps on dist.apache.org" subsection to the semi-automated release guide with the exact `svn` commands.
dimas-b
previously approved these changes
Jun 8, 2026
github-project-automation
Bot
moved this from PRs In Progress
to Ready to merge
in Basic Kanban Board
flyingImer
approved these changes
Jun 8, 2026
adnanhemani
reviewed
Jun 8, 2026
flyingImer
approved these changes
Jun 12, 2026
dimas-b
approved these changes
Jun 12, 2026
adutra
approved these changes
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The credentials used by the release workflow do not have write access to the dist release SVN area, so the dev → release move, the helm index transfer, and the cleanup of superseded versions must be performed manually by a PMC member after the workflow completes. The remaining workflow steps (final tag, GitHub release, Docker push, Nexus release) now read artifacts from dist dev via
svn export, leaving them in place for the manual move.release/polaris(artifactsvn mv, old-versionsvn rm, and helm indexsvn mv).svn exportsources fromrelease/polaristodev/polaris; non-destructive so the manual move remains possible.svncommands.Checklist
CHANGELOG.md(if needed)site/content/in-dev/unreleased(if needed)