[ubuntu-image] research: update Ubuntu runner image analysis for 20260622.220.1#41373
Conversation
Updated research/ubuntulatest.md with the latest GitHub Actions Ubuntu runner image data from image version 20260622.220.1 (June 22, 2026). Key changes from previous analysis (20260413.86.1): - Kernel: 6.17.0-1010-azure → 6.17.0-1018-azure - Go cached: 1.22.12, 1.23.12, 1.24.13, 1.25.9 → 1.24.13, 1.25.11, 1.26.4 - Node.js (n): 22.22.2, 24.14.1 → 22.23.0, 24.17.0 - Python: 3.13.13, 3.14.4 → 3.13.14, 3.14.6 - Ruby: 4.0.2 → 4.0.5 - Java: 8.0.482+8 → 8.0.492+9, 11.0.30+7 → 11.0.31+11, 17.0.18+8 → 17.0.19+10, 21.0.10+7 → 21.0.11+10, 25.0.2+10 → 25.0.3+9 - Rust: 1.94.1 → 1.96.0 - Maven: 3.9.14 → 3.9.16 - Gradle: 9.4.1 → 9.6.0 - AWS CLI: 2.34.30 → 2.35.10 - AWS SAM CLI: 1.158.0 → 1.162.1 - Azure CLI: 2.85.0 → 2.87.0 - Google Cloud CLI: 564.0.0 → 573.0.0 - .NET SDKs: updated patch versions - CodeQL: 2.25.1 → 2.25.6 - Firefox: 149.0.2 → 152.0.1 - Selenium: 4.43.0 → 4.45.0 - Miniconda: 26.1.1 → 26.3.2 - Updated Dockerfile examples with current Go 1.25.11 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
✅ Test Quality Sentinel completed test quality analysis. No test files were added or modified in this PR. PR #41373 only modifies research/ubuntulatest.md (a research markdown document). Test Quality Sentinel skipped. |
|
✅ Design Decision Gate 🏗️ completed the design decision gate check. No ADR enforcement needed: PR does not have the 'implementation' label and has ≤100 new lines of code in business logic directories. |
|
🧠 Matt Pocock Skills Reviewer has completed the skills-based review. ✅ |
|
✅ PR Code Quality Reviewer completed the code quality review. |
There was a problem hiding this comment.
Pull request overview
Updates the repository’s tracked analysis of the ubuntu-latest (Ubuntu 24.04) GitHub Actions runner image to reflect the newer runner image version 20260622.220.1, aligning the documented toolchain versions and example Dockerfile pins with the June 2026 runner state.
Changes:
- Updated the referenced runner image documentation link, image version, and kernel version.
- Refreshed key runtime/tool versions (Go, Node, Python, Ruby, Java, Rust, Maven/Gradle, cloud CLIs, browsers/drivers, .NET SDKs).
- Updated Dockerfile examples to pin Go
1.25.11.
Show a summary per file
| File | Description |
|---|---|
research/ubuntulatest.md |
Refreshes the Ubuntu runner image analysis and example version pins to match image 20260622.220.1. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 3
| **Ubuntu Version**: 24.04 LTS | ||
| **Image Version**: 20260622.220.1 | ||
| **Kernel Version**: 6.17.0-1018-azure |
| - **Available Versions**: 22.23.0, 24.17.0 (managed via n) | ||
| - **Default Version**: 20.x (system default) |
| - **Google Chrome**: 137.x (stable) | ||
| - **Chromium**: 137.x | ||
| - **Microsoft Edge**: 137.x (stable) | ||
| - **Mozilla Firefox**: 152.0.1 |
There was a problem hiding this comment.
Review: Documentation version bump — one anomaly worth noting
All version updates are consistent with the stated image upgrade (20260413.86.1 → 20260622.220.1) and match the PR description — except for the browser section.
⚠️ Browser versions appear to go backwards
Chrome/Chromium/Edge/ChromeDriver moved from 147.x to 137.x, which is a lower major version:
| Tool | Before | After |
|---|---|---|
| Google Chrome | 147.0.7727.55 | 137.x (stable) |
| Chromium | 147.0.7727.0 | 137.x |
| Microsoft Edge | 147.0.3912.60 | 137.x (stable) |
| ChromeDriver | 147.0.7727.56 | 137.x |
Chrome 137 was the stable release from ~May 2025; Chrome 147 aligns with ~April 2026. The PR description does not mention any browser version changes, and Firefox correctly moved forward (149.0.2 → 152.0.1). This suggests the analyzer workflow may have read Chrome version info imprecisely on the new runner (e.g., from a channel label rather than the installed binary). Worth investigating to ensure Chrome version detection is reliable in future updates.
🔎 Code quality review by PR Code Quality Reviewer · 42.1 AIC · ⌖ 6.87 AIC · ⊞ 5.2K
There was a problem hiding this comment.
Skills-Based Review 🧠
Applied /grill-with-docs — requesting changes on one data accuracy issue.
📋 Key Themes & Highlights
Key Themes
- Browser version anomaly: Chrome/Chromium/Edge went from 147.x → 137.x (version decrease), which conflicts with Chrome's release cadence. This appears to be a workflow capture issue worth verifying.
- Node.js default version not listed: The default Node.js version (20.x) is absent from the Available Versions list, creating a confusing gap.
- Dockerfile Go pinning: Three Dockerfile examples use 1.25.11 while the document lists 1.26.4 as the newest cached version.
Positive Highlights
- ✅ Comprehensive update across 20+ tool versions in a single PR
- ✅ PR description summarises all key changes clearly
- ✅ Dockerfile examples updated consistently across all three occurrences
- ✅ References section updated to point to the correct runner image branch
🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · 52.4 AIC · ⌖ 7.25 AIC · ⊞ 6.5K
| - **Chromium**: 147.0.7727.0 | ||
| - **Microsoft Edge**: 147.0.3912.60 | ||
| - **Mozilla Firefox**: 149.0.2 | ||
| - **Google Chrome**: 137.x (stable) |
There was a problem hiding this comment.
[/grill-with-docs] Chrome's major version appears to have gone from 147 → 137, which is a version decrease. Firefox correctly upgraded (149 → 152), but Chrome going from 147 to 137 is inconsistent with Chrome's ~4-week release cadence — version 137 corresponds to roughly August 2025, not June 2026.
💡 Details & suggested fix
The previous image (20260413.86.1) had Chrome 147.x. By June 2026 (~10 weeks later) Chrome should be at ~149+. Version strings also changed from precise build numbers (147.0.7727.55) to range notation (137.x), losing specificity.
Possible causes:
- The workflow captured Chrome's version from a different channel (e.g. Debian stable rather than the Google Chrome stable PPA)
- A
google-chrome-stable --versioncall failed silently and fell back to an older cached value
Recommended action: re-run the analyzer on the current image and verify google-chrome-stable --version returns the expected value before merging.
| - **Available Versions**: 20.20.2 (installed), 22.22.2, 24.14.1 (cached) | ||
| - **Default Version**: 20.20.2 | ||
| - **Available Versions**: 22.23.0, 24.17.0 (managed via n) | ||
| - **Default Version**: 20.x (system default) |
There was a problem hiding this comment.
[/grill-with-docs] The default Node.js version (20.x) isn't listed in the Available Versions section, which only shows 22.23.0 and 24.17.0 (managed via n). A reader can't tell whether Node 20 is still installed on the runner.
💡 Suggestion
Consider making the available versions list exhaustive, e.g.:
- **Available Versions**: 20.x (system default), 22.23.0, 24.17.0 (managed via n)
- **Default Version**: 20.xOr, if Node 20 is no longer directly installed and only available via n, clarify that in the default version note.
| ```dockerfile | ||
| # Install Go | ||
| ARG GO_VERSION=1.23.12 | ||
| ARG GO_VERSION=1.25.11 |
There was a problem hiding this comment.
[/grill-with-docs] The Dockerfile example pins Go to 1.25.11, but the document now lists 1.26.4 as the newest cached version. The same pattern repeats at lines 628 and 764.
💡 Suggestion
If the intent is to showcase the latest available version:
ARG GO_VERSION=1.26.4If 1.25.11 is intentionally kept for stability (e.g., 1.26.x is very new), add a brief comment so readers understand:
# 1.26.4 is also cached; pinning to 1.25 for stability
ARG GO_VERSION=1.25.11
Ubuntu Actions Runner Image Analysis Update
This PR updates the analysis of the default Ubuntu Actions runner image.
Changes
Key Updates
Analysis Details
Versions gathered by inspecting installed binaries, package directories, and version files on the active runner (image version confirmed via ImageVersion env var = 20260622.220.1).
Automatically generated by the Ubuntu Actions Image Analyzer workflow