Bump redhat-services-prod/openshift/boilerplate from image-v8.3.5 to image-v8.3.6 in /build#241
Conversation
Bumps redhat-services-prod/openshift/boilerplate from image-v8.3.5 to image-v8.3.6. --- updated-dependencies: - dependency-name: redhat-services-prod/openshift/boilerplate dependency-version: image-v8.3.6 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
area/dependency
WalkthroughThe Docker builder base image tag in the build stage is updated from Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 11 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Hi @dependabot[bot]. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dependabot[bot] The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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 `@build/Dockerfile`:
- Line 1: The Dockerfile's FROM line references a non-existent base image tag
image-v8.3.6 which will cause image-not-found failures; update the FROM
instruction to use a confirmed existing tag (for example image-v8.3.4) or
replace it with the correct registry/tag your CI uses, and if image-v8.3.6 is
intentional, confirm and document its availability in the registry so the FROM
line in the Dockerfile reflects an actual, accessible tag.
🪄 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: Repository: openshift/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 0decde72-832e-4937-a07f-0e3adac6d380
📒 Files selected for processing (1)
build/Dockerfile
| @@ -1,4 +1,4 @@ | |||
| FROM quay.io/redhat-services-prod/openshift/boilerplate:image-v8.3.5 AS builder | |||
| FROM quay.io/redhat-services-prod/openshift/boilerplate:image-v8.3.6 AS builder | |||
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Verify the current digest behind the tag on Quay (read-only)
TOKEN="$(curl -fsSL 'https://quay.io/v2/auth?service=quay.io&scope=repository:redhat-services-prod/openshift/boilerplate:pull' | jq -r '.token')"
curl -fsSI \
-H "Authorization: Bearer ${TOKEN}" \
-H 'Accept: application/vnd.docker.distribution.manifest.v2+json' \
'https://quay.io/v2/redhat-services-prod/openshift/boilerplate/manifests/image-v8.3.6' \
| tr -d '\r' | awk -F': ' '/Docker-Content-Digest/ {print $2}'Repository: openshift/managed-node-metadata-operator
Length of output: 66
🌐 Web query:
quay.io redhat-services-prod openshift boilerplate image-v8.3.6 docker
💡 Result:
I couldn’t verify the exact image reference you provided: quay.io/redhat-services-prod/openshift/boilerplate:image-v8.3.6. What I could verify from authoritative sources is: - The upstream OpenShift boilerplate repository uses image tags named image-v{X}.{Y}.{Z} and documents that those tags correspond to build images produced from Konflux/CI [1]. - In the boilerplate repository, the latest release I found is image-v8.3.4 (published 2026-02-25) [2]. I did not find any public evidence (in the searched sources) that an image-v8.3.6 release exists as of today (2026-05-11). So, with high confidence based on the sources above: - Image-v8.3.6 is not confirmed publicly in the boilerplate release tags I found; the most recent confirmed boilerplate build image tag is image-v8.3.4 [2]. If you want, share the full intended docker image name format you’re using (including whether “openshift/boilerplate” is actually the repository path on Quay or whether there’s an additional component like openhshift-user-workloads, user-workloads, or a tenant namespace). Then I can re-check for the exact v8.3.6 tag under the correct Quay path.
Citations:
- 1: https://github.com/openshift/boilerplate/
- 2: https://github.com/openshift/boilerplate/releases/tag/image-v8.3.4
🏁 Script executed:
# Check if the image exists and what the previous tag was
cd build && cat -n Dockerfile | head -20Repository: openshift/managed-node-metadata-operator
Length of output: 918
🏁 Script executed:
# Try alternative approach to verify the image is valid
# Check if we can find any references to this image in the codebase
rg "quay.io/redhat-services-prod/openshift/boilerplate" --type dockerfile --type yaml --type jsonRepository: openshift/managed-node-metadata-operator
Length of output: 119
🏁 Script executed:
# Search for references to the image across the repo
rg "image-v8.3.6" --type yaml --type json --type textRepository: openshift/managed-node-metadata-operator
Length of output: 113
🏁 Script executed:
# Check if there's any changelog, release notes, or documentation about v8.3.6
fd -e md -e txt | xargs grep -l "8.3.6" 2>/dev/null | head -10Repository: openshift/managed-node-metadata-operator
Length of output: 66
Verify the base image tag image-v8.3.6 exists.
The tag image-v8.3.6 does not appear in the publicly available boilerplate releases—the latest confirmed release is image-v8.3.4 (published 2026-02-25). Builds with this tag will fail with an image-not-found error. Either use a confirmed existing tag or clarify if this version is scheduled for release and available in your registry.
🤖 Prompt for 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.
In `@build/Dockerfile` at line 1, The Dockerfile's FROM line references a
non-existent base image tag image-v8.3.6 which will cause image-not-found
failures; update the FROM instruction to use a confirmed existing tag (for
example image-v8.3.4) or replace it with the correct registry/tag your CI uses,
and if image-v8.3.6 is intentional, confirm and document its availability in the
registry so the FROM line in the Dockerfile reflects an actual, accessible tag.
|
@dependabot[bot]: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #241 +/- ##
=======================================
Coverage 58.60% 58.60%
=======================================
Files 5 5
Lines 244 244
=======================================
Hits 143 143
Misses 87 87
Partials 14 14 🚀 New features to boost your workflow:
|
1 participant
Bumps redhat-services-prod/openshift/boilerplate from image-v8.3.5 to image-v8.3.6.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by CodeRabbit