diff --git a/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/decisions.md b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/decisions.md new file mode 100644 index 0000000..bc2b54b --- /dev/null +++ b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/decisions.md @@ -0,0 +1,11 @@ +## D-001: Create the ticket as drafted? +- Choice: Create as drafted +- Rationale: none given (answered in RingMaster) +- Date: 2026-10-27 +- Raised by: ticket + +## D-002: How should this job proceed? (PR #2 failure is the paratest conflict, same as ticket #7) +- Choice: Wait for ticket #7 to merge, then rebase PR #2 and confirm it is green +- Rationale: Keystone PR #8 (drop the paratest conflict, require pest ^5.3.4) is merged, so rebase PR #2 on main now and confirm it goes green. Change no code unless it still fails. (answered in RingMaster) +- Date: 2026-10-27 +- Raised by: shape diff --git a/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/meta.yml b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/meta.yml new file mode 100644 index 0000000..c411478 --- /dev/null +++ b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/meta.yml @@ -0,0 +1,6 @@ +id: 2026-10-27-1055-fix-setup-php-2-40-0-bump +title: Fix CI failure on setup-php 2.40.0 Dependabot bump +status: closed +created: 2026-10-27 +ticket: { provider: github, key: "#6", url: https://github.com/Refactor-Circus/Keystone/issues/6 } +standards: {} diff --git a/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/questions.yml b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/questions.yml new file mode 100644 index 0000000..fe51488 --- /dev/null +++ b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/questions.yml @@ -0,0 +1 @@ +[] diff --git a/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/references.md b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/references.md new file mode 100644 index 0000000..1d09b07 --- /dev/null +++ b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/references.md @@ -0,0 +1,5 @@ +# References + +- `composer.json` (`conflict` block, `pestphp/pest` constraint): source of the failing resolution; also the subject of ticket #7 and spec `2026-10-27-1057-drop-paratest-conflict-require-pest-5-3-4`. +- Failing run: https://github.com/Refactor-Circus/Keystone/actions/runs/38594628917/job/122264936537 +- PR #2: Dependabot setup-php bump. diff --git a/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/shape.md b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/shape.md new file mode 100644 index 0000000..28503b3 --- /dev/null +++ b/docs/agent/specs/2026-10-27-1055-fix-setup-php-2-40-0-bump/shape.md @@ -0,0 +1,22 @@ +# Fix CI failure on setup-php 2.40.0 Dependabot bump — Shaping Notes + +## Scope + +Ticket #6. Dependabot PR #2 (shivammathur/setup-php 2.37.2 -> 2.40.0) fails only the `P8.5 - L13.* - prefer-stable - ubuntu-latest` job; the other three matrix lanes pass. Goal: PR #2 goes green. Out of scope: merging PR #2, other matrix lanes. + +## Decisions + +- D-001: ticket created as drafted. + +## Context + +The failing log (run 38594628917) shows the failure is not caused by setup-php. The `composer update` step cannot resolve dependencies: + +- `pestphp/pest v5.3.1 conflicts with phpunit/phpunit 13.4.5` +- `refactor-circus/keystone conflicts with brianium/paratest v7.27.1 - v7.27.4` + +The second line is the `conflict: brianium/paratest >=7.26.1` entry in `composer.json`, the same problem as ticket #7 ("Drop paratest conflict, require pest ^5.3.4"). A newer prefer-stable resolution of dependencies hits it regardless of the setup-php version. Changing the workflow for the bump would not fix it. + +## Standards + +None apply: the work is CI/composer maintenance and touches no package code.