Skip to content

Patch Larasend PHP runtime to 8.4.27 - #25

Open
vijaythecoder wants to merge 1 commit into
mainfrom
codex/larasend-php-security
Open

vijaythecoder wants to merge 1 commit into
mainfrom
codex/larasend-php-security

Conversation

@vijaythecoder

@vijaythecoder vijaythecoder commented Oct 22, 2026 •

Copy link
Copy Markdown
Collaborator

Larasend's email-serving, queue, scheduler, and rehearsal containers run PHP 8.4.24. Pin the shared runtime to the official PHP 8.4.27 FPM Alpine 3.24 image by digest, which includes the critical PHP security fixes. Give queue workers a three-minute shutdown grace period so active jobs can finish within their existing 150-second timeout.

The authorized production rollout preserves deployed application commit 077b2ea, vendor dependencies, and compiled assets. Their checksums match the replacement image. The candidate is published as 252497420278.dkr.ecr.us-east-1.amazonaws.com/savvyagents/larasend:php-8.4.27-077b2ea-20261022 (OCI index sha256:0733b2c07145b17682768c6b1d82f5fda151ec28e1f582e9f127fb44be40d607).

Validation: exact replacement image reports PHP 8.4.27 CLI/FPM with all required extensions; 56 focused tests passed with 255 assertions and warnings treated as failures, isolated from production and with no network. All four upstream PHP OOM security regression tests passed. Unrouted production canary /up and /login return 200; every migration is already applied and migrations are disabled for this runtime rollout. CI PHP 8.4/8.5 tests and Docker build passed; Codex review completed without findings.

The quality check fails at composer audit --locked on existing dependency advisories in the unchanged lockfile. This PR does not suppress the audit or change application dependencies. Authorized live rollout completed for app, queue, scheduler, and rehearsal: every container reports PHP 8.4.27 and Redis extension 6.3.0 with the same image config sha256:c00f18c8ea415fc252bf14217c6a8ac60cc1013e8adcad0d5b8e6ebadb4f132f. Effective app configuration hashes are unchanged. Database and Redis containers stayed running.

A production test sent only to the AWS SES Mailbox Simulator was queued by the application, sent by the patched worker, marked delivered by SES, and its real SNS delivery notification was processed by patched Larasend at 13:28:32 UTC on October 22. No customer recipients or outbound webhook subscribers were used. Queue is empty, worker/scheduler heartbeats are fresh, and failed-job count remains at the pre-rollout baseline. Public health/login/API/webhook-route smoke checks passed. The normal port-80 target is healthy. The temporary canary finished its full 300-second drain and was removed, along with its temporary ALB-only security-group rule. Production retains the original database/Redis containers, application code, effective app settings, storage volumes, and webhook URLs. Rollback configuration and the old image remain protected on the host.

@vijaythecoder

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-22T13:18:34.005591Z 92fbe71 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 92fbe7138d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

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.

1 participant