Skip to content

MGDAPI-6741 update Mariner midstream to use replaces rather than skipRange #291

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

MGDAPI-6741 update Mariner midstream to use replaces rather than skipRange #291

wants to merge 1 commit into from

Conversation

valerymo
Copy link
Contributor

@valerymo valerymo commented Oct 5, 2025

@3scale-robot 3scale-robot added the needs-kind Indicates a PR or issue lacks a `kind/foo` label and requires one. label Oct 5, 2025
@3scale-robot
Copy link
Contributor

There are no kind on this issue.
Please add an appropriate kind by using one of the following commands:

  • /kind bug
  • /kind cleanup
  • /kind documentation
  • /kind feature
  • /kind <kind-name>

Instructions 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.

@3scale-robot 3scale-robot added needs-priority Indicates a PR or issue lacks a `priority/foo` label and requires one. size/XS Requires less than an hour to complete the PR or the issue. needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. and removed needs-size Indicates a PR or issue lacks a `size/foo` label and requires one. labels Oct 5, 2025
@valerymo valerymo mentioned this pull request Oct 5, 2025
Open
@roivaz
Copy link
Collaborator

roivaz commented Oct 8, 2025

Hi @valerymo. Why is this change in the upstream bundle needed? The upstream project uses the file based catalog format and the upgrade paths are declared in a separate file. See https://github.com/3scale-sre/marin3r/blob/main/catalog/marin3r/stable-channel.yaml.
If midstream needs this information in the bundle itself the approach should be to add it directly in the midstream repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

needs-kind Indicates a PR or issue lacks a `kind/foo` label and requires one. needs-priority Indicates a PR or issue lacks a `priority/foo` label and requires one. size/XS Requires less than an hour to complete the PR or the issue.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@valerymo @3scale-robot @roivaz