mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-12 17:56:16 +00:00
Merge pull request 'fix: Forgejo 7.0 is compatible with Gitea v1.21.11' (#3857) from earl-warren/forgejo:wip-gitea-compatibility into v7.0/forgejo
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/3857 Reviewed-by: Michael Kriese <michael.kriese@gmx.de>
This commit is contained in:
commit
07ad7dd8f6
2
Makefile
2
Makefile
|
@ -82,7 +82,7 @@ endif
|
|||
STORED_VERSION_FILE := VERSION
|
||||
HUGO_VERSION ?= 0.111.3
|
||||
|
||||
GITEA_COMPATIBILITY ?= gitea-1.22.0
|
||||
GITEA_COMPATIBILITY ?= gitea-1.21.11
|
||||
|
||||
STORED_VERSION=$(shell cat $(STORED_VERSION_FILE) 2>/dev/null)
|
||||
ifneq ($(STORED_VERSION),)
|
||||
|
|
1
release-notes/7.0.3/3857.md
Normal file
1
release-notes/7.0.3/3857.md
Normal file
|
@ -0,0 +1 @@
|
|||
- [PR](https://codeberg.org/forgejo/forgejo/pulls/3857): Gitea v1.22 is [not published yet](https://github.com/go-gitea/gitea/issues/30731) as of 21 May 2024 and in reality Forgejo v7.0.3 is compatible with Gitea v1.21.11. The Gitea v1.22 release was anticipated to happen shortly after [Forgejo v7.0 was published on 23 April 2024](https://forgejo.org/2024-04-release-v7-0/) because it was already in the late stages of its release candidate lifecycle. However, around 27 April, [the Gitea release candidates were dropped](https://github.com/go-gitea/gitea/issues/30731) and the release candidates restarted from the Gitea development branch.
|
Loading…
Reference in a new issue