quality-hotfix-workflow

A production hotfix workflow orchestrates emergency fixes for critical S1/S2 incidents. You need it when resolving urgent production issues that require rapid patches with mandatory code review, branching from production tags, smoke tests, and release governance.

To execute a production hotfix, create a branch from the production tag, implement the minimal fix scope, run smoke tests for regression validation, enforce mandatory code review, merge to main and develop branches, and emit a patch release with changelog updates.

Yes, the hotfix workflow enforces branching directly from production tags to ensure safe isolation of the fix. This approach maintains release integrity by separating the emergency fix from ongoing development work.

No, you must implement the minimal fix scope without introducing extra alterations. Keeping the hotfix isolated prevents unintended side effects during critical S1/S2 incident resolution and ensures faster, safer patch releases.

The best way to maintain consistency is merging the reviewed hotfix into both main and develop branches. This ensures the emergency fix propagates across all active development lines and prevents future regression of the resolved incident.