chore(deps): update container image ghcr.io/anthony-spruyt/devcontainer-common to

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
ghcr.io/anthony-spruyt/devcontainer-common	final	digest	91ad096 → 9459ee4

---

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 becomes conflicted, 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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1e1e04fd-09b3-42d6-9e1c-ecd9cf002583

📥 Commits

Reviewing files that changed from the base of the PR and between eb31ab8 and 043cd13.

📒 Files selected for processing (1)

• .devcontainer/Dockerfile

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated development container base image.

Walkthrough

The .devcontainer/Dockerfile base image digest for ghcr.io/anthony-spruyt/devcontainer-common is updated to a new SHA256 hash; all subsequent build logic remains unchanged.

Changes

Dev Container Base Image Update

Layer / File(s)	Summary
Base image digest update .devcontainer/Dockerfile	The FROM directive is updated to reference a new ghcr.io/anthony-spruyt/devcontainer-common image digest; all downstream build logic and NEXUS_URL-controlled apt source routing remain unaffected.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• The change addresses the dependency update for ghcr.io/anthony-spruyt/devcontainer-common that appears to be tracked in the Renovate dependency dashboard.

Possibly related PRs

• anthony-spruyt/firemerge#267: Both PRs only change the .devcontainer/Dockerfile base image digest (no code logic or shared build stages beyond the FROM line).

Suggested labels

dependencies, docker, chore

Suggested reviewers

• anthony-spruyt
• skynet-rw

Poem

🐰 A tiny nibble of a hash so bright,
FROM line swapped in morning light,
Builds hum unchanged, the brew proceeds,
One digest swapped to meet new needs,
Hooray — the devcontainer feels just right! 🥕

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title exceeds the 50-character limit at 81 characters and appears incomplete, ending with 'to' without specifying the target digest.	Revise the title to be under 50 characters and include the complete update information, for example: 'chore(deps): update devcontainer image digest'

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description clearly explains the container image digest update from 91ad096 to 9459ee4, directly related to the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/ghcr.io-anthony-spruyt-devcontainer-common

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 default

Wonderful, this rule succeeded.

• #approved-reviews-by >= 1

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.devcontainer/Dockerfile:
- Line 2: The FROM image digest specified
(ghcr.io/anthony-spruyt/devcontainer-common@sha256:91ad096ea5994218497425bbdca0c32059bbba08e77237e4406447a46cb7bc34)
is invalid and causes pulls to 404; update the FROM line to point to a valid
image (either replace the sha256 digest with a confirmed existing digest or
revert to a stable tag like a known semantic tag), then verify by attempting
docker pull for that exact reference and ensure the devcontainer build succeeds;
update only the FROM reference (the existing token is the unique symbol to
change).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 79b0d404-c9ec-4193-aeb3-66deb3f16b0c

📥 Commits

Reviewing files that changed from the base of the PR and between 8b22c55 and eb31ab8.

📒 Files selected for processing (1)

• .devcontainer/Dockerfile

[skynet-rw]

PR updates .devcontainer/Dockerfile base image ghcr.io/anthony-spruyt/devcontainer-common from digest cd254a1 (v1.2.16) to 91ad096 (v1.2.17/latest) — devcontainer-only change, no application code affected, no breaking changes. CI fails in lint / MegaLinter but the failure is not caused by this PR: MegaLinter crashes in GithubCommentReporter.produce_report() with github.GithubException: 404 when calling pr.get_issue_comments() — the GITHUB_TOKEN in the shared _lint.yaml reusable workflow lacks pull-requests permission (token only has actions:write, contents:read, metadata:read, securityEvents:write). The actual linting completed before the reporter crash. This infrastructure failure cannot be fixed within this PR branch; the permission must be added to anthony-spruyt/repo-operator/.github/workflows/_lint.yaml. Flagged RISKY because CI is red and the fix is outside this PR scope.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-29 20:04 UTC · Rule: default
• ✅ Checks passed · on draft merge queue: embarking main (13b88f3) and #306 together #309
• ✅ Merged — 2026-05-29 20:07 UTC · at 043cd1386ae59be6531c6ca9e3a67791fceca435 · squash

This pull request spent 2 minutes 59 seconds in the queue, including 2 minutes 30 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1
  • chore(deps): update container image ghcr.io/anthony-spruyt/devcontainer-common to #306
• #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule pr-rules]
  • chore(deps): update container image ghcr.io/anthony-spruyt/devcontainer-common to #306
• -draft
  • chore(deps): update container image ghcr.io/anthony-spruyt/devcontainer-common to #306
• check-success = summary / Check Results
• all of [🛡 Merge Protections rule default]:
  • #approved-reviews-by >= 1
    • chore(deps): update container image ghcr.io/anthony-spruyt/devcontainer-common to #306
• any of [🛡 GitHub repository ruleset rule pr-rules]:
  • check-success = summary / Check Results
  • check-neutral = summary / Check Results
  • check-skipped = summary / Check Results
• any of [🛡 GitHub repository ruleset rule pr-rules]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections