Skip to content

[2.x] Fix workflow YAML syntax and remove no-op composer require - #291

Merged
taylorotwell merged 1 commit into
laravel:2.xfrom
JoshSalway:fix/workflow-yaml-syntax
Mar 24, 2026
Merged

[2.x] Fix workflow YAML syntax and remove no-op composer require#291
taylorotwell merged 1 commit into
laravel:2.xfrom
JoshSalway:fix/workflow-yaml-syntax

Conversation

@JoshSalway

@JoshSalway JoshSalway commented Mar 24, 2026

Copy link
Copy Markdown

Summary

The tests workflow has been broken since 2026-02-20 when PR #289 (Laravel 13.x Compatibility) accidentally unquoted the '*.x' branch pattern. Every test run since then has been instantly rejected by GitHub Actions — 5 weeks of no CI coverage.

Root cause

The L13 compatibility PR changed '*.x' to *.x in the branches list. In YAML, * is a reserved character (alias node indicator), causing GitHub Actions to reject the workflow file. The quotes were correct before and got removed during the edit.

Fix

  1. Re-quote *.x to '*.x' — restores the branch pattern that was working before PR Laravel 13.x Compatibility #289
  2. Remove the no-op composer require --no-update line — this has been in the workflow for a while with no package argument. Composer silently ignores it (exits 0), so it's not causing failures, but it's dead code that looks like a bug.

CI result

All 30/30 matrix jobs pass — PHP 7.2–8.4 × Laravel 6–13.

- Quote *.x branch pattern — unquoted * is reserved in YAML, causing
  the workflow to fail on every push to versioned branches
- Remove empty composer require with no package name, which caused
  every CI job to fail with "Not enough arguments"
@github-actions

Copy link
Copy Markdown

Thanks for submitting a PR!

Note that draft PRs are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

@taylorotwell
taylorotwell merged commit aaf7891 into laravel:2.x Mar 24, 2026
30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants