The config file was always hardcoded to .versionize. Users couldn't rename it to something like versionize.json to align with other tooling conventions (e.g. dotnet-tools.json).

Changes

• CliConfig – New --configFile <CONFIG_FILE> option
• VersionizeOptionsProvider – Config path resolution now accounts for --configFile:
  • Absolute path → used directly, --configDir ignored
  • Relative path/filename → combined with --configDir (or working directory)
  • Not specified → falls back to .versionize (existing behavior unchanged)
• Tests – Two new functional tests covering custom filename alone and combined with --configDir

Example

<Exec Command="dotnet versionize --configDir $(MSBuildProjectDirectory) --configFile versionize.json" />

Created from VS Code.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.