Refactor error messages in command runner and interactive runner to r… (#98)

* Update Jenkinsfile to allow publishing when building a tag in addition to the existing publish parameter.

* 2.7.6-alpha.4

* Refactor error messages in command runner and interactive runner to remove user-specific context, ensuring consistency in error reporting. Update unit tests to reflect changes in error handling.

* 2.7.6-alpha.5

* Enhance CLI documentation for `--no-wait` parameter compatibility with monitoring modes and improve path handling by ensuring tilde expansion only occurs at the start of paths. Update related functions to utilize the new path expansion logic and adjust unit tests for error message consistency.

* Refactor import statements in command-runner-utilities.ts to use ES6 module syntax for consistency across the codebase.

* Enhance unit tests for file path utilities by improving tilde expansion logic and error handling. Update mocks to use `vi.spyOn` for better control and consistency. Adjust assertions to reflect new behavior in path resolution and error messages.

* 2.7.6-alpha.6

* Enhance parameter validation in command runner to ensure compatibility between `--no-wait`, `--monitor`, and download options. Update documentation to reflect these changes and clarify error handling for incompatible parameter combinations. Add unit tests to verify correct behavior when conflicting flags are used.

* Improve validation for `--monitor` parameter in command runner to handle invalid values and missing arguments. Update unit tests to ensure proper error handling for these scenarios.

* Update documentation for `--monitor` parameter to clarify valid values and error handling. Modify E2E tests to check for specific error messages related to invalid Personal Access Key format and monitor mode. Adjust unit tests to reflect optional parameter syntax for better validation.

* 2.7.6-alpha.7

* Update E2E tests to require at least 1 successful operation for concurrent commands, reflecting expected behavior under config file access conflicts or timing issues.

* 2.7.6

* #BE-7645 Fix Release Note Update for Uploading AAB File (#99)

* Fix release not update for uploading aab (testing-distribution).

* Add unit tests for appPath validation in file upload utilities.

* 2.7.7-alpha.1

* Enhance error handling in upload functions to provide clearer messages for file size, API response format, and file extension errors. Improve spinner management during error reporting for better user experience.

* 2.7.7-alpha.2

* Update documentation and interactive input handling for release notes. Clarify that two blank lines are required to finish entering release notes instead of pressing Enter twice.

* 2.7.7

* Refactor version ID retrieval and release candidate marking in command runner.

* Add unit tests for handleReleaseCandidateMarking to validate appVersionId and versionId retrieval from commitFileResponse, and ensure proper error handling when no app versions are found.

* 2.7.8-alpha.1

* Add getAppVersionAfterUploadWithTaskCompletion function to improve app version retrieval after uploads, including task completion handling and filtering by upload time. Enhance unit tests to validate new functionality and ensure accurate version selection based on file size and name.

* 2.7.8-alpha.2

* Enhance upload functions to support custom tags and release notes.

* Remove deprecated release notes update logic from handleDistributionUpload and clean up related tests. Update unit tests to reflect changes in upload functionality.

* 2.7.8-alpha.3

* Refactor Jenkins PAT (#100)

* Fix release not update for uploading aab (testing-distribution).

* Add unit tests for appPath validation in file upload utilities.

* 2.7.7-alpha.1

* Enhance error handling in upload functions to provide clearer messages for file size, API response format, and file extension errors. Improve spinner management during error reporting for better user experience.

* 2.7.7-alpha.2

* Update documentation and interactive input handling for release notes. Clarify that two blank lines are required to finish entering release notes instead of pressing Enter twice.

* 2.7.7

* Refactor version ID retrieval and release candidate marking in command runner.

* Add unit tests for handleReleaseCandidateMarking to validate appVersionId and versionId retrieval from commitFileResponse, and ensure proper error handling when no app versions are found.

* 2.7.8-alpha.1

* Add getAppVersionAfterUploadWithTaskCompletion function to improve app version retrieval after uploads, including task completion handling and filtering by upload time. Enhance unit tests to validate new functionality and ensure accurate version selection based on file size and name.

* 2.7.8-alpha.2

* Enhance upload functions to support custom tags and release notes.

* Remove deprecated release notes update logic from handleDistributionUpload and clean up related tests. Update unit tests to reflect changes in upload functionality.

* 2.7.8-alpha.3

* Update GitHub PAT credential in Jenkinsfile.

Author: fuatguzel

Jenkinsfile

@@ -5,7 +5,7 @@ pipeline {
     }
     environment {
         NPM_AUTH_TOKEN = credentials('Appcircle-CLI-NPM-Cred')
-        GITHUB_PAT = credentials('ozer-github-pat')
+        GITHUB_PAT = credentials('appcircle-cli-gh-repo-fg-pat')
     }
     stages {
         stage('PR Validation') {
@@ -230,7 +230,10 @@ pipeline {
 
         stage('Publish') {
             when {
-                expression { params.PUBLISH == true }
+                anyOf {
+                    expression { params.PUBLISH == true }
+                    buildingTag()
+                }
             }
             steps {
                 sh '''#!/bin/bash

docs/build/start.md

@@ -29,10 +29,15 @@ appcircle build start [options]
   --configurationId <uuid>  Configuration ID
   --configuration <string>  Configuration name (alternative to --configurationId)
   --no-wait                 Don't wait for build completion, return immediately with task info
+                            Note: Incompatible with monitoring modes (--monitor) and download options
   --download-logs           Automatically download build logs after completion
+                            Note: Cannot be used with --no-wait or --monitor none
   --download-artifacts      Automatically download build artifacts after completion
+                            Note: Cannot be used with --no-wait or --monitor none
   --path <string>           Download path for logs and artifacts (default: ~/Downloads)
-  --monitor <mode>          Build monitoring preference: none, summary (default), steps, or verbose
+  --monitor [mode]          Build monitoring preference: none, summary (default), steps, or verbose
+                            Valid values: none | summary | steps | verbose
+                            Note: Incompatible with --no-wait. Must be specified with a valid value.
 ```
 
 ## Options inherited from parent commands
@@ -201,9 +206,11 @@ appcircle build start --profileId <uuid> --commitId <uuid> --workflowId <uuid> -
 
 - **No Wait**: The `--no-wait` parameter is useful for automation scenarios where you don't want to wait for build completion. The command returns immediately with task information.
 
-- **Auto Download**: The `--download-logs` and `--download-artifacts` parameters automatically download files after build completion. Use `--path` to specify a custom download location.
+- **Parameter Compatibility**: The `--no-wait` flag is incompatible with monitoring modes (`--monitor verbose`, `--monitor steps`, `--monitor summary`). If both are specified, the CLI will display an error and exit. For automation scenarios, use `--no-wait` without any monitoring flags (which defaults to immediate exit like `--monitor none`).
 
-- **Monitoring Preferences**: The `--monitor` parameter allows you to control how build progress is displayed. The default `summary` mode provides real-time build status and duration, while `verbose` mode offers full verbose log streaming, `steps` shows step-by-step progress, and `none` returns only the task ID.
+- **Auto Download**: The `--download-logs` and `--download-artifacts` parameters automatically download files after build completion. Use `--path` to specify a custom download location. **Important**: These download options cannot be used with `--no-wait` or `--monitor none` because downloads require waiting for the build to complete. If you try to use them together, the CLI will display an error message with suggestions on how to resolve the conflict.
+
+- **Monitoring Preferences**: The `--monitor` parameter allows you to control how build progress is displayed. The default `summary` mode provides real-time build status and duration, while `verbose` mode offers full verbose log streaming, `steps` shows step-by-step progress, and `none` returns only the task ID. **Important**: The `--monitor` flag must be provided with a valid value (`none`, `summary`, `steps`, or `verbose`). Using `--monitor` without a value or with an invalid value will result in an error.
 
 - **Real-time Logs**: All monitor modes (except `none`) provide real-time log streaming, allowing you to monitor build progress as it happens. The system automatically formats logs and handles step transitions for better readability.
 

docs/testing-distribution/upload.md

@@ -20,6 +20,15 @@ appcircle testing-distribution upload [options]
       --help   Show help for command
 ```
 
+## Release Notes
+
+- The `--message` parameter allows you to add release notes for your distribution
+- Release notes are supported for both APK and AAB files
+- In interactive mode, you can enter multi-line release notes:
+  - Type your release notes line by line
+  - Leave two blank lines to finish entering release notes
+  - You can include line breaks and formatting in your release notes
+
 ## Note on File Size Limits
 
 - The maximum allowed file size for uploads is 3 GB

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@appcircle/cli",
-  "version": "2.7.6-alpha.3",
+  "version": "2.7.8-alpha.3",
   "description": "CLI tool for running Appcircle services from the command line",
   "main": "bin/appcircle.js",
   "bin": {

package.json

@@ -58,17 +58,25 @@ export const validateParameterErrorFlag = (params: any): ValidationResult => {
 
 /**
  * Expands tilde (~) in file paths to home directory
+ * Only expands ~ at the beginning of the path (e.g., ~/Desktop or ~\Desktop)
  * @param filePath Path that may contain tilde
  * @returns Expanded path
  */
 export const expandTildeInPath = (filePath: string): string => {
   if (!filePath) return filePath;
 
+  const trimmedPath = filePath.trim();
   const homeDir = os.homedir();
-  if (filePath.includes('~')) {
-    return filePath.replace(/~/g, homeDir);
+  
+  // Only expand tilde if it's at the start of the path
+  if (trimmedPath === '~') {
+    return homeDir;
+  }
+  if (trimmedPath.startsWith('~/') || trimmedPath.startsWith('~\\')) {
+    return path.join(homeDir, trimmedPath.slice(2));
   }
-  return filePath;
+  
+  return trimmedPath;
 };
 
 /**