Update to newer LTS?

[joelmccracken]

I'd like to use this on my project, but I would need to update to a newer LTS. Would that be accepted upstream, assuming all else is well? I have never updated an LTS on a big project so I don't totally know what to do.

[akshaymankar]

Hey @joelmccracken, yes it would be accepted if you do it. Since this code is generated, you'll have to do it in the openapi-generator. You can look at OpenAPITools/openapi-generator#4068 for inspiration.
Once the PR to the openapi-generator gets merged, you'll have to change the commit SHA in the settings file and regenerate the code as documented in the README.
Please feel free to reach out here if you face any issues while doing so.

[joelmccracken]

thanks!

[jonschoning]

ill put in a PR to update https://github.com/kubernetes-client/gen since the newest version of openapi generator no longer depends on a ParseTime instance which will make moving to a newer LTS easier

[jonschoning]

updating to newer openapi generator, don't need to update /gen.
#75

[fejta-bot]

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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jonschoning]

/remove-lifecycle stale

[jonschoning]

@joelmccracken I realize much time has passed, but with #75 I don't think there should be as many blockers to move to a later LTS if needed; please let me know if you still would like to keep this issue open

[joelmccracken]

Sure that's probably fine. I ended up working around this, so I don't know if I will be able to use i any time soon. If I have issues in the future i'll reopen or file a new ticket.