Repository navigation
Prepare PHP SDK 3.2.0 activity maintenance release - #204
Merged
Merged
Conversation
|
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.



PHP SDK 3.2.0 release identity
Merged at dfaae75 / whole 4359e5b4d8df378af47e2da29f2ef2a2f08fe8cf, identical to the candidate. Immutable 3.2.0 is published and Packagist reports that exact source. A fresh ordinary Composer installation loads the registry package at that reference and passes the existing package, quickstart and actual Worker-registration identity check as
durable-workflow-php/3.2.0. No source override or path repository is used. Portal run 39638685098 passes build/deploy; the live deployment audit reports that exact source and the homepage offersdurable-workflow/sdk:^3.2. Affected Server lease-renewal acceptance remains pending.Part of Workflow #878, following merged #202. Sets the Composer product train and quickstart contract to 3.2.0 and dates the existing changelog entry for the additive activity-maintenance API and fresh-process custom Client bootstrap. The current changelog comparison points to the new release, and onboarding selects the compatible 3.2 series.
Runtime, dependency requirements and protocol are unchanged from main
acce3db8bf6b835b73bc653905588bea49041781/ whole5f6f292de897b56e9f202b488610eb190be1a2e7. Its independent normal main CI39622133587, portal, Sonar and boundary pass. This metadata candidate independently passes supported PHP/framework, package identity, docs, analysis, corpus, Sonar and target-branch qualification before merge. Fresh-main checks remain separate.The real private-CA/rotating-auth component remains scoped source evidence. Actual published-package and six-minute/killed-worker Server controls remain open under #878; no newer Server or native capability is adopted by this release metadata.
Exact release metadata follow-through
Current source is
9d6dedb6f239eef2edb3b2211a448f52ac0c216c/ whole4359e5b4d8df378af47e2da29f2ef2a2f08fe8cf.The first metadata candidate
7bc7e6e4leaves the quickstart contract at 3.1.0. Original CI39628902216records PHP 8.1/8.4 test failures, the docs example-check failure, and the package release-identity failure. All four failed logs were read after the workflow became terminal: the tests fail the release-metadata identity assertion, docs refuses the product-train mismatch, and package smoke reportsInstalled quickstart published_version identifies '3.1.0'; expected 3.2.0. Remaining superseded jobs are cancelled. The original failed observations are preserved, and the correction changes only the three inconsistent release fields.The existing portal release module independently refuses that source with
Quickstart package identity must match the release-owned Composer metadata.Updating the three release fields makes the same unmodified module load the 3.2.0 identity anddurable-workflow/sdk:^3.2onboarding command. Both one-shot checks run in the borrowed Node/PHP tools image, with no network, repository writes, dependency installation or retained container. Those focused checks remain distinct from the subsequently passing full candidate CI and actual registry installation.