Skip to content

Conversation

@ruudk
Copy link
Contributor

@ruudk ruudk commented Oct 23, 2025

No description provided.

@ruudk
Copy link
Contributor Author

ruudk commented Oct 23, 2025

@frederikbosch Every year we see each other in these type of PR's and we previously discussed it and I understand your position.

I wonder I we could maybe find a middle ground where we say, we tag support for Money PHP as soon as we have Release Candidate X? I would be happy to do the work every year.

https://wiki.php.net/rfc/release_cycle_update

@frederikbosch
Copy link
Member

@ruudk and so we meet again. How about #818? We add a specific job to CI for early versions (and php-src main when there is no new version?) that ignores platform reqs and allows to fail?

@frederikbosch
Copy link
Member

But, once we can add || ~8.5.0, I am happy to merge that, fully support the version and tag it, even if the new PHP version is not a stable release yet.

@frederikbosch frederikbosch merged commit d418dd8 into moneyphp:master Oct 23, 2025
13 of 14 checks passed
@frederikbosch
Copy link
Member

@ruudk With new setup we always test dev version of PHP, but allow it to fail (|| true). This way we could see early on if there are problems with a new version. Once we can add || new-version to composer.json we can add full support to the version and tag a new release. Hopefully this is an improvement over what we had before.

@frederikbosch
Copy link
Member

@ruudk And v4.8.0 has just been tagged, with support for PHP8.5. Thanks for bringing it up and suggestion to improve the setup.

@ruudk
Copy link
Contributor Author

ruudk commented Oct 23, 2025

@frederikbosch Sounds like a great workflow going forward! This makes me really happy. 🎉 Thanks

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