@voltagex I mean, my interpretation is that they want to smooth the migration path from GitHub to Forgejo/Gitea by using Act, and there's no requirement to use Actions; I use Woodpecker on my Forgejo instance. Not saying implementing Actions is the best choice; just that I understand a plausible rationale.
@mattcen Yeah I understand it on that level too, but I am frustrated by lots of different software following the same decisions and not trying anything new.
@voltagex FWIW I have this working if you want help debugging. I wonder if the "unknown version" is provided as extra context but isn't necessarily meaning that it is the cause of the problem (which of course would mean the error is poorly explained regardless)
I am not sure I want to chase this across three projects.
The root cause seems to be that I compiled Forgejo from source (needed an arm64 build, the downloads were unavailable) and it's tagged the build with a git version instead of a semver.
Of course, API versions not binary versions should be checked.
@mattcen 2024/01/21 21:33:19 ...ations/migrations.go:633:Migrate() [F] Migration Error: Your database (migration version: 284) is for a newer Gitea, you can not use the newer database for this old Gitea release (280).
Add comment