Skip to content

Releasability check flags GO when it shouldn't #174

@slinkydeveloper

Description

@slinkydeveloper

Not sure where I have to open this, so I'll open here:

There is a bug in the automation that flagged some repos as ready to be cutted [6] but they were not [7], because pointing at the wrong eventing release. There is a similar bug that happened to eventing-awssqs, making it depend on hack master because it was an indirect dependency.

[6] https://github.com/knative-sandbox/eventing-natss/actions/runs/480133288
[7] knative-extensions/eventing-natss@6a1c1d9#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R21

From https://groups.google.com/g/knative-dev/c/jQsloZD-sW8/m/8E31LeFGCgAJ

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions