-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
New php-latest tag #930
Comments
I believe we are blocked as per #932 (comment) |
Sorry, but even with #932 I don't think I'm comfortable with a |
Thank you both for jumping in! Fair point @tianon. When I suggested this, I was thinking about This would simplify things for developers when building pipelines with a compatibility matrix. Let's suppose I want to test my plugin with PHP 7.4, 8.1 (the 2 most used major versions) and the latest PHP version available. It would be 8.3 right now but once there is an image for 8.4, we would test against 8.4 without applying any change to our plugin repository. I don't see a problem in calling PHP 8.3 as "php-latest" for the moment even though PHP 8.4 is out since there isn't any official WordPress image for 8.4, so anyway I can just opt in for 8.3 - i.e. for me that would be the latest version I could use. Without this "php-latest" dynamic tag, we would need to continuously monitor and update our repository every time a new image with a new PHP version is released. Do you see value in this and do you think there could be a workaround for it? Thank you! |
It's an interesting idea but I am worried it would cause confusion (since both Tianon and us made the same assumption) |
That's a great point indeed. What about |
Naming is hard! |
Hi!
We currently have the tag "latest" for images with the latest WordPress version. Would it be possible to have another
php-latest
,phplatest
or similar tag (in the same way as php8.1, php8.2, etc) to indicate the latest PHP version available?It would be quite useful for plugin developers to test compatibility with the latest PHP version dynamically.
Thank you!
The text was updated successfully, but these errors were encountered: