[todeveni]

Adds a weekly schedule trigger (Mondays 03:00 UTC) to the Build PHP Images workflow.

The image Dockerfiles use floating upstream tags (e.g. FROM php:8.4-apache-trixie), so a PHP patch release (8.4.x → 8.4.y) needs no code change, only an image rebuild. Until now, rebuilds happened only when files under images/** changed or when someone ran the workflow by hand. Patch releases and Debian security fixes could go unpublished until the next unrelated image change.

Bare minimum self-checks

What do you think of a person who only does the bare minimum?

• I've updated this PR with the latest code from main
• I've done a cursory QA pass of my code locally
• I've ensured all automated status check and tests pass
• I've connected this PR to an issue

Pieces of flare

• I've written a unit or functional test for my code
• I've updated relevant documentation it my code changes it
• I've updated this repo's README if my code changes it
• I've updated this repo's CHANGELOG with my change unless its a trivial change (like updating a typo in the docs)

Finally

• I've requested a review with relevant people

If you have any issues or need help please join the #contributors channel in the Lando slack and someone will gladly help you out!

You can also check out the coder guide.

[netlify]

👷 Deploy request for lando-php pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	cfdf2c3