Skip to content

krel missed release notes from PRs #4125

@Vyom-Yadav

Description

@Vyom-Yadav

What happened:

While generating release notes using krel, it skipped some PRs:

It is not clear why these PRs were skipped (even in the subsequent krel runs, release notes from these PRs were reverted by autogen). Investigate why krel didn't include these PR in the release notes draft.

What you expected to happen:

PRs to be included by krel.

How to reproduce it (as minimally and precisely as possible):

There isn't a straightforward way. But modifying krel to use a k8s clone and a sig-release clone with those PRs as dummy in the k8s clone might help reproducing the issue.

Anything else we need to know?:

This was manually fixed in the release notes here: kubernetes/sig-release@5756634

Environment:

  • Cloud provider or hardware configuration:
  • OS (e.g: cat /etc/os-release):
  • Kernel (e.g. uname -a):
  • Others: krel release-notes on main

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/release-engIssues or PRs related to the Release Engineering subprojectkind/bugCategorizes issue or PR as related to a bug.needs-prioritysig/releaseCategorizes an issue or PR as relevant to SIG Release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions