Skip to content

Update "google/analytics-data", dev dependencies, and support Laravel 13#47

Merged
Baspa merged 3 commits into
backstagephp:mainfrom
duyphuongn:laravel-13
Apr 30, 2026
Merged

Update "google/analytics-data", dev dependencies, and support Laravel 13#47
Baspa merged 3 commits into
backstagephp:mainfrom
duyphuongn:laravel-13

Conversation

@duyphuongn

@duyphuongn duyphuongn commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

This pull request does the following:

  • Update google/analytics-data to 0.23.3 with correct types and replacement for deprecated classes
  • Add ^13.0 to illuminate/contracts to support Laravel 13
  • Update some dev dependencies to their latest versions

@Baspa Baspa self-assigned this Apr 29, 2026
@Baspa

Baspa commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Thanks @duyphuongn! Do you think you can add tests for L13 installation as well? If not, I can take a look at it..

@duyphuongn

duyphuongn commented Apr 29, 2026

Copy link
Copy Markdown
Contributor Author

Thanks @duyphuongn! Do you think you can add tests for L13 installation as well? If not, I can take a look at it..

Hi @Baspa, due to lack of resources, I'm afraid I can't.
Thank you.

@duyphuongn duyphuongn marked this pull request as draft April 29, 2026 14:33
@duyphuongn duyphuongn marked this pull request as ready for review April 29, 2026 15:01
@duyphuongn duyphuongn changed the title Update "google/analytics-data"and support Laravel 13 Update "google/analytics-data", dev dependencies, and support Laravel 13 Apr 29, 2026
Baspa and others added 2 commits April 30, 2026 08:45
Drop PHP 8.1/8.2 (larastan ^3 requires 8.2+; modern Laravel needs 8.3+)
and replace Laravel 10 with Laravel 12 and 13. Bump dev dependency
constraints (orchestra/testbench, pestphp/pest, phpunit) to versions
compatible with Laravel 13's testbench. Migrate phpunit.xml.dist to the
PHPUnit 11+ schema so pest 4 doesn't fail on the deprecated config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PHPUnit 11+ raises a "No code coverage driver available" warning when
<coverage> is configured but no driver is loaded, and our phpunit.xml.dist
has failOnWarning="true". The workflow uses coverage: none, so passing
--no-coverage suppresses the unused coverage attempt and lets pest --ci
exit 0.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Baspa Baspa merged commit c6afc80 into backstagephp:main Apr 30, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants