Update to Forgejo 7? #884
Labels
No labels
administration
Akkoma
Android
Bare metal
bug
Communication
Community
Cryptpad
Discussion
Documentation
duplicate
enhancement
etherpad
Feature request
Feedback
finances
Fixed
forgejo
fun_project
Goal 2024
help wanted
housekeeping
Howto
In progress
🤔️ Investigate
Invoice Ninja
ios
jitsi
lacre
Lacre Test
ldap
Lemmy
LibreTranslate
low prio
Lufi
macos
Mail
Merch
monitoring
movim
needs_refine
New Auth
Nextcloud
nice to have
on hold
proposal
question
Ready
refined
Roundcube
searX
SPAM Issues
spam-protection
Staging Server
sysadmin
Themes
TOR
upstream issue
Urgent!
Website
windows
wontfix
xmpp
Yearly Report
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Disroot/Disroot-Project#884
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When will this instance update to Forgejo 7.0? It was released almost a month ago
It is already in progress; check here and here.
The deploy will most probably happen during June, but please note that things still need to be tested (e.g. locally and/or on staging environment) before going into production; better later than messing up the production environment (as version 7 introduced breaking changes and also some bugs, taking into account the number of issues fixed between 7.0.0 and 7.0.3).
@kita if all goes well it will happen on deployment window on 4th June. It took longer because of the work on preparing a staging server.
@floss4good thanks!
Thank you for the updates
There is some issue with the production which we need to solve before rolling update as it may get even more nasty. So we did not do it this Tuesday. Once the issue is solved the update will be rolled out right away.
We finally got on top of things and its updated to 7.0.4 (7.0.4 will be rolled out coming tuesday). There is a little issue though, seems like we have lost the repo-avatars upon work but this has happen at least 4 days ago and we werent aware of it until the update and restart of the service, so you will need to update avatar of your repo if you are missing one.