You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,3 +41,11 @@ The release process works like this:
41
41
After fixing the code and the tests, a release candidate's tag can be overwritten by setting the option `force`
42
42
to `force-reuse-tag` when invoking the workflow. This should only be used when a release candidate is released again
43
43
should be overwritten. If the archive was already released on github, then it should be deleted first - as goreleaser will not force to overwrite it ([issue](https://github.com/goreleaser/goreleaser/issues/557)).
44
+
45
+
46
+
## Updating Dependencies
47
+
48
+
Most dependencies are automatically checked for updates via [Dependabot](.github/dependabot.yml).
49
+
50
+
The remaining dependencies cannot be managed via Dependabot, because they are manually retrieved
51
+
during release via [0-get-latest-dependencies-versions.sh](./release/0-get-latest-dependencies-versions.sh). Hence, a weekly GitHub Action [check-manual-dependencies](.github/workflows/check-manual-dependencies.yml) checks whether the committed [versions.txt](release/versions.txt) matches the actual latest versions. If there is a new version, then the build fails and the maintainers are automatically notified. To incorporate the new version, simply follow the instructions in the failed build.
0 commit comments