Automatically create github release for tagged versions

[Woazboat]

Use github actions to automatically create a release for versions tagged with v*.*.*

• Build a docker image and upload to github container repository.
• Upload pre-built binary as release artifact.

Currently based on Ubuntu 22.04 docker image

[mmd-osm]

As a heads up: This may probably not work since I’m only collaborator in this repo and cannot create personal access tokens or configure a GITHUB_TOKEN. That’s also the reason why I work mostly with my own fork, and create pull requests from there. As long as I’m working in my own repo, I don’t have that many restrictions.

[Woazboat]

I think it should work. Looking at https://github.com/zerebubuth/openstreetmap-cgimap/actions/runs/7079318119/job/19265821617#step:1:24 , the default authentication token does have package and content write permissions that are required for this.

[mmd-osm]

I think we need to double check this with zerebubuth, who owns the repo. While we might be able to publish packages, I have no way to control or manage them afterwards.

Also, we should check if publishing packages is really worth the extra effort and does not increase the overall maintenance effort. osm.org uses Ubuntu PPAs at the moment, OpenHistoricalMap is building their own Docker images, so both of our main "customers" would not see an immediate benefit.

I introduced Docker images mainly to have a bit more control on package dependencies when running unit tests. They could be also useful for some local testing. However, in general are not meant as is for production usage. Once we start publishing packages, people might have a different expectation, i.e. would expect a more "production like" image.

[Woazboat]

While we might be able to publish packages, I have no way to control or manage them afterwards.

Okay, then that's probably not a good idea.

Also, we should check if publishing packages is really worth the extra effort and does not increase the overall maintenance effort. osm.org uses Ubuntu PPAs at the moment, OpenHistoricalMap is building their own Docker images, so both of our main "customers" would not see an immediate benefit.

The main benefit of having prebuilt packages available would be for new users who want to quickly try out cgimap. Maybe that's not really worth it since that's a very limited target audience.

I introduced Docker images mainly to have a bit more control on package dependencies when running unit tests. They could be also useful for some local testing. However, in general are not meant as is for production usage. Once we start publishing packages, people might have a different expectation, i.e. would expect a more "production like" image.

We could also simply remove the docker image upload from the workflow and just have the automatic release creation (+ maybe the binary artifact).

[mmd-osm]

Now with the discussion in #381 we could attach the build artifact to the new release, similar to how https://github.com/trstringer/azblogfilter/releases looks like.

In our case this would be single .deb file for amd64 and Debian 12, at least for now. I belive this could avoid some of issues with package registries for now.

[mmd-osm]

I've included at least the softprops/action-gh-release based release process in #449 now. Thanks a lot for the PR!