Skip to content
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

Updates, deprecation fixes and GitHub Actions CI setup #21

Merged
merged 5 commits into from
May 8, 2022

Conversation

mpdude
Copy link
Contributor

@mpdude mpdude commented May 5, 2022

Hi there 👋🏻 ,

this PR provides the results of mpdude#1, mpdude#2 and mpdude#3.

It

  • sets up GitHub Actions to run CI tests on various current Symfony versions,
  • updates PHPUnit,
  • adds missing dependency declarations
  • adds return type hints to address Symfony deprecation notices in current versions.

Update

This was released as v3.0.0 of this bundle. However, there should be not relevant changes for regular users of this code. As long as you don't extend or replace classes from this bundle, the added return types should not affect you and you should be able to upgrade to v3.0.0 right away.

mpdude added 3 commits May 5, 2022 14:07
This sets up a workflow with [ComposerRequireChecker](https://github.com/maglnet/ComposerRequireChecker) to make sure all actual dependencies are declared.
This updates tests for PHPUnit v8/v9, and sets up a GHA workflow to run a test matrix for PRs.
This adds a few return type hints where Symfony 5.4 triggers deprecation notices. 

I don't see the risk of BC breaks since there is no good reason to overwrite the methods affected. Adding types should even be compatible with PHP 7.0.
@jbouzekri
Copy link
Owner

@mpdude : thank you very much for your work. Give me a few day to review it. I should be able to do it by monday.

@mpdude
Copy link
Contributor Author

mpdude commented May 5, 2022

Awesome!

I can't really help with Travis CI, but GitHub actions should run PHPUnit already. Maybe it needs a first time approval by you so that my PRs may trigger runs in your Repo?

@mpdude
Copy link
Contributor Author

mpdude commented May 5, 2022

Oh, and maybe we need to add Symfony 5.4 (LTS) to the build matrix as well. ✅

@jbouzekri jbouzekri merged commit dbf28c6 into jbouzekri:master May 8, 2022
@jbouzekri
Copy link
Owner

Done. Merged. You were right. It was because github action did not peak up the workflow from the PR to initialize itself.

I am going to tag a new major release. Thank you very much

@mpdude mpdude deleted the mpdude-changes branch May 9, 2022 07:28
@mpdude
Copy link
Contributor Author

mpdude commented May 9, 2022

Travis failed in this PR, and I don't know about the results from Scrutinizer.

Do you still see value in using these two?

@jbouzekri
Copy link
Owner

You are right we can remove Scrutinizer.

For Travis, it succeeded https://app.travis-ci.com/github/jbouzekri/PhumborBundle when I merged your PR.

@mpdude
Copy link
Contributor Author

mpdude commented May 9, 2022

Yes, but does it add value over running PHPUnit tests in GitHub Actions?

@mpdude
Copy link
Contributor Author

mpdude commented May 9, 2022

We can discuss this in #22 .

mpdude added a commit to webfactory/WebfactoryResponsiveImageBundle that referenced this pull request May 31, 2022
Diese neue Major Version enthält keine für uns relevanten Änderungen, vgl. jbouzekri/PhumborBundle#21.
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