Skip to content

Restore bound PHP setup after upstream archive replacement #400

Closed

Description

@rmcdaniel

The upstream builds release replaced both admitted PHP 8.3 archives on November 14. The pinned Ubuntu 24.04/26.04 assets 739209532/739711545 return 404 before dependent repository tests can start. This common failure blocks SDK PHP #425/#426, CLI #161, central #401, Rust SDK #279 and Waterline #324/#311 security delivery. Closed #403 is the same root cause.

Repair: PR404, exact reviewed head d8826b0. General owns the common repair and administrator escalation. Consumer owners retain their own source, acceptance, integration and release decisions.

Completion requires:

  • Bind replacement official assets by exact ID/size/SHA-256; regenerate and independently review the archive/link/alternatives/configuration records. Preserve installer, TLS, regular-only derivation, runtime and credential boundaries.
  • Activate the reviewed immutable policy workflow through the exact full-body organization ruleset transition, with enforcement Active and every other rule/condition unchanged. Prove fresh accepted and refused events, then merge the reviewed repair through normal checks.
  • Qualify both original hosted setup profiles and admit immutable helper 5c1ddbf through the reviewed action/workflow policies.
  • Consumer owners update their prepared pins and verify the previously blocked original callers. Original failures remain failures; no new General per-run or merge gate is required.
  • Verify drift detection against the refreshed catalog and document upstream retention limits. A Git pin cannot prevent upstream asset deletion. No mirror, fallback or broader profile is selected.

Current state: the common repair is delivered at central main ac69417b63ffb63f61ec55be3ec667526a7482f2, with exact reviewed tree equality and all actual-main workflows passing. The approved change to ruleset 26628397 retains Active enforcement and every other condition, while selecting immutable workflow d8826b0. The UI also retains its source ref; the live effective-rule readback matches. Fresh accepted policy run passes and the deliberate unknown-pin control refuses through the expected closed-context check. The negative control PR #406 is closed without merge.

Both original hosted setup qualifications pass: Ubuntu 26.04 and Ubuntu 24.04. Exact archive identities, configured receipt, normalization/configuration manifests, nine alternatives, Composer/PHPUnit probes and terminal cleanup are verified. No further administrator action is pending.

Remaining work is consumer adoption and its actual caller checks, including PHP #429 and Rust #281, plus verification of the existing catalog drift check. General owns this follow-through while the other managed agents are off. Retain the selected central source branch while it remains the ruleset's source ref.

Related: #297 and the re-pin policy recorded in closed #358.

Activity

  1. added
    priority:P1High-priority product or release risk
    status:blockedWaiting on a named dependency or decision
    on Nov 14, 2026
  2. rmcdaniel commented on Nov 18, 2026

    @rmcdaniel
    MemberAuthor

    Delivered; every criterion is met.

    • Central repair and helper admission: delivered at ac69417b. Both hosted setup qualifications pass (Ubuntu 26.04, Ubuntu 24.04), and helper 5c1ddbff is admitted.
    • Consumer adoption: sdk-php#429 and sdk-rust#281 are merged. workflow#1191 moved Workflow's tag-time release verification to 5c1ddbff; a verification of 2.28.1 and the 2.29.0 release verification both passed. A scan of every workflow and action file on the default branches of cloud, server, workflow, sdk-php, sdk-python, sdk-rust, cli, waterline, sample-app, docs and .github finds no remaining reference to the retired 411a14ac.
    • Drift detection: the scheduled php-linux-upstream-pins check caught the upstream deletion (assets reported missing, runs 43681162956 and 43810614875 failed on Nov 15/16). It passes against the refreshed catalog on Nov 17 and 18 (runs 44024228265 and 44244453135). As recorded above, a Git pin cannot prevent an upstream deletion; the daily check is what detects one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority:P1High-priority product or release riskstatus:blockedWaiting on a named dependency or decision

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions