Release Crawler has stopped running

[jberkus]

@mfahlandt the release crawler hasn't run for the last two weeks, since we patched it with the date fix. Should I revert the changes?

[mfahlandt]

It appears it is not the code, but smith changed in the permissions

https://github.com/kubernetes-sigs/lwkd/actions/runs/10444759394/job/28919685969

The report was generated but it cannot open the pr.

I don't know if I have the rights to fix it. I will be back on Friday

[jberkus]

Huh, I have no idea what's going on here. Why would GH's bot not have permissions to push (as me)?

[mfahlandt]

@jberkus i think i found out what is the issue

Something changed apparently in August:

These are the rights we need:

And This is what we have:

It seems only you can change this @jberkus as i'm missing the rights

For reference: actions/checkout#417

[jberkus]

I can't change it either. I suspect this is a factor in our Enterprise Account. Will raise with GH-Admin

[chrischdi]

This are the default permissions. Isn't it possible to set enable write permissions directly in the action yaml? As we do e.g. here:
https://github.com/kubernetes-sigs/cluster-api/blob/main/.github/workflows/pr-dependabot.yaml#L13-L14

[mfahlandt]

@chrischdi i tested it it still needs the checkbox set to create Pullrequests - you also can see this in this error line: https://github.com/kubernetes-sigs/lwkd/actions/runs/11365048163/job/31612364491#step:6:568

[jberkus]

I've raised this in github-management, but nobody is sure what to do, yet.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jberkus]

/remove-lifecycle stale

[chrischdi]

Maybe related: kubernetes/org#5126 (comment)