-
Notifications
You must be signed in to change notification settings - Fork 11
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
Bump base image version #116
base: master
Are you sure you want to change the base?
Conversation
23aa16c
to
db8963c
Compare
Tested with https://github.com/Al2Klimov/twintowers . It's for you to decide whether this makes sense for 2.12.1 or not. |
|
AlternativeWait for all IW2 versions not supporting PHP 8.2 to EOL. |
Yet another alternative: make a |
But then we'd have to maintain multiple branches. My alternative involves less maintenance and it's realistic because Debian 11 will be maintained until Jul 2026. I don't know the exact IW2 release schedule, but idk why we shouldn't see at least a v2.13 by then. Also, why to force all image users to support PHP 8.2 right now? I'd say let's wait 1y+ before bumping the base images. CC @nicolasberens |
Fact-checkThis is false#116 (comment)
#116 (comment)
#116 (comment)
This is true
|
Omitting virtual php8.2-json, that extension is always there since PHP 8.
by not creating dynamic properties.
@lippserd I've re-built and pushed :2.12.1, :2.12, etc. with this branch, so that we have PHP 8.2 for K8s. So this PR should be merged before a v2.12.2, not to loose PHP 8.2. 😅 |
@lippserd Not only it already confuses people (1) that :latest already has PHP 8 while :main doesn't, the latter surely breaks K8s-web in :main, our "snapshot images". 🙈 Two more reasons to merge this. 😅 |
Omitting virtual php8.2-json, that extension is always there since PHP 8.
DbCommand now supports PHP 8.2 by not creating dynamic properties.
fixes #128