Update to ubuntu-latest for building images

[tekante]

Summary by CodeRabbit

• Chores
  • Updated the automated build environment to the latest stable system, ensuring continued reliability and access to modern system enhancements while keeping the overall workflow unchanged.

[coderabbitai]

Walkthrough

This pull request updates the GitHub Actions workflow used for building images. The configuration has been modified to change the runner environment from ubuntu-20.04 to ubuntu-latest, ensuring that the build now uses the most current Ubuntu release. All other aspects of the workflow—including job structure, cron schedules, secret handling, and the PHP matrix strategy—remain unchanged.

Changes

File(s)	Change Summary
.github/workflows/default.yml	Updated runner from ubuntu-20.04 to ubuntu-latest; all other logic remains unchanged.

Poem

Hop along, dear friends, with glee so bright,
I found a change in our build site.
Ubuntu now is the latest knight,
Guiding our code with fresh light.
A rabbit’s hop celebrates this update in flight!

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between bd2ef1d and 755cdeb.

📒 Files selected for processing (1)

• .github/workflows/default.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (5)

• GitHub Check: Build: 8.3
• GitHub Check: Build: 8.2
• GitHub Check: Build: 8.1
• GitHub Check: Build: 8.0
• GitHub Check: Build: 7.4

🔇 Additional comments (3)

.github/workflows/default.yml (3)

21-21: Verify build compatibility.

Since the workflow builds PHP images from 7.4 to 8.3, let's verify that all required build dependencies are available on the latest Ubuntu runner.

❌ Verification inconclusive

🏁 Script executed:

#!/bin/bash
# Description: Check if the workflow has been running successfully with ubuntu-latest
# Look for recent workflow runs and their status

gh api -X GET /repos/$GITHUB_REPOSITORY/actions/workflows/default.yml/runs \
  --jq '.workflow_runs[] | select(.head_branch == "master") | {status: .status, conclusion: .conclusion, created_at: .created_at}' \
  | head -n 10

Length of output: 315

---

Action Required: Adjust the Branch Filter for Accurate Verification

The GitHub CLI API call returned a 404 error because it filtered for workflow runs on the "master" branch, which likely does not match the active branch (e.g., "main"). As a result, we couldn’t confirm whether the Ubuntu runner has all the necessary build dependencies for building PHP images from 7.4 to 8.3.

• The API call using --jq '.workflow_runs[] | select(.head_branch == "master") | ...' did not return any data.
• It’s recommended to update the branch filter (or run the query on the active branch) to confirm that the workflow runs use the "ubuntu-latest" environment with the expected dependencies.
• Additionally, a manual review or test build can help ensure all required build dependencies are available.

---

21-21: LGTM! The change to ubuntu-latest is appropriate.

The update from ubuntu-20.04 to ubuntu-latest aligns with best practices for maintaining up-to-date build environments.

Note: As of February 2025, ubuntu-latest maps to Ubuntu 22.04. Let's verify this:

✅ Verification successful

🌐 Web query:

What Ubuntu version does 'ubuntu-latest' currently map to in GitHub Actions?

💡 Result:

As of February 11, 2025, the ubuntu-latest label in GitHub Actions maps to Ubuntu 24.04 LTS. This transition was completed on January 17, 2025[1][4], following a phased rollout that began December 5, 2024[1][7].

Key details about the transition:

• Previous default: Ubuntu 22.04 (used until January 17, 2025)[1][8]
• Rollout period: December 5, 2024 - January 17, 2025[1][7]
• Long-term support: Ubuntu 24.04 LTS will receive maintenance updates until June 2029[6]

Developers can still explicitly target older versions using:

runs-on: ubuntu-22.04 # For previous LTS
runs-on: ubuntu-20.04 # For older version

The change brings updated toolchains but removes several pre-installed packages to maintain disk space SLAs[1][7]. Users should audit workflows for compatibility with Ubuntu 24.04's reduced package set[4][7].

Citations:

• 1: https://www.yellowduck.be/posts/github-actions-will-update-ubuntu-latest-to-ubuntu-24-04
• 2: https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/
• 3: https://juliusgamanyi.com/2022/04/27/run-github-actions-workflows-locally-using-act/
• 4: https://dev.to/siddhantkcode/critical-changes-coming-to-github-actions-ubuntu-24-migration-guide-oo8
• 5: https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions
• 6: https://wiki.ubuntu.com/Releases
• 7: https://github.com/actions/runner-images/
• 8: Ubuntu-latest workflows will use Ubuntu-22.04 actions/runner-images#6399
• 9: https://github.blog/changelog/2022-11-09-github-actions-ubuntu-latest-workflows-will-use-ubuntu-22-04/
• 10: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners

---

Update: ubuntu-latest now maps to Ubuntu 24.04 LTS

The PR’s update to use ubuntu-latest is valid—it now points to Ubuntu 24.04 LTS (as of February 2025), not Ubuntu 22.04. Be aware that this major platform update might affect pre-installed packages; if your workflow relies on specific packages, consider explicit version pinning or testing compatibility.

---

21-21: Consider version pinning trade-offs.

While using ubuntu-latest ensures you get the latest updates and security patches, it may lead to unexpected changes when GitHub updates the runner image. Consider if explicit version pinning would be more appropriate for your use case.

To help make this decision, let's check GitHub's runner update frequency and policy:

✅ Verification successful

🌐 Web query:

How often does GitHub update the 'ubuntu-latest' runner image? What is their policy for major version updates?

💡 Result:

GitHub updates the ubuntu-latest runner image weekly with software updates[1][3][7], while major OS version migrations follow a structured policy:

Update Frequency

• Weekly software updates: Tools/package versions are refreshed every week through automated deployments[1][3][7]
• OS version updates: Follow a phased migration process over 1-2 months when moving ubuntu-latest to new major versions[1][4]

Major Version Update Policy

Aspect	Policy Details
Announcement	Major changes announced 2 weeks in advance via GitHub Changelog/blog[1][4][8] High-risk changes get 1-month notice[1][3]
Migration Process	Gradual rollout over 1-2 months[1][4] Example: Ubuntu 24 migration occurred Dec 5, 2024 - Jan 17, 2025[4]
Deprecation	Older images deprecated after new GA release[1][3] Includes scheduled brownouts before final removal[1][3]
Fallback	Users can pin workflows to specific versions (ubuntu-22.04) for stability[1][4][10]

Key Considerations

• Default tools/versions may change during OS migrations (e.g., Node.js 16 removed in Ubuntu 24)[8]
• Pre-installed packages are periodically trimmed (Ubuntu 24 lost ~30% of previous packages)[4]
• Users must audit workflows before major migrations and test against new OS versions[4]

The current ubuntu-latest (as of February 2025) points to Ubuntu 24.04 following its GA release in late 2024[1][4]. GitHub maintains only the two latest GA versions simultaneously[1][3].

Citations:

• 1: https://github.com/actions/runner-images/
• 2: https://github.com/marketplace/actions/update-semver
• 3: https://github.com/actions/runner-images/blob/main/README.md?plain=1
• 4: https://dev.to/siddhantkcode/critical-changes-coming-to-github-actions-ubuntu-24-migration-guide-oo8
• 5: https://github.com/marketplace/actions/update-major-version
• 6: https://talk.jekyllrb.com/t/building-error-on-github-actions/9471
• 7: Frequency of Kotlin updates actions/runner-images#5199
• 8: https://github.blog/changelog/2024-09-25-actions-new-images-and-ubuntu-latest-changes/
• 9: https://docs.gitlab.com/runner/
• 10: https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners

---

Review Feedback: Evaluating the Use of ubuntu-latest

The web query confirms GitHub updates the ubuntu-latest runner image on a weekly basis—with automated software patches—and follows a structured process for major OS version migrations (with advance announcements and gradual rollouts). This means:

• Pros of ubuntu-latest: You always gain the latest patches and tool updates automatically.
• Cons: There’s an inherent trade-off in that major version changes (even if gradual and announced) can potentially introduce unexpected changes in pre-installed packages and tool versions.

In summary, if your workflows can tolerate these periodic changes, using ubuntu-latest is acceptable. However, if you require a more stable, predictable environment, you may want to pin to a specific version (e.g., ubuntu-24.04 or ubuntu-22.04).

• File: .github/workflows/default.yml (Line 21: runs-on: ubuntu-latest)

---

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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 or @coderabbitai title 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.