-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ci): Switch back to actions/[email protected] #589
Conversation
The version `v3.7.0` of actions/setup-java was removed. Fix the workflows by using the previous version. See actions/setup-java#422.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting decision by them 😅
bors merge
Build succeeded: |
It might be better to switch the version to the latest major release 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. Likely it is easiest for us when using actions like these (e.g. checkout) to use the major version tag. |
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 <[email protected]>
Description
The version
v3.7.0
of actions/setup-java was removed. Fix the workflows by using the previous version. See actions/setup-java#422.Related issues
Failed action: https://github.com/camunda/zeebe-process-test/actions/runs/3626043207
Definition of Done
Not all items need to be done depending on the issue and the pull request.
Code changes:
Testing:
Documentation: