[GH-ISSUE #3130] [RFC]: Release Branch Workflow for Stable Releases #801

New issue

Open

opened 2026-10-29 21:19:41 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-29 21:19:41 +00:00

Owner

Originally created by @ykwd on GitHub (Jul 27, 2026).
Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/3130

Changes proposed

Motivation

Our last release exposed several issues during the release process. We spent significant time resolving release-related problems, and after publishing the release, we discovered that the generated wheel package was broken, requiring an immediate post1 release.

To reduce release risk and improve reproducibility, I propose the following release workflow.

Proposal

For each release:

Create a dedicated release branch from main.
Treat the release branch as frozen. Only merge PRs that fix critical release-blocking bugs.
Trigger the release workflow to publish artifacts (especially wheels) to the PyPI Test Repository.
Verify that the generated packages can be installed and function correctly.
Once the artifacts are validated, publish the same release to the official PyPI repository.

Benefits

Provides a stable target for release validation.
Prevents unrelated changes from entering a release while validation is in progress.
Allows verification of the actual wheel artifacts before publishing to users.
Reduces the likelihood of emergency post releases caused by packaging or release pipeline issues.

Before submitting a new issue...

Make sure you already searched for relevant issues and read the documentation

Originally created by @ykwd on GitHub (Jul 27, 2026). Original GitHub issue: https://github.com/kvcache-ai/Mooncake/issues/3130 ### Changes proposed ## Motivation Our last release exposed several issues during the release process. We spent significant time resolving release-related problems, and after publishing the release, we discovered that the generated wheel package was broken, requiring an immediate `post1` release. To reduce release risk and improve reproducibility, I propose the following release workflow. ## Proposal For each release: 1. Create a dedicated `release` branch from `main`. 2. Treat the release branch as frozen. Only merge PRs that fix **critical release-blocking bugs**. 3. Trigger the release workflow to publish artifacts (especially wheels) to the **PyPI Test Repository**. 4. Verify that the generated packages can be installed and function correctly. 5. Once the artifacts are validated, publish the same release to the official PyPI repository. ## Benefits * Provides a stable target for release validation. * Prevents unrelated changes from entering a release while validation is in progress. * Allows verification of the actual wheel artifacts before publishing to users. * Reduces the likelihood of emergency post releases caused by packaging or release pipeline issues. ### Before submitting a new issue... - [ ] Make sure you already searched for relevant issues and read the [documentation](https://kvcache-ai.github.io/Mooncake/)

bsakaguchi added the

RFC

stale

labels

2026-10-29 21:19:41 +00:00

bsakaguchi commented

2026-10-29 21:19:41 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 27, 2026):

Thanks for opening this issue, @ykwd!

Field	Value
Issue	#3130
GitHub user ID	`11404354`
Reporter	@ykwd

A maintainer will triage this when possible. To help us respond faster, please include:

Mooncake version or commit SHA
Environment (OS, CUDA/driver, RDMA stack if relevant)
Steps to reproduce and expected vs. actual behavior

Useful links: Documentation · Contributing guide

This message was posted automatically by the issue bot.

@github-actions[bot] commented on GitHub (Jul 27, 2026): Thanks for opening this issue, @ykwd! | Field | Value | |-------|-------| | **Issue** | #3130 | | **GitHub user ID** | `11404354` | | **Reporter** | @ykwd | A maintainer will triage this when possible. To help us respond faster, please include: - Mooncake version or commit SHA - Environment (OS, CUDA/driver, RDMA stack if relevant) - Steps to reproduce and expected vs. actual behavior Useful links: [Documentation](https://kvcache-ai.github.io/Mooncake/) · [Contributing guide](https://github.com/kvcache-ai/Mooncake/blob/main/CONTRIBUTING.md) > This message was posted automatically by the issue bot.

bsakaguchi commented

2026-10-29 21:19:42 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 26, 2026):

This issue has had no activity for 90 days and will be closed in 7 days if there is no further activity. Please comment or react if it should stay open.

@github-actions[bot] commented on GitHub (Oct 26, 2026): This issue has had no activity for 90 days and will be closed in 7 days if there is no further activity. Please comment or react if it should stay open.

bsakaguchi referenced this issue

2026-10-29 21:30:42 +00:00

[PR #801] [MERGED] [CI] Fix Release build_wheel.sh to make python 3.8 auditwheel happy #1831