feat: use ci/test scope for dependency updates (#88)#95
Conversation
# Description Dependency updates for workflows and test dependencies do not have to publish a new version as the changes are not end-user relevant. This PR uses the `ci` prefix for workflow dependency updates and `test` for Maven test dependencies. Semantic release will not create a new version for those updates. # Verification None. Used the examples from the documentation: https://docs.renovatebot.com/presets-default/#semanticprefixfixdepschoreothers
|
Hey @kayman-mk! 👋 Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process. Make sure that this PR clearly explains:
With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE. The following ChatOps commands are supported:
Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command. This message was generated automatically. You are welcome to improve it. |
|
Json linter fails with json5. We can ignore this and tackle the problem in Hapag-Lloyd/Workflow-Templates#27 |
|
🎉 This PR is included in version 1.6.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
3 participants
Description
Commit ef17abc accidentally deleted the changes in
default.jsonand is reintroduced with this PR.Dependency updates for workflows and test dependencies do not have to publish a new version as the changes are not end-user relevant.
This PR uses the
ciprefix for workflow dependency updates andtestfor Maven test dependencies. Semantic release will not create a new version for those updates.Closes #87
Verification
None. Used the examples from the documentation:
https://docs.renovatebot.com/presets-default/#semanticprefixfixdepschoreothers