Skip to main content

Version Troubleshooting

Version Troubleshooting

Support Guide

Common problems and solutions when synchronizing project versions.

Commandcusty version update

Category

Versioning

Quick Command

custy version update
troubleshootingversion

Overview​

Most Version Update issues are caused by missing configuration, missing project files, or selecting an unsupported versioning strategy.

The following guidance covers the most common situations.

Version File Not Found​

What you see

  • Version Update stops before synchronizing files.
  • A version file cannot be located.

Why it happens

  • The configured version file does not exist.
  • The path in config.toml is incorrect.
  • The project has not been initialized.

How to resolve it

  • Verify the configured version_file.
  • Ensure the file exists.
  • Run custy init if the required project structure has not yet been created.

Invalid Version Strategy​

What you see

  • Version generation fails.
  • The requested strategy is rejected.

Why it happens

  • Unsupported strategy name.
  • Invalid configuration.
  • Conflicting command-line arguments.

How to resolve it

  • Verify the configured strategy.
  • Use one of the supported strategies.
  • Remove conflicting command-line options.

Unexpected Version Format​

What you see

  • The generated version format differs from expectations.

Why it happens

  • A different strategy is being used.
  • Automatic project detection selected a different synchronization format.

How to resolve it

  • Review the configured versioning strategy.
  • Confirm the detected project type.
  • Verify whether version format conversion is expected.

Project Files Were Not Updated​

What you see

  • Some project files remain unchanged.

Why it happens

  • The files are not supported.
  • The detected project type differs from expectations.
  • The command was executed using --dry-run.

How to resolve it

  • Verify the project structure.
  • Confirm the detected project type.
  • Re-run without --dry-run if changes should be applied.

Next Diagnostic Step​

If the issue persists:

  • Review your config.toml.
  • Verify the configured version file.
  • Confirm the selected versioning strategy.
  • Run with --debug to obtain additional diagnostic information.