Skip to content

feat: OLS PHP 8.4 support#20

Merged
alaminfirdows merged 14 commits intoflywp:mainfrom
ma-04:main
Jul 17, 2025
Merged

feat: OLS PHP 8.4 support#20
alaminfirdows merged 14 commits intoflywp:mainfrom
ma-04:main

Conversation

@ma-04
Copy link
Copy Markdown
Member

@ma-04 ma-04 commented Jun 26, 2025

  • Enabled Docker image creation and deployment for OLS with PHP 8.4.

Summary by CodeRabbit

  • New Features
    • Added support for PHP 8.4 in the build and test workflows for OpenLiteSpeed Docker images.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 26, 2025

Walkthrough

The GitHub Actions workflows for building and testing OpenLiteSpeed Docker images have been updated to add PHP 8.4 support. Both the deploy and test workflow matrices now include PHP 8.4, ensuring that images for this version are built and tested alongside existing PHP versions.

Changes

Files Change Summary
.github/workflows/deploy.yml Added PHP 8.4 to build matrix and matrix include for deploy.
.github/workflows/test.yml Added PHP 8.4 to build matrix for test workflow.

Sequence Diagram(s)

sequenceDiagram
    participant GitHub Actions
    participant Build Matrix
    participant Docker Build
    participant Test Suite

    GitHub Actions->>Build Matrix: Expand matrix (php_version: 7.4, 8.1, 8.2, 8.3, 8.4)
    loop For each php_version
        Build Matrix->>Docker Build: Build OpenLiteSpeed image with PHP $version
        Docker Build->>Test Suite: Run tests on built image
        Test Suite-->>GitHub Actions: Report results
    end
Loading

Possibly related PRs

Suggested reviewers

  • alaminfirdows

Poem

A new PHP arrives, version eight point four,
The matrix expands, just like before.
Images are built, and tests run anew,
OpenLiteSpeed shines with something fresh to do!
With every hop, our workflow grows bright—
The future of PHP is looking just right! 🐇✨

✨ Finishing Touches
🧪 Generate Unit Tests
  • Create PR with Unit Tests
  • Post Copyable Unit Tests in Comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai auto-generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e3f40dd and 124380c.

📒 Files selected for processing (2)
  • .github/workflows/deploy.yml (2 hunks)
  • .github/workflows/test.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (11)
  • GitHub Check: build-openlitespeed (8.4, lsphp84)
  • GitHub Check: build-openlitespeed (8.3, lsphp83)
  • GitHub Check: build-openlitespeed (8.2, lsphp82)
  • GitHub Check: build-php (8.4)
  • GitHub Check: build-php (8.1)
  • GitHub Check: build-openlitespeed (8.1, lsphp81)
  • GitHub Check: build-php (7.4)
  • GitHub Check: build-openlitespeed (7.4, lsphp74)
  • GitHub Check: build-php (8.2)
  • GitHub Check: build-php (8.0)
  • GitHub Check: build-php (8.3)
🔇 Additional comments (4)
.github/workflows/deploy.yml (3)

84-85: Confirm lsphp84 packages exist in LiteSpeed repos
If LiteSpeed hasn’t shipped lsphp84 yet, the Dockerfile build will fail on apt-get install lsphp84. Double-check the repo or pin the job behind a feature flag until the package is published.


21-21: Verify upstream availability of the php:8.4 base image before merging
8.4 is added to the build matrix, but the official PHP Docker library may not publish that tag yet (or it may still be in alpha). A missing base image will break the whole workflow at build time.

#!/usr/bin/env bash
# Quick sanity-check: does the official library already expose a `8.4` tag?
curl -fsSL "https://registry.hub.docker.com/v2/repositories/library/php/tags/8.4" | jq '.name' || echo "Tag not found"

74-85: ```shell
#!/bin/bash
set -e

echo "=== build-php job (including matrix) ==="
rg -n "build-php:" -A10 .github/workflows/deploy.yml || true

echo
echo "=== build-openlitespeed job (including matrix) ==="
rg -n "build-openlitespeed:" -A10 .github/workflows/deploy.yml || true

echo
echo "=== All php_version definitions in .github/workflows/deploy.yml ==="
rg -n "php_version:" .github/workflows/deploy.yml || true


</details>
<details>
<summary>.github/workflows/test.yml (1)</summary>

`17-17`: **Same caution as in the deploy workflow: make sure `php:8.4` is actually pull-able**  
The unit-test workflow will also fail early if the tag is missing. Consider gating the job or using an `allow-failure` strategy until 8.4 GA images land.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

Comment thread .github/workflows/test.yml
@alaminfirdows alaminfirdows merged commit bc4817b into flywp:main Jul 17, 2025
18 of 23 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Jan 22, 2026
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.

2 participants