Created by: Jonas1893
Follow up from discussion here: https://github.com/OpenAPITools/openapi-generator/pull/13667#discussion_r992466220
Currently we only allow dependency resolution to resolve Alamofire 5.4.3 and possible future patch versions of 5.4. Since Alamofire is using semver we can safely optimistically resolve to next major version instead without the danger of breaking API changes. Consuming projects can still opt-in whether to use an older version, currently they are forced to use the old 5.4.* versions.
This PR optimistically pins Alamofire to next major version allowing cocoapods / SPM to resolve everything from version 5.4 until and not including version 6.
PR checklist
-
Read the contribution guidelines. -
Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community. -
Run the following to build the project and update samples: Commit all changed files. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example./mvnw clean package ./bin/generate-samples.sh ./bin/utils/export_docs_generators.sh./bin/generate-samples.sh bin/configs/java*. For Windows users, please run the script in Git BASH. -
File the PR against the correct branch: master(6.3.0) (minor release - breaking changes with fallbacks),7.0.x(breaking changes without fallbacks) -
If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request. -> @jgavris (2017/07) @ehyche (2017/08) @Edubits (2017/09) @jaz-ah (2017/09) @4brunu (2019/11)
Declaration
The program was tested solely for our own use cases, which might differ from yours.