[renovate]

Description

Renovate proposes this dependency update under the family preset. The table below lists each package and its version change, and the release notes follow.

Pre-Merge Verification Checklist

The bot ticks nothing; CI runs the repository's required gate on this pull request; items no check decides (3D tests among them) still need a reviewer's look.

• Local verification passed: make verify-all
• No new HISS / NASA Power-of-10 infractions (all new/modified functions
  $\le 60$ LOC)
• 3D Tests included (Positive, Negative, Boundary) for public APIs
• Agent contexts in sync: standardsctl compile-context --verify
• Commit messages adhere to Conventional Commits format

This PR contains the following updates:

Package	Type	Update	Change
ubuntu (source)	final	digest	c098726 → 6a06111

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

Run configuration

• Source mode: Auto
• Repository: VMAFx/pelorus
• Branch: master
• File: .coderabbit.yaml
• Commit: 312ee3e
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: 74b27844-fc78-4854-a9e7-b0d15abf0743

Commits

Reviewing files that changed from the base of the PR and between 5367024 and c2d256c.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

No actionable comments were generated in the recent review.

Walkthrough

The assembled stage in the base container configuration now uses a different pinned Ubuntu 26.04 image digest. Other container configuration remains unchanged.

Changes: Container image update

Layer / File(s)	Summary
Update assembled-stage image digest .devcontainer/base/Containerfile	The assembled stage now uses a different pinned Ubuntu 26.04 image digest.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · previous review c1e72

The pinned base-image update has no identified merge-blocking risk.

Architecture risk: Low · up to c1e72

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .devcontainer/base/Containerfile: The assembled stage’s Ubuntu 26.04 base image digest changed from c098726d… to 6a06111c….

Pre-merge checks: 5

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: updating the pinned Ubuntu 26.04 Docker image digest.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 5b2dd420-207a-4633-a8a2-a90a771e2e64

Commits

Reviewing files that changed from the base of the PR and between e79218a and c1e7283.

Files selected for processing: 1

• .devcontainer/base/Containerfile

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

✅ No blocking issues noticed

No blocking findings were identified. The intent agent recommended validating the development-container build and confirming unrelated configuration remains unchanged; both scenarios are currently unverified.

Test suggestions

• Build the development container successfully using the updated pinned Ubuntu image.
• Verify that unrelated container configuration remains unchanged.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Build the development container successfully using the updated pinned Ubuntu image.
2. Verify that unrelated container configuration remains unchanged.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[lusoris]

Both test suggestions are covered by this PR's own checks.

• Container builds on the new base image: the "Dev container image / Build pelorus-dev (no push)" job built the image from the updated digest and passed: https://github.com/VMAFx/pelorus/actions/runs/41654900499/job/125982487142
• Nothing else changes: the diff is the single FROM ubuntu:26.04@sha256:... line in .devcontainer/base/Containerfile (one line out, one line in). No other configuration is touched.

[sourcery-ai]

Reviewer's Guide

Configuration

Update the pinned Ubuntu 26.04 base-image digest used to assemble the devcontainer.

• .devcontainer/base/Containerfile L22

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.