We default release level to stable in api.go, but when releasing a new library, it defaults to v0.1.0 in bump. This is conflicting.
If we "discover" each new API request and added to sdk.yaml with release-level set to "preview". We should be fine. Otherwise, we are again forced to update sdk.yaml for a new API onboarding.
In Java "release level" is not used in actual code generation, however it is used to generate a badge and a banner in README.md (e.g. java-chat/README.md).
Curious if any other languages use "release level" for more than repo-metadata?
We default release level to stable in api.go, but when releasing a new library, it defaults to v0.1.0 in bump. This is conflicting.
If we "discover" each new API request and added to sdk.yaml with release-level set to "preview". We should be fine. Otherwise, we are again forced to update sdk.yaml for a new API onboarding.
In Java "release level" is not used in actual code generation, however it is used to generate a badge and a banner in README.md (e.g. java-chat/README.md).
Curious if any other languages use "release level" for more than repo-metadata?