You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using the OpenAPI spec contained in this repo in order to create a HTTP client using OpenAPI generator, as the pre-built Java SDK does not suite our needs.
Everything works like a charm, yet as a matter of production maturity, we strive for immutable builds.
As we do not wanna manually download the spec file on change, we leverage the "remoteSpec" feature of the OpenAPI Gradle plugin.
The problem
The remote spec we consume just points to the main branch if this project, making our build mutable.
Feature request
Please introduce some sort of release management to this repo, so that we can consume a tagged version of the spec.
The tag is easily accessible via GitHub core features, yet the tag just needs to be created.
Side note
Having dedicated releases might also come in handy for other use cases our API stability management at all.
Thanks
✌️
The text was updated successfully, but these errors were encountered:
Situation
We are using the OpenAPI spec contained in this repo in order to create a HTTP client using OpenAPI generator, as the pre-built Java SDK does not suite our needs.
Everything works like a charm, yet as a matter of production maturity, we strive for immutable builds.
As we do not wanna manually download the spec file on change, we leverage the "remoteSpec" feature of the OpenAPI Gradle plugin.
The problem
The remote spec we consume just points to the
main
branch if this project, making our build mutable.Feature request
Please introduce some sort of release management to this repo, so that we can consume a tagged version of the spec.
The tag is easily accessible via GitHub core features, yet the tag just needs to be created.
Side note
Having dedicated releases might also come in handy for other use cases our API stability management at all.
Thanks
✌️
The text was updated successfully, but these errors were encountered: