Closed dprotaso closed 12 months ago
Since we use Chainguard's Kind action we'll need to make changes to their action here:
https://github.com/chainguard-dev/actions/blob/main/setup-kind/action.yaml
/assign @MeenuyD
@dprotaso: GitHub didn't allow me to assign the following users: MeenuyD.
Note that only knative members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
/assign MeenuyD
@dprotaso: GitHub didn't allow me to assign the following users: MeenuyD.
Note that only knative members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
/assign
Hello, @Priyansurout I am working on that issue I saw you are doing work that is already assigned or working on that please let me do it.
Yeah let's not assign ourselves to issues that are currently being worked on
/assign @MeenuyD /unassign @Priyansurout
sure
As per the Release Schedule
We don't need to bump the go modules - those will come through when we bump knative.dev/pkg (https://github.com/knative/pkg/issues/2821)
We should spin up 1.26 clusters in e2e https://github.com/search?q=repo%3Aknative%2Fserving%201.25&type=code
For kind testing we should drop v1.25 and add v1.28 https://github.com/knative/serving/blob/55bec5f5f8ca5f720b3eef1afe2c3a43af808916/.github/workflows/kind-e2e.yaml#L90-L92