build(deps): bump black from 25.9.0 to 26.3.1 - #22
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [black](https://github.com/psf/black) from 25.9.0 to 26.3.1. - [Release notes](https://github.com/psf/black/releases) - [Changelog](https://github.com/psf/black/blob/main/CHANGES.md) - [Commits](psf/black@25.9.0...26.3.1) --- updated-dependencies: - dependency-name: black dependency-version: 26.3.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/pip/black-26.3.1
branch
from
July 25, 2026 12:50
d233cab to
323cf0b
Compare
ourway
added a commit
that referenced
this pull request
Jul 31, 2026
…sserts both directions (issuedb #22) Found while releasing 3.0.1: `make publish` aborted because the pre-publish smoke test failed at add_membership. Confirmed NOT a 3.0.1 regression — the released 3.0.0 wheel reproduces it identically. Reproduced against the LIVE service, exactly as the README instructed a new user to proceed: POST /api/role/engineers -> 200 POST /api/permission/engineers/deploy -> 200 POST /api/membership/alice/engineers -> 409 user_not_key_backed The 409 is CORRECT and stays: strict user identity is the default for namespaces created after 3.0.0 (SPEC 0008/0012), and this is the refusal shape runflow asked for in 2.5.1. The defect is that the documented onboarding path predates the flip and never taught the step that satisfies it, so every brand-new user hit a wall on step 3 while grandfathering kept all 181 existing tenants working. This is the consumer-facing instance of the hazard runflow described on thr-00ea026de72c4dcab1d9 — a fresh namespace is strict from birth and RBAC is dead on arrival. They found it in their environment-rebuild path; the same blind spot was in our own front door. Both supported paths are now documented in README.md and in all three quickstart blocks of auth/docs_page.py (landing /, /claude, Python client section): 1. key-first (default): POST /api/apikeys/user/<user> before the grant; the returned secret need not be kept if only the identity must exist 2. opt-out: PUT /api/settings {"strict_users": false}, once per namespace, for consumers whose users can never hold auth keys Each block says why the step exists and that the 409 is permanent, not a transport fault, so retries never help. scripts/smoke_install.sh now mirrors the documented sequence and asserts BOTH directions: the keyless grant must be refused, then key issuance must release exactly that block. A quickstart that cannot succeed now fails the release — which is what would have caught this before 3.0.0 shipped. Endpoint shapes were verified against the SERVED API before being written down, not read off the source. That caught a real error in the first draft: /api/settings is PUT, not POST. Live confirmation on fresh namespaces — key-first path 200/200/200/200/true, and opt-out path 200 then role/permission/membership/has_permission all 200 with no key ever issued. ruff, mypy, 214 unit tests green; smoke passes on the built 3.0.1 wheel. Co-Authored-By: Claude Opus 5 (1M context) <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.
Bumps black from 25.9.0 to 26.3.1.
Release notes
Sourced from black's releases.
... (truncated)
Changelog
Sourced from black's changelog.
... (truncated)
Commits
c6755bbPrepare release 26.3.1 (#5046)69973fdHarden blackd browser-facing request handling (#5039)4937fe6Fix some shenanigans with the cache file and IPython (#5038)2e641d1docs: remove outdated Black Playground references (#5044)c014b22Remove unused internal code (#5041)0dae20bAdd new changelog (#5036)c5c1cbdMinor release patches (#5035)7e5a828docs: clarify relationship between Black style and PEP 8 (#5025)69705dedocs: add clearer pyproject configuration guidance (#5026)35ea679Prepare release 26.3.0 (#5032)