Update the release schedule after August patch releases

[jeremyrickard]

This PR updates the schedule to reflect the August patch release.

This was generated with:

schedule-builder -uc data/releases/schedule.yaml

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	912818a
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/66be1eb9d2c12800080e9d2d
😎 Deploy Preview	https://deploy-preview-47510--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[xmudrii]

/lgtm
/approve
/hold
we might want to use this opportunity to test #45762, if we don't get to merge it soon, unhold this PR

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xmudrii

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• data/releases/OWNERS [xmudrii]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 55222f1275a379ac72948d1861f5db43655d5ec2

[Arhell]

lgtm

[sftim]

#45762 has merged; is this still needed?

[xmudrii]

@sftim The workflow still didn't run, we're keeping this PR open as an alternative if we can't get the workflow working (soon). That said, is it possible to manually retrigger the workflow with the latest changes?

[sftim]

That said, is it possible to manually retrigger the workflow with the latest changes?

Maybe. It wouldn't be me doing that though as I have stepped back from being a SIG Docs tech lead.

[jeremyrickard]

@katcosgrove @salaxander could ya'll take a look at the Github action that merged with #45762 and see if you can re-trigger it? This should ideally automatically update the patch release schedule.

If we can't get that to run, then we need to merge this PR.

Thanks!

[sftim]

Cc @tengqm (also a tech lead)

[katcosgrove]

@jeremyrickard I have manually triggered the job, and it fails on re-run.

From the logs, attempting to push to k/website returns 403.

[sftim]

@katcosgrove you could try manually triggering it afresh; the behavior changed in 4365f3e which is more recent than the most recent scheduled run.

To trigger the workflow for main, click Run workflow from https://github.com/kubernetes/website/actions/workflows/update-schedule.yml

[katcosgrove]

That surfaces a different error:

https://github.com/kubernetes/website/actions/runs/10457332314

GH Actions is not permitted to create or approve pull requests.

[xmudrii]

Apparently this must be configured on the repo level: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#preventing-github-actions-from-creating-or-approving-pull-requests

By default, when you create a new repository in your personal account, workflows are not allowed to create or approve pull requests. If you create a new repository in an organization, the setting is inherited from what is configured in the organization settings.

Do we have to reach out to GH Admins for this?

[katcosgrove]

I believe so. Tech leads definitely don't have the necessary access.

[xmudrii]

We can't get the action working, so let's proceed with this PR
/hold cancel