Skip to content

Comments

adding olm.bundle image/relatedImages pullspec format validation#1905

Merged
openshift-merge-bot[bot] merged 1 commit intooperator-framework:masterfrom
grokspawn:validate-bundle-image-pullspecs
Feb 23, 2026
Merged

adding olm.bundle image/relatedImages pullspec format validation#1905
openshift-merge-bot[bot] merged 1 commit intooperator-framework:masterfrom
grokspawn:validate-bundle-image-pullspecs

Conversation

@grokspawn
Copy link
Contributor

Assisted-By: Claude

Description of the change:

Motivation for the change:

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /docs
  • Commit messages sensible and descriptive

@codecov
Copy link

codecov bot commented Feb 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.47%. Comparing base (a40ca89) to head (114eeb7).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1905      +/-   ##
==========================================
+ Coverage   57.44%   57.47%   +0.03%     
==========================================
  Files         139      139              
  Lines       13323    13334      +11     
==========================================
+ Hits         7653     7664      +11     
  Misses       4488     4488              
  Partials     1182     1182              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@grokspawn grokspawn force-pushed the validate-bundle-image-pullspecs branch 3 times, most recently from 5b788c0 to 3bb33ee Compare February 17, 2026 23:20
Signed-off-by: grokspawn <jordan@nimblewidget.com>
Assisted-By: Claude
@grokspawn grokspawn force-pushed the validate-bundle-image-pullspecs branch from 3bb33ee to 114eeb7 Compare February 17, 2026 23:33
Bundles: []Bundle{newTestBundle("foo", "0.1.0", func(b *Bundle) {
b.RelatedImages = []RelatedImage{
{Name: "bundle", Image: testBundleImage("foo", "0.1.0")},
{Name: "operator", Image: "quay.io/operator-framework/my-operator@ssha256:abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234abcd1234"},
Copy link
Contributor

Choose a reason for hiding this comment

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

I feel like the same kind of invalid pull spec is being used here and in line 517. But here it's an invalid pull spec, and for the test case in 517 its an unsupported digest. Is there a difference between these two cases that we care about?

@perdasilva
Copy link
Contributor

/approve

just a small nit - let me know if you want to address it and I'll re-approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 23, 2026
Copy link
Contributor

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

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

Great 🎉

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 23, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 23, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [camilamacedo86,perdasilva]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 81aee76 into operator-framework:master Feb 23, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants