Deployment & Versioning

[meinte]

We need to select a tool for versioning, which allows easy versioning of the frontend:

• updates package.json version
• creates tag
• creates changelog

We need to decide on versioning strategy. If its semver, it can be automatically versioned by using conventional commits
https://dev.to/coderarchive/semver-and-conventional-commits-4omc

BUT, as discussed, it makes sense to version the frontend against the eventuras framework versioning. This would mean that major versions of backend services correspond to frontend major version. (frontend version 3.4.1 for instance, should have no trouble communicating with an API at 3.9.3, but would expect to break when the API has a major change to v4). Major version in this case signifies breaking changes / incompatibility with previous versions. If we don't link FE versions to backend service versions we need to be very diligent in mapping frontend versions to backend versions.

Finally, all this ties in with deployment strategy, and possible Ci/Cd workflows.