Skip to content

Release v1.1.0: make docker release-readiness installable (composer + patches) #9224

Description

@PurHur

Problem

Daily ./script/docker-exec.sh -- bash -lc "./script/release-readiness.sh --json" is red in a clean workspace:

  • check-selfhost-spine-coverage-sync fails because vendor/autoload.php is missing
  • Attempting composer install inside the docker wrapper fails on PHP 8.2 with lock constraints (ircmaxell/php-cfg + multiple dev locks require PHP ^7)
  • north-star5-verify-fast fails with patch-application hint (patches not applied in this flow)

This blocks maintainers from getting a reliable quick readiness signal and therefore blocks a user-facing tag.

Acceptance criteria

  • ./script/docker-exec.sh -- bash -lc "./script/release-readiness.sh --json" runs to completion on a fresh checkout.
  • spine-coverage gate does not fail due to missing vendor/.
  • Patch gates run in the same flow (either apply patches automatically or provide a single documented command sequence).

Repro

./script/docker-exec.sh -- bash -lc "./script/release-readiness.sh --json"
# (currently fails)

./script/docker-exec.sh -- bash -lc "composer install -n --prefer-dist"
# (currently fails on PHP 8.2 vs lock constraints)

Scope

  • script/release-readiness.sh — orchestration / vendor bootstrap
  • composer.json / composer.lock — PHP version constraints for docker image PHP 8.2
  • script/apply-patches.sh — integrate into readiness flow or document prerequisite
  • Docker image php-compiler:22.04-dev — ensure composer install succeeds in script/docker-exec.sh

Done when

  • ./script/docker-exec.sh -- bash -lc "./script/release-readiness.sh --json" exits 0 on a clean tree after documented bootstrap (composer install + script/apply-patches.sh).
  • JSON output includes green spine-coverage and north-star5-verify-fast gates (or documented opt-out with reason).
  • README or docs/local-ci-matrix.md lists the single copy-paste release-readiness command sequence.
  • No manual vendor/ commit required; lock file installable in Docker PHP 8.2.

Context

Roadmap: #78 (User release roadmap → v1.1.0 → must-ship + gate checklist). Related bootstrap: #1492, #9223.

Activity

  1. added
    releaseUser-facing release tracking
    implementation-readySpec complete: repro, php-src ref, done-when — safe for workers to claim
    on Jun 17, 2026
  2. PurHur commented on Jun 17, 2026

    @PurHur
    OwnerAuthor

    claim: cursor-agent — starting this run

  3. PurHur commented on Jun 17, 2026

    @PurHur
    OwnerAuthor

    Handoff: release-readiness quick mode fails on north-star5-verify-fast step 2 — spine missing 4 inventory files (acosh/asinh/atanh + BackedEnumDuplicateJitGuard). bootstrap-inventory --check is green (2757/2757). Composer/vendor path from issue repro not reproduced on this host (vendor present). Next: add spine requires per bootstrap-selfhost-next-includes.php --limit=4.

  4. PurHur commented on Jun 18, 2026

    @PurHur
    OwnerAuthor

    claim: cursor-agent-lane-c — continuing spine sync handoff from prior run

  5. PurHur commented on Jun 18, 2026

    @PurHur
    OwnerAuthor

    Merged via #9634.

    Verification:
    ```bash
    php script/check-selfhost-spine-coverage-sync.php

    check-selfhost-spine-coverage-sync: OK (spine covers all 2770 inventory files)

    make north-star5-verify-fast

    north-star5-verify: OK (fast)

    ```

    Added 11 missing spine requires (acosh/asinh/atanh, DeployPathJitHelper, ProgressJitHelper, BackedEnumDuplicateJitGuard, NamedOptionalCallArgs, LastErrorRuntimeLlvm, ProgressNoteRuntimeLlvm, TimeSleepRuntimeLibcBridge, StringStripTagsJit).

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

    IMPORTANTCritical pathimplementation-readySpec complete: repro, php-src ref, done-when — safe for workers to claimreleaseUser-facing release trackingrelease-blockerBlocks tagged user release

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions