Skip to content

Test Laravel 10 and 11 #2746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 7, 2024
Merged

Test Laravel 10 and 11 #2746

merged 1 commit into from
Mar 7, 2024

Conversation

GromNaN
Copy link
Member

@GromNaN GromNaN commented Mar 5, 2024

Follow-up #2735

In order to keep testing Laravel 10 when Laravel 11 will be released, I'm using a variable in the CI that specifies the version of laravel/framework, which is a meta package containing all illuminate packages.

Checklist

  • Add tests and ensure they pass
  • Add an entry to the CHANGELOG.md file
  • Update documentation for new features

@GromNaN GromNaN requested a review from alcaeus March 5, 2024 13:33
@GromNaN GromNaN requested a review from a team as a code owner March 5, 2024 13:33
Copy link
Member

@alcaeus alcaeus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. We should add Laravel 11 to the matrix instead of running two dev builds once it's been released.

@GromNaN
Copy link
Member Author

GromNaN commented Mar 5, 2024

LGTM. We should add Laravel 11 to the matrix instead of running two dev builds once it's been released.

Yes, but we have to wait for other dependencies to be tagged, like orchestra packages.

@GromNaN GromNaN force-pushed the ci-laravel-11 branch 2 times, most recently from 2e58716 to 62fe7ca Compare March 5, 2024 15:36
@GromNaN
Copy link
Member Author

GromNaN commented Mar 5, 2024

@alcaeus updated. We have to update the project config to adapt to the new job names.

@alcaeus
Copy link
Member

alcaeus commented Mar 6, 2024

Updated. While doing that I noticed that this will cause issues with pull requests targeting 4.1, as the new build names won't match there. Since branch protection rules won't properly match, should we target 4.1 with this change (excluding Laravel 11) and then add Laravel 11 after merging up?

@GromNaN GromNaN requested a review from alcaeus March 6, 2024 16:58
@GromNaN GromNaN merged commit 963d01f into mongodb:4.2 Mar 7, 2024
@GromNaN GromNaN deleted the ci-laravel-11 branch March 7, 2024 09:30
alcaeus added a commit that referenced this pull request Mar 13, 2024
* 4.2:
  PHPORM-139 Implement `Model::createOrFirst()` using `findOneAndUpdate` operation (#2742)
  Test Laravel 10 and 11 (#2746)
  PHPORM-150 Run CI on Laravel 11 (#2735)
  PHPORM-152 Fix tests for Carbon 3 (#2733)
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