Repository navigation
Apply One Identity to the Python developer portal - #286
Conversation
|
Current head The replacement is the single shared no-APT installed-Chrome path, not execution of the provider's raw writable Cloud owns the generic complete private non-writable-tree/closed-loader successor. CLI confirmed there is no accepted central helper yet and owns its eventual single public-safe adoption under central #295 after that source is frozen/reviewed. Both owners were asked directly for the exact reuse interface; General has the concrete failed run. Python will adopt that accepted source, retain all current product checks, and run fresh exact-head qualification. No separate custody implementation, raw-path execution, installer or fallback is being introduced here. The prior local Chrome checks do not replace this required hosted result. The independent Sonar correction removes unnecessary editable SDK installation from source-preview documentation. An import-denial control confirms strict source documentation builds without importing SDK runtime code; stable still installs and byte-checks its exact published wheel. This small source delta is prepared locally for the combined next qualification after the shared browser input is available. Fresh anonymous readback at23:22UTC: all five restored public portal byte identities still match, PyPI latest remains2.14.1 with wheel1b3bc645, the existing annotated tag peels to dc47958, and all five docs-writer status counts are zero. No source merge or protected deployment has occurred. Owner |
|
The prepared P0 source is now immutable commit The current stable-target build still binds SDK2.14.1@dc47958c, exact wheel1b3bc645 and all44 source bytes; no private/staging paths appear in rendered HTML/assets. The final two-view check at1440light/390dark passed card alignment, typography, fonts, theme, overflow and action contrast>=4.977:1. This follows the separately retained failed margin predecessor and the earlier8-view functional+8API+3 synthetic-status /8-view layout baselines. The owned browser/server/processes are independently absent. These local source checks do not replace the failed hosted result or qualify a browser publisher input. Next owners/actions: Cloud finishes the generic sealed-Chrome custody source disposition; CLI owns the single accepted public-safe helper/interface under central295, including Python-callable inspection/verification. Both owners were asked directly and confirmed no accepted helper is available yet. sdk-python then adopts the exact source, preserves every product check, pushes the normally refreshed PR pair, and completes current-head/main/artifact qualification before returning the distinct protected |
|
P0 delivery blocker has a confirmed owner and finite next step. CLI returned that Cloud owns the three remaining custody corrections on the existing finite browser prototype; the producer-only Cloud630 head Current saved Python presentation/source remains |
|
Cloud returned the exact browser correction checkpoint. The retained prototype is Cloud owns those corrections after its separately selected status freshness-parity source checkpoint, then returns one frozen generic blob/receipt-JSON handoff to CLI295. CLI owns the single public Python-callable inspect/verify/revalidate/cleanup interface; sdk-python owns the thin caller and fresh exact-head qualification. Both owners were asked directly and supplied this sequence. The separately merged producer-only77ce source is not the browser handoff or live status acceptance. Python's current source/native checks remain as recorded; current PR286's real APT/Sonar failures remain unqualified. No duplicate custody implementation, raw writable Chrome execution, installer/acquisition/fallback, publisher or additional full browser matrix was started. P0 remains open until the current-head hosted source checks, protected publication and actual live portal checks finish. |
|
Following General's source decision, the existing #286 is refreshed normally to 22ca11d / tree fa785db6f237e8de2f804be15456a961cf6c5667, including the prepared preview-SDK-install removal, current-main merge and concept-grid correction. The two browser commands now use The checker records package version, bundled headless revision/version, actual launched version and OS/architecture, requiring the launched version to match the bundle. The record accompanies the rendered screenshots; it is emitted only after actual launch. 38 focused selector/source-split/no-APT controls and Ruff pass locally. CLI was asked for exact no-APT applicability review. Actual changed-head hosted runs are in progress: Docs This ordinary source command supersedes the default wait for a custom browser helper for this P0. After current-head qualification and normal integration, sdk-python owns actual-main preview/deploy-skipped and stable preservation, then returns the exact protected |
|
Central #295 applicability review of exact The central fixed-APT prerequisite no longer applies to these two changed commands. This source applicability finding does not qualify a browser subject or publication. Python owns its actual fresh runner/browser result; the previous guard refusal remains historical evidence. This does not adopt the held sealed-copy prototype or qualify the separate PHP #297 profile. |
|
|
The actual bundled-browser path passed on this repository's own hosted runner at 22ca11d, Docs run 42141331142 / attempt1. Runner: Ubuntu26.04.1, image20261101.186.1, Linux x86_64. Locked Playwright1.64.1 downloaded and launched Chromium156.0.8078.4 / revision1248 without APT/system-library installation or a fallback. All eight landing and eight API/theme/functional views passed, including full-program copy, keyboard/drawer/search, fonts, contrast and overflow checks. Cross-references passed15 generated API pages and analytics passed24 pages. CLI's exact no-APT applicability return is separate from this actual launch proof. Review artifact 13466873294, ZIP SHA256 f76774cd1d41df2c0e0512ec8208eef5d3b6f7558d1c6ade12b3554e147d0a75, contains eight screenshots plus browser evidence, deployment audit and API inventory. The downloaded ZIP digest and all11 safe members were checked. Audit binds source-preview merge c33ba88, parents Whole-head22ca qualification remains NONPASSING because two Sonar S8544 findings remain at the version-pinned pip requirements installs. The existing PR now carries the narrow correction at 32b2a62 / tree b438bca7d2a11e29f00f56fb6ba8b763b2df6eac: all42 already-selected Linux/Python3.12 wheel filenames/hashes were verified against official versioned PyPI metadata, with unchanged package versions and zero archive retrieval in that metadata step; both installs now enforce The source still uses the selected bundled browser. The writable installed-Chrome proposal and #184 stops remain untouched. No publisher/deployment is selected; the exact protected stable packet follows normal source/main acceptance. |
|
Exact head 32b2a62 / tree b438bca7d2a11e29f00f56fb6ba8b763b2df6eac / base6e903713 is CLEAN,21/21 checks SUCCESS. Normal CI42142014037, including required Target branch qualification and actual SDK integration, is terminal success. Docs42142014195 and Sonar42142013845 succeed; direct Sonar PR inventory has0 open findings and quality gateOK. No earlier failure/cancellation was carried forward. Current Docs artifact13467749575 has ZIP SHA256 An exact-head local stable build also passes strict MkDocs under SDK-import denial,15 API cross-references and24 analytics pages. Audit binds docs32b2 to published SDK2.14.1@dc479, wheel1b3bc645 and all44-file inventoryc83125; all published example fences/support metadata remain checked. Five current public stable byte comparisons still equal the accepted2.14.1 site and latest PyPI remains2.14.1. Normal protected integration follows this source checkpoint. Main's automatic portal job remains preview-only/deploy-skipped, and package publishing requires a separate release tag or selected manual publisher. sdk-python owns actual-main acceptance/stable preservation/branch cleanup, then returns the concrete protected stable portal packet. No deployment is selected or dispatched by this source merge; Cloud's real status-feed/publication gate and #184 stops remain separate. |
|
Actual main d3e7297 / tree b438bca7d2a11e29f00f56fb6ba8b763b2df6eac is accepted. Ordered parents are All six original main workflows succeeded: CI42143059352, Docs42143059293, Sonar42143059347, Public Boundary42143059755, CodeQL42143058505 and dependency graph42143065055. All21 check runs are terminal:20 success and the expected deploy skipped. Main Docs again launched Playwright1.64.1 / bundledChromium156.0.8078.4/rev1248 and passed full portal assertions,15 API cross-reference pages and24 analytics pages with the canonical site token. The inspected main Pages artifact13469575226 has92 regular files, ZIP SHA256 The merged head and temporary WIP remote branches were deleted and independently verified absent; the local feature branch was removed and shared main fast-forwarded cleanly. A detached exact-main review checkout is retained for the pending publisher follow-through. The complete one-original protected stable publisher packet is returned to General for the distinct publication decision. No dispatch/deployment has occurred. #285 remains open for actual publication/live acceptance and the separately owned real status-feed prerequisite. #184's failed wheel and blocked review remain unchanged. |
The Python portal uses a different identity from the other Durable Workflow sites. This applies One Identity in the existing MkDocs components: canonical logo and self-hosted fonts, shared navigation and SDK switcher, light-default/dark-opt-in themes, Python install hero, four concept cards, readable complete greeter steps, runtime cards and shared footer/status consumer.
Stable documentation can now use current presentation without exposing unreleased SDK APIs. The protected workflow checks out its own exact revision for templates/tooling/presentation, and the explicitly selected published SDK tag separately for all SDK content, navigation and generated API. It installs the exact PyPI wheel with enforced SHA-256, compares all 44 SDK source files to that wheel, preserves every landing example fence, and checks the Python support floor. The deployment audit records both immutable revisions, wheel digest and API inventory digest. Main pushes remain source previews with deployment skipped.
For the current published target, SDK source is
2.14.1/dc47958c026b35167d2f90a33b96f7a575c48aee, Python >=3.10, wheel SHA-2561b3bc645cc167979849cc2d07bc5ee342ba486f84d1ad9fbc8592594ce83c285. Documentation wheel versions and SHA-256 bytes are locked for Linux amd64/Python3.12 inrequirements-docs.txt, and both installs enforce--require-hashes. Both browser paths download only that Playwright package’s bundled Chromium withpython -m playwright install chromium, without system-dependency installation or a fallback. The actual launched version must match the locked bundle and is retained with the screenshots. Existing protected Pages deployment, concurrency and canonical domain remain the publisher path.Validation: 38 local selector/separation/refusal/no-APT controls, 14 canonical status controls, strict stable MkDocs build, 15 generated API cross-reference pages and 24 analytics pages pass. Native Chrome checks passed eight landing views at 1440/1024/390/320 in both themes plus eight API views, complete program copying, SDK/theme/drawer/search keyboard controls, fonts and internal scrolling. Screenshot review corrected the concept grid and hero spacing; the affected eight-view follow-up passed with action contrast >=4.977:1. Prior failed copy/keyboard/contrast cells remain failed and separately attributed. Current-head required checks and uploaded screenshots remain authoritative for integration.
The footer consumes the shared public status contract, including expiry and truthful unknown fallback. Operational/stale/unknown browser fixtures are synthetic; real cross-origin feed acceptance remains Cloud-owned. No SDK release or #184 operating/review clearance is carried by this PR.
After normal source integration, the owner will verify actual-main preview/deploy-skipped behavior and stable preservation, then return the exact
main+stable_tag=2.14.1protected-dispatch packet before deployment. No deployment has been dispatched by this draft.Refs #285; shared identity and publisher source-split decision: durable-workflow/durable-workflow.github.io#483.