chore: arm versioning

[FoseFx]

This reverts commit d524afd.

[felixevers]

@MaxSchaefer I think we can finally check this pr.

[MaxSchaefer]

@use-to a review is okay. But why should we arm versioning yet?

[felixevers]

@use-to a review is okay. But why should we arm versioning yet?

As you already said, services is production ready. We could wait one more day before or at least for #271

[MaxSchaefer]

@use-to a review is okay. But why should we arm versioning yet?

As you already said, services is production ready. We could wait one more day before or at least for #271

Nope MVP (view). services will be released after web.

[felixevers]

@use-to a review is okay. But why should we arm versioning yet?

As you already said, services is production ready. We could wait one more day before or at least for #271

Nope github.com/orgs/helpwave/projects/14/views/2. services will be released after web.

Why "Nope"? As I said we can wait for one more day or so...

[MaxSchaefer]

@use-to a review is okay. But why should we arm versioning yet?

As you already said, services is production ready. We could wait one more day before or at least for #271

Nope github.com/orgs/helpwave/projects/14/views/2. services will be released after web.

Why "Nope"? As I said we can wait for one more day or so...

The MVP project-board is a good indicator when services is ready as an MVP. All issues of this board must be addressed before we can merge this pull request. 🙌

[MaxSchaefer]

@FoseFx could we arm this but instead of failing the CI we emit a warning?

[FoseFx]

GitHub action warnings are not present enough to justify this. (Evident by the fact that this PR has a massive amount of warnings, which I had to go looking for to notice)
Additionally, we might want to add a comment to the PR using a bot account or sth.