@@ -148,7 +148,7 @@ Now, a wild bug occures and you have to fix that on production!
With the normal workflow you would need to fix that, merge it into master and trigger a normal release.
But this will release everything that is on stage right now!
To avoid this, you can do this hotfix flow, which follows [this recipe](https://github.com/semantic-release/semantic-release/blob/master/docs/recipes/maintenance-releases.md):
To avoid this, you can do this hotfix flow, which follows [this recipe](https://github.com/semantic-release/semantic-release/blob/master/docs/recipes/release-workflow/maintenance-releases.md):
Let's assume your current "good" version on prod is `v2.4.3`
It's important that this version is the latest `patch` version so (v2.4.4 does not exist). This is usually in praxis, as you want to release bugfixes as soon as possible usually.
