chore: Release 2026.08.10 - #120
Merged
Merged
Conversation
Bump the version to 2026.08.10, refresh uv.lock, and rev NEWS.md so the GraphQL deprecation migration lands under a dated heading. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
| Filename | Overview |
|---|---|
| NEWS.md | Archives the accumulated GraphQL migration notes under the August 10, 2026 release heading and resets the upcoming-release sections. |
| stacklet/client/platform/init.py | Updates the package version to 2026.08.10 for the planned release. |
Reviews (2): Last reviewed commit: "Merge branch 'main' into thumper/chore/r..." | Re-trigger Greptile
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
2 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.
what
Prepare the
2026.08.10release:__version__from2026.05.06to2026.08.10.NEWS.md: the GraphQL deprecation migration notes move under a dated## August 10, 2026heading, leaving a fresh emptyNext Releasescaffold.why
mainhas accumulated the deprecated-GraphQL-API migration (#118) but theversion on
mainis still2026.05.06— identical to the last publishedrelease. The release workflow publishes on tag push and uses
skip-existing: true, so tagging without a version bump would silently skipPyPI while still creating a GitHub release. The bump has to land first.
Once merged, the release is triggered by tagging the merge commit
2026.08.10and pushing the tag.
testing
just test— 90 passeduv run pre-commit run --all-files— all 14 hooks passVerified against the existing
uv.lockonmain, so the tagged commit'sdependency set is exactly what CI has been testing.
docs
NEWS.mdis updated as part of this change.🤖 Generated with Claude Code