Explicitly set Maven's --no-snapshot-updates option in CI. Although certain providers may configure snapshot updates, it's unclear across our providers what would occur if we run mvn install in one command, followed by mvn verify in another during which time a SNAPSHOT release was published on master. Declaring this option provides some certainty across all providers where we follow this approach. Because we also run with --quiet, we reduce our visibility into whether CI is downloading the SNAPSHOT or using the locally cached version.
Gradle doesn't require such an option because it caches snapshot dependencies for 24 hours by default and requires either manual updates or reconfiguration to change that behavior (see https://docs.gradle.org/current/userguide/dynamic_versions.html).
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.