tag-audit

To check tag and version alignment, you need to audit your package.json version against local and remote git tags. This process surfaces mismatches like missing tags or version gaps to prevent release conflicts and deploy drift.

Semantic-release can cause tag misalignment when package.json versions, local tags, and remote tags fall out of sync. Auditing these components detects drift and provides remediation steps for common scenarios like tags pointing to wrong commits.

The best way to prevent release drift in CI/CD pipelines is conducting regular tag audits. By verifying consistency between package.json and remote tags before releases, you can detect and fix version misalignment early.

Yes, tag auditing works with both semantic-release and manual workflows. It inspects package.json versions alongside local and remote tags to provide remediation suggestions for discrepancies, fitting both npm packages and app deployments.

You need to audit git tags for version control during pre-release checks, post-release validations, and ongoing health audits. This ensures package.json versions align with local and remote tags to prevent deploy drift.

To fix missing git tags or tags at wrong commits before a release, run an audit to detect mismatches between package.json and remote tags. The audit provides step-by-step remediation suggestions to resolve these specific drift scenarios.