From 62bdb4345a0b6b43452f7904f4b10ab4f9dd3304 Mon Sep 17 00:00:00 2001 From: Ousama Ben Younes Date: Sat, 22 Aug 2026 23:09:57 +0000 Subject: [PATCH] ci: restore the PMU_VERSION pin that the merge up dropped The pin landed on 4.3 in #8442, but merging up to main kept the 21 "soyuka/pmu:$PMU_VERSION" call sites while dropping the env entry that defines the variable. Every job that installs pmu therefore runs composer global require "soyuka/pmu:" and aborts with "Option soyuka/pmu is missing a version constraint", which is why main is currently red in 90 of its 91 failing checks and every pull request targeting it fails the same way. Restore the env entry, and constrain the one remaining call site in the Upgrade Filter Codemod job that #8442 did not cover, so no job installs whatever version the registry serves that day. --- .github/workflows/ci.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 79cb690e4c..2524ecf066 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -25,6 +25,9 @@ permissions: env: COMPOSER_TOKEN: ${{ secrets.GITHUB_TOKEN }} COMPOSER_ROOT_VERSION: "5.0.x-dev" + # Pinned build tooling: these are installed and executed on the runner, so an + # unconstrained version would run whatever the registry serves that day. + PMU_VERSION: "0.3.0" jobs: architecture: @@ -156,7 +159,7 @@ jobs: restore-keys: ${{ runner.os }}-composer- - name: Update project dependencies run: | - composer global require soyuka/pmu + composer global require "soyuka/pmu:$PMU_VERSION" composer global config allow-plugins.soyuka/pmu true --no-interaction composer global link . - name: Codemod unit tests