Skip to content

chore(stash): add stash image digest - #2167

Merged
jfroy merged 1 commit into
mainfrom
stash-digest
Aug 8, 2026
Merged

chore(stash): add stash image digest#2167
jfroy merged 1 commit into
mainfrom
stash-digest

Conversation

@jfroy

@jfroy jfroy commented Aug 8, 2026

Copy link
Copy Markdown
Owner

No description provided.

@daddy-ro

daddy-ro Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

konflate — summary

Note

+0 added · 2 changed · −0 removed — 2 resources · 2 apps

Tip

Routine — only container-image and chart-version changes; nothing else changed.

Image changes

image from to
ghcr.io/jfroy/stash v0.31.1-cudajellyfin sha256:720df0459b84…

View the full rendered diff →

konflate · rendered 2bc70da · advisory, not a gate

@coderabbitai

coderabbitai Bot commented Aug 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jfroy, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 39 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 94db716f-846f-4b35-8b0d-a186156a5df8

📥 Commits

Reviewing files that changed from the base of the PR and between c303bf9 and 2bc70da.

📒 Files selected for processing (1)
  • kubernetes/apps/default/stash/app/helmrelease.yaml

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

Comment @coderabbitai help to get the list of available commands.

@claude

claude Bot commented Aug 8, 2026

Copy link
Copy Markdown

Looks correct. The tag: <version>@sha256:<digest> form matches how the rest of the repo pins images (e.g. nams a few lines below in this same file), the plain scalar needs no quoting since it starts with v, and nothing else in the app changes.

One thing I couldn't check from the review sandbox (no registry egress): that sha256:720df0459b84722d086cf6cacb2248d451aa7491eba13d88c1c956f052df21e0 is the digest ghcr.io/jfroy/stash:v0.31.1-cudajellyfin currently resolves to, and that it's the multi-arch index digest rather than a single-platform manifest digest. If it was taken from crane digest/docker buildx imagetools inspect on the tag, it's fine; if it came from a per-platform docker inspect, the pod would fail to pull on any other node arch. Worth a quick confirm before merge since a wrong digest here means ImagePullBackOff on next reconcile.

@jfroy
jfroy merged commit a50f54c into main Aug 8, 2026
3 checks passed
@jfroy
jfroy deleted the stash-digest branch August 8, 2026 05:46
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.

1 participant