Versioning and release design for Medulla packages

[dariuswatson]

Summary

Currently Medulla packages are manually push to Github container registry (ghcr.io), opening design proposal to establish versioning/tagging strategy with automate build and publishing workflow.

Motivation and goals

• Currently packages are published and tagged with "latest"
• Pinned versions will allow users to pull previous release

In scope

Medulla packages:

• controller
• database-service
• database-designer
• database-sync

Out of scope

Packages outside of Medulla project

Risks / unknowns

Tagging and releases should be fully automated

Examples

Ability to pull down previous image builds for example: docker pull ghcr.io/recro/medulla/controller:v1.0.0

Detailed design

• Implement semantic versioning of packages
• Releases and tagging strategy will be automated within pipeline
• Build failures will not release new versions of packages
• All Medulla packages will have the same build version to be packaged as a full release

[andrewbabbittdev]

Partially completed in #251 but still needs additional container builds on completion of PRs.