Bump openapi-generator version in a future pre-release

[roycaihw]

ref #1353 (comment)

There is some bug fixes in openapi-generator that we want to pick up. We should bump the generator version in an upcoming pre-release.

Currently our latest releases are v17.14.0a1 (published) and v18.17.0a1 (cut but not published yet). I don't think we want to bump the version in v17.x.0b1 because that will cause more merge conflict, plus Kubernetes 1.17 is no longer supported. Our options are either v18.x.0b1 or v19.x.0a1.

/assign
cc @yliaog

[roycaihw]

I'm working on adding some scripts to automate the release process, e.g. #1419.

I want to use the scripts to automate the client generation and release note collection for 18.0.0-snapshot in master (today it's 17.0.0-snapshot), and then we can upgrade the client generator.

[roycaihw]

/reopen

to track upgrading the generator version in this client.

[k8s-ci-robot]

@roycaihw: Reopened this issue.

In response to this:

/reopen

to track upgrading the generator version in this client.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten