Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(bugfix) Update to handle mermaid visualization for deprecation of multiple packages #1173

Conversation

rashmigottipati
Copy link
Member

PR to add colorblind-friendly color indicators for deprecation of each scope (bundle, package and channel) was merged last week. Based on this review comment, previously merged PR presumes that we will only ever have at most one deprecated package. This PR fixes that by handling the case of a declarative config includes multiple deprecated packages.

Signed-off-by: Rashmi Gottipati <chowdary.grashmi@gmail.com>
Copy link
Contributor

openshift-ci bot commented Dec 12, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, rashmigottipati

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 12, 2023
Signed-off-by: Rashmi Gottipati <chowdary.grashmi@gmail.com>
@rashmigottipati
Copy link
Member Author

Closing this as this is not a bug and we're indeed handling the deprecation of multiple packages in this PR #1172 as

if depByPackage.Has(filteredChannel.Package) {
is within the channel loop and we're bound to hit every single package that is being deprecated and capture it as deprecated.

@rashmigottipati rashmigottipati deleted the bugfix-deprecation branch December 12, 2023 20:32
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants