-
Notifications
You must be signed in to change notification settings - Fork 401
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
[Bug] OLM annotation make bundle/redhat manual #1313
Labels
bug
Something isn't working
help wanted
Extra attention is needed
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Comments
NissesSenap
added
bug
Something isn't working
needs triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Nov 21, 2023
NissesSenap
added
help wanted
Extra attention is needed
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
and removed
needs triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
labels
Nov 21, 2023
Should have mentioned that, I currently remove those two lines manually when creating a release. |
I missed that this issue already existed: #1245 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
help wanted
Extra attention is needed
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Describe the bug
As a part of the release cycle we are running
make bundle/redhat
, this generatesbundle/metadata/annotations.yaml
.This file currently contains
We should either remove scorecard or start to enable it as a part of the https://github.com/k8s-operatorhub/community-operators PRs.
The release channel is currently
alpha
, so I manually had to change it tov5
.This should be fixed during some generation or in some other manifests. This way we don't have to do it manually.
Version
N/A
To Reproduce
make bundle/redhat
Expected behavior
The scorecard annotation shoulden't be added.
Suspect component/Location where the bug might be occurring
Please provide this if you know where this bug might occur otherwise leave as
unknown
Somewhere in
config/
The text was updated successfully, but these errors were encountered: