Define how renovate bot updates increase versions
This commit is contained in:
committed by
Linus Gasser
parent
96f4c4e5e4
commit
7144606b15
+15
-1
@@ -4,7 +4,21 @@ All contributions should be made via pull requests.
|
|||||||
|
|
||||||
## Pull Requests
|
## Pull Requests
|
||||||
|
|
||||||
A pull request can be merged directly into `main` by any maintainer. No approval is needed, but pull requests should be tested as working before merge.
|
A pull request can be merged directly into `main` by any maintainer.
|
||||||
|
No approval is needed, but pull requests should be tested as working before merge.
|
||||||
|
|
||||||
|
## Dependency Updates
|
||||||
|
|
||||||
|
- patch updates proposed from renovate bot are merged directly -
|
||||||
|
if there is a CVE, also release a new patch version of this recipe
|
||||||
|
- minor updates proposed from renovate bot are tested by one maintainer
|
||||||
|
and merged if they don't break, then a new minor version of the recipe
|
||||||
|
is released
|
||||||
|
- major updates proposed form renovate bot are tested by two maintainers
|
||||||
|
and merged if they don't break, then a major version of the recipe is
|
||||||
|
released.
|
||||||
|
If the renovate bot PR is older than one week, one maintainer can decide
|
||||||
|
to merge it anyway.
|
||||||
|
|
||||||
## Become a maintainer
|
## Become a maintainer
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user