mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-21 17:36:59 -05:00
developer: dependencies: document upgrades on stable branches
This commit is contained in:
parent
b10a9127dd
commit
9ab29a27fa
1 changed files with 12 additions and 0 deletions
|
@ -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)).
|
||||
|
|
Loading…
Reference in a new issue