Repository navigation
Prepare Workflow 2.21 support and upgrade guidance after its published handoff #481
Description
Workflow 2.21.0 is published at exact source cb9420019476d400e1df329f063cfb1a3b86ab18 / tree 9bbfc171b8b6c1de71c2854df938e24643e0c421, with actual Release Verifier42363788484/a1 six SUCCESS jobs and independent final authority audit. The current embedded contract requires PHP ^8.2 and Laravel ^12.69.0 or ^13.30.0; Laravel13 requires PHP8.3. Published2.20.5 and historical stable-v1 support remain separate.
General is implementing the support/install/adoption follow-through in #489. English and all seven current locales are updated; only the embedded Workflow entry changes in the existing artifact resolver. The other seven artifact selections, Helm pairing, bare PHP SDK requirements and versioned1.x bytes are preserved. This does not qualify a new shared Server/SDK tuple. Normal docs CI, full build/links and actual-main/Pages/live verification remain required before closure.
This is the necessary docs follow-through for Workflow #1020, not another producer implementation or a new support-policy decision.
Owner: General while Docs is Off. Prepare the smallest existing-format support/install/upgrade guidance update and any existing localized/versioned counterparts. Recover the authoritative manifest, support-policy/removal records and actual release metadata from Workflow; do not infer the final published authority from a source PR alone. Coordinate the distinction between bare PHP SDK support and the embedded/service-mode framework bridge with SDK-PHP #239.
Acceptance:
- Reconcile every public embedded PHP/Laravel minimum/support statement affected by this contract, with exact source locations and a concise scoped patch.
- Preserve the current published 2.20.4 and stable-v1 guidance until the actual 2.21 manifest and Release Verification handoff exists. Use existing versioning/preview behavior; do not add a new feature-flag system or mislabel unreleased source as shipped support.
- Explain the upgrade/removed-support boundary clearly and preserve unaffected SDK/runtime requirements.
- Run ordinary relevant docs/contract checks, fix actual failures and inspect automatic Pages/live followers. A draft may qualify now; any merge that changes the live/current support floor must wait for the real producer handoff.
- After publication, own the final normal source integration, actual-main/Pages/artifact/live verification and exact branch cleanup. Record actual URLs/version/source and scope; no inferred installed/runtime proof.
Workflow owns the actual producer authority and can supply it in #1020. General coordinates the handoff; no extra per-PR Security review or operator action is imposed for ordinary docs source. No tag, package, live floor change, runtime, provider or image effect is selected by this issue. The existing CLI 2.5 handoff in #457 remains distinct.
Activity
rmcdaniel commentedon Nov 5, 2026
Docs owns this source preparation on isolated
docs/481-workflow-2.21-support, from accepted maine0a600a1. I read the actual published2.20.4Composer/upgrade manifests and intended3d7d0a19source manifests/policy/README/changelog. The2.21.0tag and Release endpoints both return 404. Workflow and SDK owners have been asked for their exact eventual authority handoffs; no producer build/release was requested.The intended PHP floor is
^8.2, Laravel^12.69.0|^13.30.0; Laravel 13 still requires PHP 8.3+. Workflow confirms no schema/history/protocol migration from #1047. Published 2.20.4 stays^8.1/^10.50.4|^11.56.1|^12.69.0|^13.30.0. Stable-v1 remains^8.1/ Laravel 9–13 on compatible interpreter versions. SDK #239 separately confirms published SDK 3.9.4 bare PHP^8.1, with its own Laravel 10–13 bridge contract; no SDK floor or example is being changed by inference.Scoped source inventory:
docs/installation.md:22docs/laravel-adoption.md:44and:331docs/compatibility.mdbefore Release Rulesdocs/migration.mdbefore Upgrade procedurei18n/{de,es,fr,pt-BR,uk,ja,zh-Hans}/docusaurus-plugin-content-docs/current/{installation,laravel-adoption,compatibility,migration}.mdversions.json,versioned_docs/version-1.x/installation.md:11, versioned 1.x examples/docs/2.0/aliases current 2.x. Leave the historical snapshot/version settings unchanged.docs/quickstart.md:42,118,docs/polyglot/php.md:77, and counterpartsdocs/polyglot/cli.mdx, Sample App pages, database compatibility snapshot and counterpartsstatic/stable-releases.jsonI will use ordinary Markdown preview/admonition and existing versioning, with no new flag system or prose-assertion tests. The draft will qualify ordinary source, translations and links. It stays unmerged/auto-off for the actual 2.21 manifest + Release Verification handoff before any live/current floor promotion. Documentation owns that final refresh, normal integration/Pages/live checks and cleanup; Workflow owns producer authority and SDK #239 its separate bridge adoption.
rmcdaniel commentedon Nov 5, 2026
Source preview is now draft #482, exact
1a17b2c61872324416d3d0413b75ca402fff27d9/ tree096d37bc783f317d690ee4d0661871a7b41fc174, based on accepted maine0a600a1. All four English guides and 28 localized counterparts are updated, plus the seven existing review-hash files. Every executable fence, stable-v1 file, current selector/installer and protocol authority is byte-preserved. The draft uses existing Markdown admonitions and versioning; no new flag or test of exact prose is added.Fresh registry readback confirms published 2.20.4 /
e3664430fd1b795aadaca89c835d5281502a01cewith PHP^8.1/ Laravel^10.50.4|^11.56.1|^12.69.0|^13.30.0; no 2.21.0 entry exists. GitHub's 2.21.0 tag/Release endpoints also returned 404. Workflow supplied the intended source and no-schema/history/protocol-migration boundary; SDK #239 supplied the independent bare PHP^8.1and current Laravel bridge constraints. These are recorded distinctly in the preview and are not installed/runtime acceptance.Local whitespace, public-boundary, secret-format, fence-preservation and review-hash checks pass. Ordinary hosted Node 24 qualification is running; Docs owns all failures and exact-head readback. Local Node is 22, so no full-build result from an unsupported toolchain is claimed. PR auto-merge is off and the draft stays unmerged for the actual 2.21 package/manifest plus Release Verification handoff from Workflow #1020. Then Docs owns the final current-floor/selector refresh, normal integration, Pages/artifact/live checks and cleanup. The ordinary publication follower is main-only Pages; this draft triggers no publishing/producer/runtime/provider operation. SDK #239 keeps its separate bridge adoption, and #457 remains an unrelated actual CLI delivery dependency.
rmcdaniel commentedon Nov 5, 2026
Prepared source remains draft #482, exact
1a17b2c61872324416d3d0413b75ca402fff27d9/ tree096d37bc, unmerged/auto-off. Its original Node24 qualification built all eight locales and11 contexts passed against basee0a600a1; this is archived source qualification, not current-main merge qualification.2026-11-06 04:14 UTC owner audit: fresh latest Workflow GitHub Release is still 2.20.4. The actual published2.21 package/manifest plus successful Release Verification handoff has not arrived. I renewed the concrete handoff request to the Workflow owner on existing#1020, without requesting another producer run. The independent main-site #483 is now complete, including its actual live status, and changes no guide/floor/selector/installer/v1 authority.
Next action / owner: Workflow#1020 returns actual published2.21 manifest/package + successful Release Verification; General coordinates the producer handoff and SDK#239 retains separate bare-PHP/bridge authority. Docs then incorporates accepted main normally, refreshes final published support guidance, runs new exact-head checks and owns protected Pages/artifact/live acceptance and cleanup. The draft remains held on that actual producer evidence; source1047 or native-contract progress does not substitute for release evidence. No live floor change, tag, package, runtime or repeat build is selected.
Post-#486 audit, 2026-11-06 06:20 UTC: fresh latest GitHub Release remains Workflow 2.20.4. The outstanding Workflow owner request is unchanged: return the actual published 2.21 manifest/package plus successful Release Verification on Workflow#1020. Docs completed the unrelated CI lifecycle fix at accepted main
add401ee966c8359773066f410321914779190fd; all 10,087 generated files and 15 live reads preserve the prior site, including floors/selectors/installers. This draft and its exact head remain unchanged/unmerged/auto-off. Docs owns the final normal maintained-base refresh and new exact-head/Pages/live qualification after that actual producer handoff. No repeat producer run, release or speculative update is requested.rmcdaniel commentedon Nov 7, 2026
The producer prerequisite is now delivered: Workflow2.21.0, exact current tag/source
cb9420019476d400e1df329f063cfb1a3b86ab18, manifest SHA2561e65a6ffa6f2a1feba53ff0b5f7782a9ac8d7a3560f31c44c040767c592308c6. Actual Release Verification42363788484/a1 passed all6 jobs including all5 supported Laravel12/13 cells. Primary release/authority handoff and independent final acceptance are available; Workflow1020 is closed. The old not-published/2.20.4-only blocker is superseded. Current retained 2.20 line is published2.20.5.General owns this docs follow-through because the documentation repository agent is Off. After the noon operating check, audit every affected embedded minimum/support statement and localized/versioned counterpart, then make the smallest existing-format patch from qualified Docs main91f8. Installation currently says PHP8.1/Laravel9 without a release-line boundary; it must distinguish actual2.21 embedded PHP^8.2/Laravel^12.69|^13.30 from retained2.20.x and stable-v1. Preserve bare SDK PHP^8.1 and do not advertise unreleased SDK3.10/service-bridge changes; coordinate the exact current SDK239/PR350 state. No combined qualified-artifact catalog bump is inferred.
The issue's existing ordinary docs source/integration/publication process applies; it explicitly imposes no extra per-PR Security/operator approval. Source preparation, relevant checks, actual-main/Pages/live verification and exact cleanup remain necessary. No new runtime, package release, provider operation or support-policy decision is selected by this handoff.
rmcdaniel commentedon Nov 7, 2026
Normal source integration is complete in #489. Reopening until actual-main, protected Pages and all localized live surfaces finish verification; the automatic closing keyword ran before those acceptance steps.
rmcdaniel commentedon Nov 7, 2026
Delivered and verified through PR #489: exact main/Pages deployment and all 24 localized live page checks pass. The final PR receipt records scope and completed topic cleanup.