CI: semver and releases

[JustSamuel]

Description

The goal of this PR is to create automagic versioned releases of the monorepo and its libraries. They will be released in the form of {{app}}:{{monorepo version}}. The releases will be atomically done when merging into main based on sementic-release commits analyzer:

(Squashed) PRs with commits containing:

• fix: will cause a patch release
• feat: will cause a feature release (minor)
• BREAKING CHANGE: will cause a major release

Related issues/external references

none afaik.

Types of changes

• CI/CD (Changes to the CI/CD configuration)

[SuperVK]

If I read the yaml's correctly, the docker image ci run and push to pkg.gewis.nl on pushing to main. Now with the fast-forward this should not trigger, but if we do want to push it will trigger and still push to main tag on docker. Is this intended?

[JustSamuel]

If I read the yaml's correctly, the docker image ci run and push to pkg.gewis.nl on pushing to main. Now with the fast-forward this should not trigger, but if we do want to push it will trigger and still push to main tag on docker. Is this intended?

Yes, in this construction we will also have a rolling main, develop, sudopos-ab (which is develop)

You can decide to not do it, but since not every push releases a version it might be nice to have a "always latest of the branch". I.e someone did a wrong commit (ci but actually contained a bugfix( which can then be instant deployed if needed.

[rinkp]

I have not tested the GH actions, but i am in favor of this idea.

Please note that you are renaming an action that is mandatory for PRs so upon merging this, please update the branch protection rules accordingly

[rinkp]

Please note that you are renaming an action that is mandatory for PRs so upon merging this, please update the branch protection rules accordingly

[SuperVK]

lets test it!

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀