Skip to content

chore(deps): update valkey/valkey docker digest to 4963247#71

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/valkey-valkey
Open

chore(deps): update valkey/valkey docker digest to 4963247#71
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/valkey-valkey

Conversation

@renovate

@renovate renovate Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
valkey/valkey service digest c6d46374963247

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • "before 9am on monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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.

Summary by CodeRabbit

  • Chores
    • CIのバックエンドテストで使用するRedis(Valkey)のコンテナイメージ参照を更新しました。ワークフローの他の設定には変更がなく、テスト実行時に異なるValkeyコンテナイメージが起動されます。

@renovate renovate Bot added the dependencies label Jun 7, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 7, 2026

Copy link
Copy Markdown

Deploying koyori with  Cloudflare Pages  Cloudflare Pages

Latest commit: 35b208d
Status:⚡️  Build in progress...

View logs

@renovate renovate Bot force-pushed the renovate/valkey-valkey branch 28 times, most recently from 15e4176 to 2fac2b5 Compare June 9, 2026 17:53
@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: acc1056c-86e3-4056-a076-3a19f6d24c76

📥 Commits

Reviewing files that changed from the base of the PR and between 3be3c02 and 2268728.

📒 Files selected for processing (1)
  • .github/workflows/backend-test.yml

Walkthrough

GitHub Actions のバックエンドテストワークフローで、jobs.test.services.redis.image に指定された Valkey(Redis互換)コンテナイメージの SHA256 ピン留めを別のダイジェスト値へ更新しました。ワークフローの他の設定に変更はありません。

Changes

CI インフラストラクチャ

Layer / File(s) Summary
Valkey コンテナイメージのピン留め更新
.github/workflows/backend-test.yml
jobs.test.services.redis.image の SHA256 ダイジェストを更新し、テスト環境で起動される Valkey コンテナイメージを差し替えました。

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 新しいダイジェストが風に舞う
小さな変更で準備は整う
CI の朝にコンテナが走る
テストは静かに扉を開ける
さあ、ビルドよ、よく頑張ったね

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed プルリクエストのタイトルは、Valkey Dockerイメージのダイジェスト更新という変更内容を正確に反映しており、主な変更を明確に要約しています。
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/valkey-valkey

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

@renovate renovate Bot force-pushed the renovate/valkey-valkey branch from 2fac2b5 to 6a9625f Compare June 9, 2026 20:24

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 @.github/workflows/backend-test.yml:
- Line 41: The workflow references the pinned image "image:
valkey/valkey@sha256:4963247afc4cd33c7d3b2d2816b9f7f8eeebab148d29056c2ca4d7cbc966f2d9";
confirm in the workflow that this digest is intentionally pinned (keep the
digest) and add a short inline comment noting the digest is valid for the
9.1.0-trixie multi-arch tag, then add a CI step invoking a vulnerability scanner
(e.g., Trivy or Grype) after image pull to scan the full container including OS
layers so container-wide CVEs are reported; ensure the new step references the
same pinned image string so scanning and execution use the identical artifact.
🪄 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 580c8ae3-c874-4e07-a067-17bb47c3da9e

📥 Commits

Reviewing files that changed from the base of the PR and between 2fac2b5 and 6a9625f.

📒 Files selected for processing (1)
  • .github/workflows/backend-test.yml

Comment thread .github/workflows/backend-test.yml
@renovate renovate Bot force-pushed the renovate/valkey-valkey branch from 6a9625f to 3be3c02 Compare June 9, 2026 21:17
@renovate renovate Bot force-pushed the renovate/valkey-valkey branch from 3be3c02 to 2268728 Compare June 10, 2026 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants