Repository navigation
docs: leave the package version to the release pull request - #49
Merged
Merged
Conversation
A fix does not edit the changelog or __version__.py. RELEASING.md is the procedure. The older pages point at it and drop the fix-branch version bump.
Say which steps are live, which packages this page covers, and how to pick a version Packagecloud has not already taken.
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
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.


Why
A changelog edit on
mainis what publishes a package today, so fix pull requests were taking a version with them. A fix should land with no version. The release pull request is the one that sets it.What changed
wlanpi/devorwlanpi/main.Scope
Contributor and maintainer docs in this repo. No CI change, no package version bump, and no edit to
REPOS.md. Draft pull request 48 is untouched. The dev stamp and the direct upload towlanpi/mainare written as not live yet.Tradeoffs
The page states both the upload that happens today and the planned upload. Writing only the future upload would tell a maintainer to skip a promote the workflow still performs.
Blast Radius
Docs only. A fix that follows the page does not publish until a release pull request. That gap is intended until the stamp CI lands.
Verification
dpkg1.22.6 sorts2.4.12-1below2.4.13~dev20261024.1842.1+gabcdef1, below2.4.13~rc1, below2.4.13. It also sorts2.5.0above2.4.14~dev20261024.1842.1+gabcdef1, and2.5.0~rc1below2.5.0~rc2.7.3.0-rc5-2712-wlanpi-2026090114sorts above7.3.0-2712-wlanpi-2026102509and below7.3.1-2712-wlanpi-2026102414.dch -v 2.4.13, thendch -aonce per subject, thendch -r "".v2.4.12, which exists. Tagv2.4.13does not.2.4.12-1, webui1.21.18-1, fpms1.4.25-1, profiler2.1.8-1, and mcp0.7.0-1.Note
Low Risk
Documentation-only changes to contributor and maintainer workflows; no CI or application code is modified.
Reviewed by Cursor Bugbot for commit 8b762cd. Bugbot is set up for automated code reviews on this repo. Configure here.