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

Build Failing due to psalm update #130

Open
jarstelfox opened this issue Nov 3, 2020 · 3 comments · May be fixed by #151
Open

Build Failing due to psalm update #130

jarstelfox opened this issue Nov 3, 2020 · 3 comments · May be fixed by #151

Comments

@jarstelfox
Copy link
Contributor

The last passing build of master was running psalm v3.8.5, but after that, builds have been failing psalm v3.11.5+.

I think the best options are either:

  1. Put a composer.lock so you can pick when to update psalm in CI
  2. Fix the existing issues as you notice them crop up

I don't mind helping out here, just let me know the direction you would like to go.

@mnapoli
Copy link
Member

mnapoli commented Nov 3, 2020

Hi, thank you for raising this!

Putting the composer.lock is indeed not ideal, but I would prefer that here since this is a library that doesn't receive a lot of activity or updates (for good reason, it's pretty stable). So that would be the best to avoid continuous work on this.

If you are able to send a pull request that would be perfect!

@gharlan
Copy link
Contributor

gharlan commented Nov 13, 2020

Instead of pushing the composer.lock, you could use an explicit version for vimeo/psalm in composer.json, and update it manually from time to time, or dependabot can create pull requests for increasing the version in composer.json.

@mnapoli
Copy link
Member

mnapoli commented Nov 14, 2020

you could use an explicit version for vimeo/psalm in composer.json

@gharlan that's a good idea!

@simPod simPod linked a pull request Aug 3, 2021 that will close this issue
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 a pull request may close this issue.

3 participants