You must log in or # to comment.
From the Matrix Forgejo Room:
Attention: We currently advise against upgrading to Forgejo 17.0.0. An issue is currently being investigated that prevents pushing, merging, or other code operations in some cases.
If you haven’t updated yet, please wait until the issue has been investigated more thoroughly, if possible.
Oh man - thanks for this. Just realized my server still had v10 which is long discontinued for support. Updating the docker was really easy and now I’m on v15, their current Long Term Support version.
Go FOSS!
Donate if you like Forgejo
I love Forgejo, it’s SO freaking good. However, I really need it to have issue retagging when moving them between different kanban columns and a proper API to manage it all from elsewhere.
You should open an issue for this if it doesn’t exist yet, or, if possible, attempt a pull request. The maintainers are kind, welcoming and helpful from my experience.
Might pay to wait a minor or two before repinning your compose file, Forgejo has had issues on the first release of a major.
Does it have to be a minor, though?
Generally, yes! I couldn’t resist though and merged the renovate PR - seems fine so far. (It’s my local single user instance and I could easily restore, so it hasn’t been particularly high stakes)
You updated f’jo with renovate? Badass.
Yeah, I keep forgejo’s compose file in forgejo. Changing the file triggers my Komodo which pulls the new file and applies it. It may interrupt a pipeline triggered by the merge or similar, but it’s generally fine.
I’m non-container - too much time in security - but that’s a wicked workflow. Well done.
too much time in security
By this, do you mean there’s a lot of work with security when running in a container?
How does the latest release compare to the LTS?
Guess you’d need to check the release notes from v16 as well, though some stuff might be backported
