This is from last month, but I haven’t seen any discussion of it. Seems like Forgejo is now a hard fork of Gitea, instead of being a soft fork like it was over the previous year.

The main reason I’m posting it now is this: “As such, if you were considering upgrading to Forgejo, we encourage you to do that sooner rather than later, because as the projects naturally diverge further, doing so will become ever harder. It will not happen overnight, it may not even happen soon, but eventually, Forgejo will stop being a drop-in replacement.”

  • @rjcEnglish
    10•9 months ago

    If you deployed with docker composr you just change the image and hit redeploy. Super simple.

    • @ikiddEnglish
      3•9 months ago

      Appreciate that, sounds super easy

      • @nadirEnglish
        2•9 months ago

        It is. Did that when this was first announced

        • @ikiddEnglish
          1•9 months ago

          Huh, using their instructions for docker compose, I use docker pull codeberg.org/forgejo/forgejo:7.0.0 and it errors for manifest unknown. Removing the version tag so it default to latest doesn’t help.

          Do I need to make an account and docker login? That seems like it should be unnecessary for a simple pull.

          • chameleonOP
            2•9 months ago

            Login isn’t necessary, but there is no :latest tag published so you need to pull a version that exists. The current version is at codeberg.org/forgejo/forgejo:1.21.8-0 or at :1.21 if you want one that tracks patch updates (as found in the container registry).

            • @ikiddEnglish
              2•9 months ago

              Ah, the docs reference V.7.0.0 so that’s what I was trying with.

              TY, that got her transitioned. The config actually pops a notice that 1.21.9 is available but I don’t see that it’s in the registry yet. I do like the :latest tag because then I can use watchtower, but I can understand why some people would want to specify the version.