---
title: "Discussion on \"A Green Deploy That Ships the Old PHP\" | Hashnode"
description: "Discussion on \"A Green Deploy That Ships the Old PHP\". A critical PHP release, an unpinned install that should have picked it up, and the one line in a deploy log that showed my builds would quietly keep serving the vulnerable version."
url: "https://hashnode.com/posts/green-deploy-ships-old-php/6ad9d31c010592d53dc4a58b"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A Green Deploy That Ships the Old PHP](https://ubeyd.dev/green-deploy-ships-old-php?utm_source=hashnode&utm_medium=feed)

A critical PHP release, an unpinned install that should have picked it up, and the one line in a deploy log that showed my builds would quietly keep serving the vulnerable version.

Oct 22 · 11 min read · ubeyd.dev  
Read the article

-   [#laravel](https://hashnode.com/tag/laravel)
-   [#php](https://hashnode.com/tag/php)
-   [#fly-io](https://hashnode.com/tag/fly-io)
-   [#docker](https://hashnode.com/tag/docker)
-   [#security](https://hashnode.com/tag/security)
-   [#devops](https://hashnode.com/tag/devops)

## Written by

[Ubeydullah Keleş](https://hashnode.com/@ubeyd)

@ubeyd · Abidjan, Ivory Coast

  
[View profile](https://hashnode.com/@ubeyd)

Laravel Developer

## Responses 2

Markdown supported · ⌘↵ to post

[Kamran Khan](https://hashnode.com/@kamrankhandev)

[Oct 22](https://hashnode.com/posts/green-deploy-ships-old-php/6ad9d31c010592d53dc4a58b/comment/6ada0d3f7b6785cabc4c1e27)

There is a sibling to this one on servers that upgrade PHP in place rather than rebuilding the image. apt installs the new binary and php -v says 8.5.12, but the running php-fpm pool keeps serving requests from the old one until the service restarts. My rule after any PHP bump is now: restart the FPM pool, then confirm the version through the request path, not just the CLI.

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 22](https://hashnode.com/posts/green-deploy-ships-old-php/6ad9d31c010592d53dc4a58b/comment/6ada4f94e45e5683bfa0f10f)

Classic failure mode: the green environment gets tagged from a cached base image, so the deploy is green but the runtime is still the unpatched PHP. Pinning the base image digest and forcing a rebuild on security releases is the boring fix that prevents exactly this.
