Skip to content

Conversation

Caesarsage
Copy link
Contributor

@Caesarsage Caesarsage commented Sep 7, 2025

Description

Added 1.34.0 release (2025-08-27) to schedule

validated with schedule builder

  1. Updating schedule.yaml and eol.yaml This updates the upcoming release section (max at 3)
image
  1. For Patch Release Schedule:
image

Issue

#52220

Closes: #52220

@k8s-ci-robot k8s-ci-robot added the area/release-eng Issues or PRs related to the Release Engineering subproject label Sep 7, 2025
@k8s-ci-robot k8s-ci-robot added sig/docs Categorizes an issue or PR as relevant to SIG Docs. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/release Categorizes an issue or PR as relevant to SIG Release. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 7, 2025
Copy link

netlify bot commented Sep 7, 2025

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 398004b
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/68c296d173cdac00082f5e4c
😎 Deploy Preview https://deploy-preview-52269--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just checking - is this data updated using the "schedule-builder" tool mentioned at the top of the file?

# Use "schedule-builder" to maintain this file:
# https://github.com/kubernetes/release/tree/master/cmd/schedule-builder
# For example by running:
# schedule-builder -uc data/releases/schedule.yaml -e data/releases/eol.yaml

Copy link
Contributor Author

@Caesarsage Caesarsage Sep 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, @dipesh-rawat I followed this

https://github.com/kubernetes/release/tree/master/cmd/schedule-builder.

However, I discovered the tool doesn't automatically detect new major releases. I had to manually add the 1.34 entry to the schedule.yaml file first, then ran schedule-builder -uc data/releases/schedule.yaml -e data/releases/eol.yaml to validate the format and maintain consistency across the schedule.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added screenshots following the "schedule-builder".

Thanks @dipesh-rawat

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Caesarsage Could you please re-run the schedule-builder tool again to refresh the results? Yesterday’s patch version releases (v1.34.1, v1.35 etc) may have now made the current data in PR a little stale.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes @dipesh-rawat

done that.

Thanks

@xirehat
Copy link
Member

xirehat commented Sep 11, 2025

Hi @Caesarsage,

To finalize this PR, please squash commits of this PR into one commit.

https://kubernetes.io/docs/contribute/new-content/open-a-pr/#squashing-commits

Thanks!

- Add initial release schedule for Kubernetes 1.34
- Update upcoming release information using schedule-builder
- Include patch release details for 1.34
@Caesarsage Caesarsage force-pushed the add-k8s-1.34-release-schedule branch from f2d51b7 to 398004b Compare September 11, 2025 09:30
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Sep 11, 2025
@Caesarsage
Copy link
Contributor Author

Hi @Caesarsage,

To finalize this PR, please squash commits of this PR into one commit.

https://kubernetes.io/docs/contribute/new-content/open-a-pr/#squashing-commits

Thanks!

yes. Thanks

@dipesh-rawat
Copy link
Member

Hello @kubernetes/release-managers - small request to review this PR updating the releases schedule file.

(LGTM from docs perspective based on the data being rendered correctly in Preview pages)

Copy link
Contributor

@Verolop Verolop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

thanks!

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 11, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 1173ddbbac4b3f9bb00154d7548f5a295bedda6b

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Verolop

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:

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 k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 11, 2025
@k8s-ci-robot k8s-ci-robot merged commit 4bb0f40 into kubernetes:main Sep 11, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/docs Categorizes an issue or PR as relevant to SIG Docs. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

There is no release information for 1.34.
5 participants