Option to use an older version without facing y/n prompt?

[KenzoB73]

I have had to revert to an older version of the tool in order to get workitem migration working on some projects. I am also trying to automate this process in a pipeline, but whenever I run with the older tool I get the below prompt. Is there a way to supress this?

You are currently running version 11.12.23.0 and a newer version (13.0.8.0) is available. You should upgrade now using Chocolatey command 'choco upgrade vsts-sync-migrator' from the command line.
Do you want to continue? (y/n)

[MrHinsh]

You can add skipVersionCheck to the args on the command line to skip it!

azure-devops-migration-tools/src/MigrationTools.Host/StartupService.cs

Lines 47 to 58 in 9e3509a

	if (latestVersion > version && args.Contains("skipVersionCheck"))
	{
	_logger.LogWarning("You are currently running version {Version} and a newer version ({LatestVersion}) is available. You should upgrade now using Chocolatey command 'choco upgrade vsts-sync-migrator' from the command line.", version, latestVersion);
	#if !DEBUG
	Console.WriteLine("Do you want to continue? (y/n)");
	if (Console.ReadKey().Key != ConsoleKey.Y)
	{
	_logger.LogWarning("User aborted to update version");
	throw new Exception("User Abort");
	}
	#endif
	}

[KenzoB73]

Hi, that arg check doesn't appear to exist in v 11.12.23

azure-devops-migration-tools/src/MigrationTools.Host/StartupService.cs

Lines 46 to 57 in 06db817

	if (latestVersion > version)
	{
	_logger.LogWarning("You are currently running version {Version} and a newer version ({LatestVersion}) is available. You should upgrade now using Chocolatey command 'choco upgrade vsts-sync-migrator' from the command line.", version, latestVersion);
	#if !DEBUG
	Console.WriteLine("Do you want to continue? (y/n)");
	if (Console.ReadKey().Key != ConsoleKey.Y)
	{
	_logger.LogWarning("User aborted to update version");
	throw new Exception("User Abort");
	}
	#endif
	}

[MrHinsh]

We do not support older versions of the tooling. This was added 10 months ago in v13.1.1

You should update to the latest version of the tooling.

[MrHinsh]

To use an older version you would need to modify the code yourself and build a custom version.