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.

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

Re-enable dependency report generation in v2.3.x #4820

Open
richardcase opened this issue Feb 26, 2024 · 2 comments
Open

Re-enable dependency report generation in v2.3.x #4820

richardcase opened this issue Feb 26, 2024 · 2 comments
Labels
needs-priority triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
v2.6.0

Comments

@richardcase
Copy link
Member

We are temporarily disabling the dependency report in the release notes generation for the release-2.3 branch due to an issue with the change to use go 1.21. We need to enable this again in the next release.

See #4812 & #4819
@k8s-ci-robot k8s-ci-robot added needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 26, 2024
@richardcase
Copy link
Member Author

/triage accepted
/milestone v2.3.next

@k8s-ci-robot k8s-ci-robot added this to the v2.3.next milestone Feb 26, 2024
@k8s-ci-robot k8s-ci-robot added 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 Feb 26, 2024
@richardcase richardcase mentioned this issue Feb 26, 2024
Merged
5 tasks
@richardcase
Copy link
Member Author

/milestone v2.6.0

@k8s-ci-robot k8s-ci-robot modified the milestones: v2.3.next, v2.6.0 Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-priority triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
v2.6.0
Development

No branches or pull requests
2 participants
@richardcase @k8s-ci-robot