Skip to content

handle cases where spec.version.release is a number instead of string#1909

Merged
openshift-merge-bot[bot] merged 1 commit intooperator-framework:masterfrom
grokspawn:release-number-fix
Feb 23, 2026
Merged

handle cases where spec.version.release is a number instead of string#1909
openshift-merge-bot[bot] merged 1 commit intooperator-framework:masterfrom
grokspawn:release-number-fix

Conversation

@grokspawn
Copy link
Copy Markdown
Contributor

@grokspawn grokspawn commented Feb 6, 2026

Assisted-By: claude

Description of the change:
explicitly handles the case where a CSV's spec.release version is represented as an int or float instead of a string.

Motivation for the change:
while the tooling in operator-framework should always steer towards CSVs which use string release values, there remain a variety of ways to generate a CSV which might result in a numerical value for release. So we need to provide a more flexible import approach to encompass these capabilities.

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

Signed-off-by: grokspawn <jordan@nimblewidget.com>
Assisted-By: claude
@openshift-ci openshift-ci Bot requested review from anik120 and kevinrizza February 6, 2026 05:12
@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 6, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 57.48%. Comparing base (a40ca89) to head (10fed99).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1909      +/-   ##
==========================================
+ Coverage   57.44%   57.48%   +0.03%     
==========================================
  Files         139      139              
  Lines       13323    13328       +5     
==========================================
+ Hits         7653     7661       +8     
+ Misses       4488     4485       -3     
  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.

Comment thread pkg/registry/csv_test.go
Spec: json.RawMessage(`{"release": true}`),
},
wantErr: true,
},
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is it worth exercising the {"release": ""} case?

@perdasilva
Copy link
Copy Markdown
Contributor

/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
Copy Markdown
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.

Nice work 🥇

@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
Copy Markdown
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 f410a39 into operator-framework:master Feb 23, 2026
13 checks passed
@grokspawn grokspawn deleted the release-number-fix branch April 2, 2026 13:44
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.

3 participants