Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] : create hotfix on previous version #241

Open
alxreed opened this issue Oct 30, 2022 · 4 comments
Open

[FEATURE] : create hotfix on previous version #241

alxreed opened this issue Oct 30, 2022 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@alxreed
Copy link

alxreed commented Oct 30, 2022

Is your feature request related to a problem? Please describe.

With the current version of cocogitto it's not possible to make a hotfix on a previous version. For example, if my acceptance environnement is on 6.8 version and my preproduction / production versions are on 6.7 i can't make a 6.7.1 version only 6.8.1.
It is really frustrating to have to make those fixes by hand when you have a production issue and you need to be as fast as you can.

Describe the solution you'd like
It would be super nice to be able to hotfix previous version(s)

@alxreed alxreed added the enhancement New feature or request label Oct 30, 2022
@oknozor
Copy link
Collaborator

oknozor commented Jan 19, 2023

This is now easier to implement since tag are now sorted in SemVer order instead of date.

Use case

The git log below show a fix commit living on a branch between 1.0.0 and 1.1.0.

* 08c2f5d (HEAD -> master, tag: v1.1.0) chore(version): v1.1.0
* a6ddf88 feat: some feature
* 9bef8f2 (hotfix-branch) fix: fix some prod bug // unreleased hotfix
| * b07f3ed (HEAD -> master, tag: v1.0.0) chore(version): v1.0.0
|/

We should be able to produce a hotfix tag doing the following:

  1. git checkout hotfix-branch
  2. cog bump --auto | cog bump --patch etc

Implementation notes

  • cocogitto should get latest tag starting from current worktree HEAD instead of trying to get all tags.
  • Version number should be generated with normal tag validation (i.e: {{version}} > v1.0.0).
  • Additional tag validation : {{version}} < next_tag_starting_from(v1.0.0) (do not assume next tag = latest tag)
  • Should support auto bump and manual bump failing with safety checks.
  • Must not be the default behavior and should be enabled via a dedicated flag (--from-worktree, --unsafe, --force maybe ? )
  • Generated changelog should convey the idea that generated tag is not the latest one. Probably using someting like "Patched version" in the changelog heading.
  • We need to check that this is not breaking tag to tag git traversal ( patched tag version commits won't be reachable from the later tags). In the example above 9bef8f2 is not reachable from 08c2f5d

@lukehsiao
Copy link
Contributor

As another reference, semantic-release is a popular way to manage releases from conventional commits, and their workflow is described here:

https://semantic-release.gitbook.io/semantic-release/recipes/release-workflow/maintenance-releases

@mofojed
Copy link

mofojed commented Jun 28, 2024

I'm confused - I'm looking for this feature as well, and it seems to be missing in Cocogitto. But then there is documentation for for hotfix in Bump Profiles: https://docs.cocogitto.io/guide/#bump-hooks
Why is a hotfix Bump Profile shown when hotfix doesn't work?
Looks like this may also be addressed with an open PR? #324

@oknozor
Copy link
Collaborator

oknozor commented Jul 2, 2024

@mofojed bump profile allow you to run arbitrary command pre and post cocogitto release.
Because of that you can achieve hotfix using standard git commands within a specific bump profile.

That said hotfix is not a builtin cocogitto command yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants