Github Action-Release Helm Charts is failing

[zhanggbj]

Which jobs are failing?

https://github.com/kubernetes/cloud-provider-vsphere/actions/runs/12347309309/job/34454202551#step:5:107

Which tests are failing?

Release Helm Charts

Looking up latest tag...
Discovering changed charts since 'v1.32.0-rc.0'...
Installing chart-releaser on /opt/hostedtoolcache/cr/v1.6.1/x86_64...
Adding cr directory to PATH...
Packaging chart 'charts/vsphere-cpi'...
Successfully packaged chart in /home/runner/work/cloud-provider-vsphere/cloud-provider-vsphere/charts/vsphere-cpi and saved it to: .cr-release-packages/vsphere-cpi-1.32.1.tgz
Releasing charts...
Error: error creating GitHub release vsphere-cpi-chart-1.32.1: POST https://api.github.com/repos/kubernetes/cloud-provider-vsphere/releases: 403 Resource not accessible by integration []
Usage:
  cr upload [flags]

Since when has it been failing?

Last successful run is 1 month ago

Testgrid link

No response

Reason for failure (if possible)

No response

Anything else we need to know?

No response

Relevant SIG(s)

/sig

[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

[kundan2707]

/remove-lifecycle stale

[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

[zhanggbj]

/remove-lifecycle stale