Skip to content

Conversation

@torchello
Copy link
Contributor

Resolving #1499

  1. Update composer.json/lock
  2. Update README
  3. Add 8.5 to CI

@torchello
Copy link
Contributor Author

@andypost seems like 8.5 should be added to Prophecy first 🤔

@andypost
Copy link
Contributor

yes, related phpspec/prophecy#656

- PHP 8.4 compatibility [@jrfnl](https://github.com/jrfnl) [@andypost](https://github.com/andypost)
- PHP 8.4 compatibility [@jrfnl](https://github.com/jrfnl) [@andypost](https://github.com/andypost)

## [8.1.0](https://github.com/phpspec/phpspec/compare/8.0.0...8.1.0)
Copy link
Member

Choose a reason for hiding this comment

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

new versions should be added on top rather than at the end (so that we see first the recent version)

Copy link
Contributor

Choose a reason for hiding this comment

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

@torchello please polish it as it's only dependency left waiting for Drupal to declare compatibility with PHP 8.5

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was waiting for the prophecy's release. Seeing some network issues in CI now. Will re-trigger later.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

So latest Psalm 6.x release does not support PHP 8.5 :(
https://github.com/vimeo/psalm/blob/6.13.1/composer.json#L22

Seems like we need to wait or migrate to 7.0-beta.

@stof
Copy link
Member

stof commented Dec 1, 2025

I think we should split the CI workflow into different jobs. Coding standard checks and static analysis don't need to be done for all PHP versions, which would allow us to decouple the PHP versions being tested from versions supported by our static analysis tooling.

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.

3 participants