chore: bump version to 1.0.5 - #184
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
yzld2002
approved these changes
Aug 7, 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
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.
Bumps
pyproject.tomlanduv.lockto 1.0.5 (minimal two-line diff; the lockfile edit is validated byuv sync --locked, full suite green,ade versionreports 1.0.5).Merge #183 first, then this PR — v1.0.5 is intended to include:
x-org-id(ADR-0009)Once #183 is in, cut the release via Actions → Release → "Run workflow" on
main. The pipeline runs the live integration suite (macOS + Windows, against production) before taggingv1.0.5.Release note candidate
Browser (OAuth) sign-in now acts in a chosen organization: a single membership is selected automatically, several prompt at login (or take
--org), andade auth org list/ade auth org switchmanage the selection afterwards without a re-login. Requests — and credits — go to the selected organization. API-key logins are unaffected; a key already acts in the organization it was created in.🤖 Generated with Claude Code