From 8b5f8f970184eaf3e276615c212c1a24ce2ae4c6 Mon Sep 17 00:00:00 2001 From: Marko Korhonen Date: Thu, 4 Apr 2024 08:49:48 +0300 Subject: [PATCH] Fixes to README --- README.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.adoc b/README.adoc index d3f1578..b49ce3b 100644 --- a/README.adoc +++ b/README.adoc @@ -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