saenyakorn/monorepo-versioning-gitops

Versioning workflows on Monorepo and deploy the services with GitOps concept

Hi there 👋

Hi! I'm Saenyakorn Siangsanoh, a 3rd-year Computer Engineering student, Chulalongkorn University.

I'm a full-stack front-end engineer passionate about software development. In addition, I can do and understand UX/UI design. I love to collaborate with others and support social activities. Recently, I have learned more about DevOps and Infrastructure to comprehend everything software developers should know to serve the best products to users. I'm also interested in Data Science and Data Analyst to make myself do more ultimate features and be more capable.

Programming Languages

Frameworks

Designs

Github Stats

monorepo-versioning-gitops's Issues

How to handle hotfix releases to production?

Let's say I have published my apps to production and have begun working on the next release on beta. Now I have realized there is a minor bug on production but all my changes on staging have not been properly tested yet and are too risky to push to production. So I would like to be able to create a branch from the last release on main fix the super minor bug and deploy that change to production?

I am trying to understand how the versioning would work given that production might be on version 1.0.0 and beta may be on 1.0.1-beta.0. Simply versioning and deploying a hotfix to production would make it 1.0.1 and somehow beta then needs to get bumped to 1.0.2-beta.0?

Or is there a way I can version production hotfix to 1.0.0-hotifx.0? But the problem here is creating any changeset for the hotfix release will cause it to become 1.0.1-hotfix.0 if I try to use a hot fix prerelease....

Any ideas on how to handle this scenario?