-
Notifications
You must be signed in to change notification settings - Fork 154
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
[TASK] Update the development tools #1121
Conversation
c5834db
to
870b57f
Compare
870b57f
to
0170991
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you intend to update the minimum Psalm version?
0170991
to
7de861b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine now.
I'm happy to work the the current known build failures if you are happy to use your superhero powers to commit changes. However, neither test failures are straightforward to fix, and it may be some time (one would require a new release of a 3rd party component, and for the other, see #1139). Maybe we should temporarily disable the failing tests, so as to avoid any mistakes propagating to |
Build might be green after a rebase, as a result of #1138. |
Also reorder the entries in the `composer.json` to match the rules of the latest composer-normalize version.
7de861b
to
60135e7
Compare
Also reorder the entries in the
composer.json
to match the rulesof the latest composer-normalize version.