Recommended format
Use semantic tags like v1.2.0 or v2.0.1.
Avoid reusing tags; ReleaseMind treats a tag as a release boundary.
Prefer annotated tags for release clarity and traceability.
- Use consistent prefixes (v) across repos
- Include pre-releases when needed (v1.3.0-rc.1)
- Keep tag names short and predictable
Hotfix tags
For hotfixes, create a new patch tag and generate a fresh draft.
Keep hotfix notes short and focused to avoid confusing the main release stream.
Link the hotfix tag to the same release branch if you maintain one.
Avoid common pitfalls
Do not move tags after publication; it breaks audit trails.
Avoid mixing build metadata into tag names unless it is consistent.
Review and introspect
Tag consistency makes every release easier to trust.
- Is your tagging scheme consistent across all repos?
- Do you need a lightweight tagging policy for your team?
- Are hotfixes clearly separated from regular releases?