chore: drop alpha warnings and stay on prerelease version - #8
Open
mishamilovidov wants to merge 2 commits into
Open
chore: drop alpha warnings and stay on prerelease version#8mishamilovidov wants to merge 2 commits into
mishamilovidov wants to merge 2 commits into
Conversation
Bumps the SDK to 1.0.0 and drops all alpha-specific guidance now that the API is stable for general availability. Removes the alpha status badge, warning block, and --pre install instructions from the docs so users can install the package normally. RUNNER-9680
mishamilovidov
force-pushed
the
RUNNER-9680-remove-alpha
branch
from
July 22, 2026 18:11
c2a8da5 to
d6fbace
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
mishamilovidov
marked this pull request as ready for review
July 22, 2026 20:50
MichaelGoberling
approved these changes
Jul 22, 2026
MichaelGoberling
left a comment
MichaelGoberling
left a comment
Collaborator
There was a problem hiding this comment.
Approved with the same naming Q as on the JS lib
asteed
approved these changes
Jul 22, 2026
wllbo
approved these changes
Jul 22, 2026
buskamuza
approved these changes
Jul 23, 2026
Contributor
Author
|
note: I have added the |
The team decided not to go GA yet, so this reverts the previous commit's bump to 1.0.0 and keeps the SDK on a PEP 440 prerelease version, 0.1.0a10, while still removing the user facing alpha warning badge and the now redundant --pre install flag from the docs. Every release of this package has been a prerelease, and pip already resolves the latest prerelease when no stable release exists to fall back to, so dropping --pre does not change install behavior or imply a stable release. Also fixes RELEASING.md so the example version bump command no longer instructs a future releaser to cut a 1.0.0 release. RUNNER-9680
mishamilovidov
changed the title
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.
Changes
0.1.0a9to0.1.0a10. This stays a PEP 440 prerelease, it is not a GA release.--prefrom the install snippet.--prefrom theRELEASING.mdinstall verification step and update the example version bump command.RELEASING.mdnote that claimedpip install aio-lib-sandboxwill not pick up the package without--pre.Why
The
--preflag was never actually required. pip only excludes prereleases when a stable release exists to fall back to, and every release of this package is a prerelease, so a plainpip install aio-lib-sandboxalready resolves the newest version. Verified with a dry run install, which selected0.1.0a9without--pre. The deletedRELEASING.mdnote was therefore factually incorrect and is removed on those grounds.Unlike npm, PyPI has no dist-tag concept, so there is no stale pointer to repair on this side. This change is docs and version only.
The package remains on a prerelease version string deliberately. The team has not decided to go GA, so this removes the user facing alpha noise without claiming API stability.
Related Issues