feat: expose plans and masking on the client facade, bump to 0.9.0 - #27
Merged
Conversation
Version 0.8.1 -> 0.9.0. A minor bump rather than a patch: this adds surface, it does not fix anything. Also completes the previous commit, which had a real gap. Every other resource is reachable BOTH as `client.sets.get_sets()` and as `client.get_sets()`, but plans and masking policies were only wired as properties. Two consequences: they read differently from every other resource, and - the part that actually matters - `artifacts/autocomplete-types.ts` is generated from the facade, so they were invisible to the editor autocomplete that ships to users. The artifact went from 89 methods to 98 once the facade methods existed. The artifact is regenerated here rather than left to a follow-up push, which is the hygiene #25 established: it is committed so consumers can fetch it at a tagged ref, and a tag cut at the bump commit permanently carries whatever artifact was in the tree at that moment. 69 tests pass, 24 skipped. `ruff check --select F,E9` reports 7 findings across the package, identical to the count on main - all pre-existing, none from this change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Recovers work that was orphaned when #26 merged. That PR landed the
plansandmasking_policiesroute clients; this commit was pushed to the branch a few minutes after the merge, so it never reachedmain.Version 0.8.1 → 0.9.0
A minor bump rather than a patch: this adds surface, it does not fix anything.
It also completes #26, which had a real gap
Every other resource is reachable both ways -
client.sets.get_sets()andclient.get_sets()- but #26 wired plans and masking as properties only.Two consequences, and the second is the one that matters:
artifacts/autocomplete-types.tsis generated from the facade, so they were invisible to the editor autocomplete that ships to users. The artifact goes from 89 methods to 98 once the facade methods exist.So the resources were in the package but absent from the surface users actually discover them through.
The artifact is regenerated here, not in a follow-up push
That is the hygiene #25 established: the artifact is committed so consumers can fetch it at a tagged ref, and a tag cut at the version-bump commit permanently carries whatever artifact was in the tree at that moment. Leaving it to a follow-up is exactly how the v0.8.0 tag ended up carrying the 0.8.0 method set stamped 0.7.0.
Verification
ruff check --select F,E9reports 7 findings across the package, identical tomain- all pre-existing.After merge, 0.9.0 reaches PyPI via a GitHub release, and the runner's version floor needs bumping separately.