Tag Troubleshooting

🚀Tag Troubleshooting

Support Guide

Resolve existing-tag conflicts, version errors, missing files, pre-tag validation, and incorrect local tags.

Commandcusty tag

📦Category

Git Operations

🚀Quick Command

custy tag [OPTIONS]

---

troubleshootingversion errorstag conflicts

---

Overview

Stop before publishing any unexpected tag. Confirm local and remote state, then correct version or validation inputs before retrying.

⚠️Never replace a published tag casually

Moving or replacing a shared tag can invalidate release expectations and automation. Follow the repository's explicit correction policy.

---

The Tag Already Exists

Inspect the existing tag locally and remotely:

Terminal

bash

git show --decorate <tag>
git ls-remote --tags origin <tag>

Choose another approved version or follow your team's documented replacement procedure. Do not force a replacement without knowing whether it is published.

---

Custy Cannot Determine the Next Version

Confirm the strategy, existing tags, version file, and required strategy inputs. Use an explicit --tag when the release version is already known.

---

The Version File Is Missing

Correct [tool.custy.cli.paths].version_file or pass --version-file with an existing writable file.

---

Pre-Tag Validation Fails

Read the first validation error and correct repository or branch state. The currently advertised --skip-checks option is not reliably propagated by the adapter, so it should not be used as a recovery mechanism.

---

The Wrong Local Tag Was Created

Do not publish it. Inspect whether the tag exists on a remote, preserve relevant working-tree changes, and follow the team's safe local-tag correction process.