nx 23.2.0-beta.7 → 23.2.0-beta.8

package/dist/src/command-line/release/version/resolve-current-version.js

@@ -6,7 +6,7 @@ exports.resolveCurrentVersionFromRegistry = resolveCurrentVersionFromRegistry;
 exports.resolveCurrentVersionFromGitTag = resolveCurrentVersionFromGitTag;
 const tslib_1 = require("tslib");
 const pc = tslib_1.__importStar(require("picocolors"));
-const enquirer_1 = require("enquirer");
+const prompt_helpers_1 = require("../../../utils/prompt-helpers");
 const spinner_1 = require("../../../utils/spinner");
 async function resolveCurrentVersion(tree, projectGraphNode, releaseGroup, versionActions, logger, cachedCurrentVersionsPerFixedReleaseGroup, finalConfigForProject, releaseTagPattern, latestMatchingGitTag) {
     switch (finalConfigForProject.currentVersionResolver) {
@@ -221,15 +221,12 @@ async function handleNoAvailableDiskFallback({ logger, projectName, versionActio
         throw unresolvableCurrentVersionError;
     }
     try {
-        const reply = await (0, enquirer_1.prompt)([
-            {
-                name: 'useZero',
-                message: `\n${pc.yellow(`Warning: Unable to resolve the current version for "${projectName}" ${currentVersionSourceMessage} and there is no version on disk to fall back to. This is invalid with ${specifierSource} because the new version is determined by relatively bumping the current version.\n\nTo resolve this, ${resolutionSuggestion}, or set an appropriate version in a supported manifest file such as ${validManifestFilenames}`)}. \n\nAlternatively, would you like to continue now by using 0.0.0 as the current version?`,
-                type: 'confirm',
-                initial: false,
-            },
-        ]);
-        if (!reply.useZero) {
+        const useZero = await (0, prompt_helpers_1.confirmationPrompt)({
+            message: `\n${pc.yellow(`Warning: Unable to resolve the current version for "${projectName}" ${currentVersionSourceMessage} and there is no version on disk to fall back to. This is invalid with ${specifierSource} because the new version is determined by relatively bumping the current version.\n\nTo resolve this, ${resolutionSuggestion}, or set an appropriate version in a supported manifest file such as ${validManifestFilenames}`)}. \n\nAlternatively, would you like to continue now by using 0.0.0 as the current version?`,
+            initial: false,
+            onCancel: () => false,
+        });
+        if (!useZero) {
             // Throw any error to skip the fallback to 0.0.0, may as well use the one we already have
             throw unresolvableCurrentVersionError;
         }