forked from forgejo/forgejo
[crystal/release] Forgejo v1.18.5-0crystal1 #4
Labels
No Label
bug
duplicate
feature/enhancement
help wanted
invalid/wontfix
question
upstream/Forgejo
upstream/Gitea
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: crystal/forgejo#4
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Efforts have been focused on preparing Forgejo v1.19 and commits have not been pushed to the v1.18/forgejo branch since Forgejo v1.18.5's release. I am putting together a quick release with all of the backports that were planned for Gitea v1.18.6. I (and Forgejo) will consider maintaining further backports for v1.18 until such a time as we feel Forgejo v1.19 is ready for use in production on Codeberg.
release/v1.18
withv1.18/crystal
branchv1.18/crystal
ci-verify
will not proceed until there is a passing pipeline for the target commitv1.18.5-0crystal1
on forgejo-build