FunctionalHacker/forgejo-asciidoc
FunctionalHacker/forgejo-asciidoc
1
0
Fork 0
Code Issues Pull requests Actions Packages Releases Activity

Fixes to README

Browse source
This commit is contained in:
Marko Korhonen 2024-04-04 08:49:48 +03:00
parent ca4bfafdad
commit 8b5f8f9701
Signed by: FunctionalHacker
GPG key ID: A7F78BCB859CD890
1 changed files with 2 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.adoc
View file

@ -31,7 +31,7 @@ IS_INPUT_FILE = false
== Updates
The image will be link:/FunctionalHacker/forgejo-asciidoc/actions[built automatically] when I make changes to it,
or every day at midnight EET if there are new patch releases available upstream.
or every day at midnight EET/EEST if there are new patch releases available upstream.
link:https://codeberg.org/forgejo/forgejo/issues/984[Forgejo doesn't supply a latest] tag so whenever there is a new major (X.y) or minor (y.X) release, I will have to manually update it when I have to time, so there might be a longer delay in those cases.
If you want to get notified when there is a new version available, you can subscribe to the link:https://t.me/korhonen_cc[Korhonen.cc News Telegram channel].
@ -42,6 +42,7 @@ A notification will be sent there whenever a new image is built.
Images are tagged following upstream versioning, with the addition of the `latest` tag for convenience.
As mentioned in xref:updates[the previous section], Forgejo doesn't support or encourage the usage of the latest tag, because upgrades might require manual intervention.
If you decide to use the `latest` tag, be sure to read the link:https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.md#1-21-6-0[upstream release notes] before upgrading.
* `latest` - The latest available release from upstream
* `x.y` - The latest release for any given minor version
* `x.y.z` - A patch release