search

kubernetes-client / c

Official C client library for Kubernetes
Apache License 2.0
147 stars 46 forks source link

v0.11.0 release plan #248

Open ityuhui opened 1 week ago

ityuhui commented 1 week ago

Release plan for v0.11.0:

  1. Regenerate the C client based on Kubernetes 1.31 via GitHub Action https://github.com/kubernetes-client/c/actions/workflows/generate.yml Parameters for the action:

    • Use workflow from: Branch master
    • The remote kubernetes release branch to fetch openapi spec. e.g. "release-1.28": release-1.31
    • The commit to use for the kubernetes-client/gen repo: master
    • The commit to use for the OpenAPITools/openapi-generator repo. e.g. "v7.0.0": master
    • Semvar to use for the version number: 0.11.0 PR: https://github.com/kubernetes-client/c/pull/249

  2. Update Versioning and Compatibility PR: TBD

  3. Release the C client v0.11.0 guided by RELEASE.md Create the branch: release-0.11

    git checkout -b release-0.11
git push origin release-0.11

    Release action: https://github.com/kubernetes-client/c/actions/workflows/release.yml Parameters for release action:

    • Use workflow from: Branch release-0.11
    • The release version of this release. Must be a semantic version of the form X.Y.Z: 0.11.0
    • Dry run, will not push tags to branch and release: No Release announcement: TBD

FYI @brendandburns

ityuhui commented 1 week ago

Hi @brendandburns

The auto-generated action https://github.com/kubernetes-client/c/actions/runs/11193825680/job/31119593597 failed due to missing permissions of github-actions[bot]:

remote: Permission to kubernetes-client/c.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/kubernetes-client/c/': The requested URL returned error: 403
Error: Process completed with exit code 128.

It seems "Read and write permissions" are disabled in Settings -> Actions -> General -> Workflow permissions (https://github.com/kubernetes-client/c/settings/actions)

Do you have any suggestions for this issue?

brendandburns commented 1 week ago

@ityuhui see this issue here: https://github.com/kubernetes/org/issues/5126

For now, I think the best we can do as a workaround is to run the github action in your fork of the repo, and then send a PR from that fork to this repo. That's what I did recently for the Java repo:

https://github.com/kubernetes-client/java/pull/3680

ityuhui commented 6 days ago

Thanks @brendandburns, I'll give it a try.