If you’re like me, you probably need to update your image tag to this new major version. I’ll probably wait for a minor release first.
You must log in or # to comment.
This is the first time we’re hearing of this, what is Forgejo/ what’s it used for??
15.0 adds support for OIDC tokens being handed to Actions workflows compatible with GitHub Actions. I was excited to upgrade because I wanted to continue doing cosign Docker image signing, but then I found out that the Cosign transparency log doesn’t support Forgejo. Looks like I need an alternative.
My next biggest problem is the Actions workflow itself. I setup Docker in Docker, but turns out there’s a bit of work in preparing the runners to be on par with what I used on GitHub.
Otherwise, I’ve found Forgejo to be quite good and almost all my private repos are moved over.
Damn I feel like I only just upgraded to v14. Those guys develop fast.
An amazing project. Good work devs.
Amy Idea why there isn’t a “:latest” release?
It might be OK now, but for a while there before they hard forked, you set yourself up for issues if you updated majors without being aware of breaking changes.
Forgejo was initially a soft fork of Gitea but they knew it would very possibly become a hard fork. Using the latest tag meant your setup could break unexpectedly so I think they’d opted to not use it at all. What you want to do is use the full version “15” in this case which will keep it updated up the currently major release.
Thoughts on this versus tangled besides this being more mature? Also question, I have cloudflare serving as my ddns, I believe some settings I have configured there prevent ssh from working to my forgejo instance. Is it a security risk to allow ssh traffic properly? I have other services on the same subdomain published as well if that matters.
Edit: would Tailscale be a solution here?
Tangled seems to focus on the “social” aspect by being inherently federated using the protocol Bluesky uses.
Federation is in the works for Forgejo but it’s not a focus.
