Skip to content

Add Laravel 13 support + modernise CI matrix (currently Laravel 10 only) #115

Description

@SimonBarrettACT

Tracking Laravel 13 readiness for the People app (ACT-Training/people#3153, #3155).

Current state

This package has no direct illuminate/* / laravel/framework dependency, and its runtime requires already resolve on Laravel 13:

  • secondnetwork/blade-tabler-icons ^3.24 → latest (v3.44.0) supports illuminate/support ^13.0
  • spatie/laravel-package-tools ^1.14 → latest supports illuminate/contracts ^13.0
  • livewire/livewire ^3|^4

So 2.4.0 (the version People pins) is effectively already L13-compatible. Laravel Shift flags it because it's pinned exact with no explicit Laravel support declared.

Gap to close (this one is real)

CI is badly out of date — it only proves Laravel 10:

  • run-tests.yml matrix: laravel: [10.*] only (no 11/12/13).
  • orchestra/testbench is ^9.0 (Laravel 11 era).

Done when

  • Bump orchestra/testbench to allow ^11 (Laravel 13) alongside existing — e.g. ^9|^10|^11; bump Pest if testbench 11 requires Pest 4.
  • Update the run-tests.yml Laravel matrix from 10.* to cover 11.*, 12.*, 13.*.
  • Green suite on Laravel 13 (watch the TableBuilder paths People relies on across Settings pages).
  • Tag a patch release (e.g. 2.4.1) so People can require a provably-L13 version.

Note: no production code change is expected unless a real L11→L13 incompatibility surfaces — primarily CI modernisation + proof.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions