Our latest tags track master. We don't currently have a stable tracking tag.
This github workflow runs every couple of days, gets the last known tagged release from git metadata, pulls that image from dockerhub if it exists, and creates/updates a tag which represents the latest release.
openapitools/openapi-generator-online:latest-releaseopenapitools/openapi-generator:cli-latest-releaseopenapitools/openapi-generator:online-latest-release
Review github workflow docs for details on secrets usage.
Secrets are already setup and ready for this to be merged.
fixes #3840 (closed)
cc @OpenAPITools/generator-core-team
PR checklist
-
Read the contribution guidelines. -
If contributing template-only or documentation-only changes which will change sample output, build the project before. -
Run the shell script(s) under ./bin/(or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc). -
File the PR against the correct branch: master,4.3.x,5.0.x. Default:master. -
Copy the technical committee to review the pull request if your PR is targeting a particular programming language.