From 9ab29a27fab891979a635d7a31c7d41f990ddefa Mon Sep 17 00:00:00 2001 From: Earl Warren Date: Thu, 4 Jul 2024 09:30:58 +0200 Subject: [PATCH] developer: dependencies: document upgrades on stable branches --- docs/developer/dependencies.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/developer/dependencies.md b/docs/developer/dependencies.md index cc0976b7..cc024e71 100644 --- a/docs/developer/dependencies.md +++ b/docs/developer/dependencies.md @@ -11,6 +11,8 @@ Software referenced by a release (even if such a release is the hash of a commit ## Decision to upgrade +### Development branch + An upgrade is justified if: - it is beneficial to Forgejo @@ -18,6 +20,16 @@ An upgrade is justified if: There is no need to upgrade if there is no indication that it is beneficial to Forgejo. +### Stable branch + +The [dependency +dashboard](https://codeberg.org/forgejo/forgejo/issues/2779) can be +used to create a pull request for an upgrade on a stable branch. It is +not done automatically. + +An upgrade is justified if it follows the restrictions that apply to +stable branches (not backporting features for instance). + ## Reviewing renovate pull requests Pull [requests are opened](https://codeberg.org/forgejo/forgejo/pulls?poster=165503) when an upgrade is available and the decision to merge (positive review) or not (request for change review) depends on what the upgrade offers. The history of past upgrades can be browsed by looking for PR with the same title (e.g. [happy-dom upgrades](https://codeberg.org/forgejo/forgejo/pulls?q=Update+dependency+happy-dom)).