Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
590: ci: use major version for actions/setup-java r=saig0 a=korthout ## Description <!-- Please explain the changes you made here. --> Changes the version used for actions/setup-java in all workflows to major version `v3`. This should reduce the amount of effort needed to update this action (i.e. no more dependabot pull requests unless a new major version is released). It should also avoid problems when actions/setup-java removes a specific patch release tag (as has happened before, see pull request mentioned below). Using a major version is possible because GH recommends moving the major release tags along with the minor and patch releases of that same version. Note that this may result in reduced reproducibility. However, since all tags can be moved, the only way to guarantee reproducibility is by pinning specific commit shas. Since we don't necessarily depend on a specific version, we should trust the maintainers of the action to adhere to semver. ## Related issues <!-- Which issues are closed by this PR or are related --> discussed in #589 (comment) <!-- Cut-off marker _All lines under and including the cut-off marker will be removed from the merge commit message_ ## Definition of Ready Please check the items that apply, before requesting a review. You can find more details about these items in our wiki page about [Pull Requests and Code Reviews](/~https://github.com/camunda-cloud/zeebe/wiki/Pull-Requests-and-Code-Reviews). * [ ] I've reviewed my own code * [ ] I've written a clear changelist description * [ ] I've narrowly scoped my changes * [ ] I've separated structural from behavioural changes --> ## Definition of Done <!-- Please check the items that apply, before merging or (if possible) before requesting a review. --> _Not all items need to be done depending on the issue and the pull request._ Code changes: * [ ] The changes are backwards compatibility with previous versions * [ ] If it fixes a bug then PRs are created to backport the fix Testing: * [ ] There are unit/integration tests that verify all acceptance criterias of the issue * [ ] New tests are written to ensure backwards compatibility with further versions * [ ] The behavior is tested manually Documentation: * [ ] Javadoc has been written * [ ] The documentation is updated Co-authored-by: Nico Korthout <nico.korthout@camunda.com>
- Loading branch information