Merge pull request #2351 from amanchopra1905/stage

updated the release notes and yaml retry directive

Author: surishubham

docs/browserstack-to-lambdatest-migration-guide.md

@@ -458,15 +458,6 @@ runtime:
 
 ***
 
-<!-- ### `retryOnFailure`
-This allows you to configure automatic retries for failed test scenarios. When set to true (`retryOnFailure: true`), tests will be retried based on the [`maxRetries`](/support/docs/deep-dive-into-hyperexecute-yaml/#maxretries) value specified. The default setting is **false**.
-
-This feature eliminates the need to rerun the entire job to verify if a test scenario is genuinely failing or encountering an intermittent issue. By enabling `retryOnFailure`, you can promptly retry tests upon failure, helping determine if the test consistently fails or passes in subsequent attempts."
-
-```yaml
-retryOnFailure: true
-``` -->
-
 ### `retryOnFailure`
 The `retryOnFailure` enables automatic retries for failed test scenarios only when the [testRunnerCommand](/support/docs/deep-dive-into-hyperexecute-yaml/#testrunnercommand) itself fails. When set to `true`, the system will retry failed commands based on the [`maxRetries`](/support/docs/deep-dive-into-hyperexecute-yaml/#maxretries) value defined. The default setting is `false`.
 
@@ -481,6 +472,14 @@ retryOnFailure: true
 #### ✅ Use Case:
 This feature helps avoid re-running the entire job to determine if a test failure is due to a genuine issue or a transient problem (e.g., flaky tests, network hiccups). By enabling `retryOnFailure`, only the failing command is retried, allowing for quicker feedback and more efficient test execution.
 
+:::tip
+If you are using Maven, ensure that the `testFailureIgnore` flag in your `pom.xml` is set to `false`. When `testFailureIgnore` is set to `true`, Maven treats test failures as ignored, causing HyperExecute’s retry mechanism to not trigger, even if `retryOnFailure` is enabled.
+
+```java
+<testFailureIgnore>false</testFailureIgnore>
+```
+:::
+
 ***
 
 ### `maxRetries`

docs/deep-dive-into-hyperexecute-yaml.md

@@ -0,0 +1,166 @@
+---
+id: hyperexecute-github-app-integration
+title: GitHub App Integration Support for HyperExecute
+hide_title: false
+sidebar_label: GitHub App
+description:  GitHub App Integration Support for HyperExecute 
+keywords:
+  - LambdaTest Hyperexecute
+  - LambdaTest Hyperexecute help
+  - LambdaTest Hyperexecute documentation
+  - GitHub App
+  - Integrations
+  - Products
+  - Automated testing alerts
+  - DevOps communication
+url: https://www.lambdatest.com/support/docs/hyperexecute-github-app-integration/
+site_name: LambdaTest
+slug: hyperexecute-github-app-integration/
+---
+
+import CodeBlock from '@theme/CodeBlock';
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Integration with Products",
+          "item": "https://www.lambdatest.com/support/docs/hyperexecute-github-app-integration/"
+        }]
+      })
+    }}
+></script>
+> This is currently in the **Beta** version.
+
+HyperExecute supports integration with GitHub App, enabling secure, fine-grained, and scalable access to your GitHub repositories without relying on long-lived Personal Access Tokens (PATs).
+
+With this integration, HyperExecute automatically generates short-lived installation access tokens via GitHub App for all Git-related operations in Projects and Workflows, enhancing security, compliance, and maintainability.
+
+This integration supports three onboarding paths:
+- **LambdaTest's Marketplace GitHub App** (Public Cloud)
+- **Your Existing GitHub App** (On-Prem / Private Cloud)
+- **Private GitHub App Dedicated to Your Organization** (On-Prem / Air-Gapped)
+
+## How It Works
+1. Install a GitHub App using one of the three supported approaches. <br />
+2. Complete the post-installation registration within the LambdaTest platform. <br />
+3. HyperExecute backend (Logistics) sends data to Sentinel to persist details in the `github_app_integration` table. <br />
+4. For customer-managed GitHub App, create an org-level secret using the Logistics Secrets API: `github_app_private_key_{{git_tenant}}`. <br />
+
+Once setup is complete, all HyperExecute Project and Workflow Git operations use short-lived installation tokens instead of PAT tokens. The PAT-based flow is used only as a fallback when no GitHub App is configured.
+
+## Installation Approaches
+HyperExecute supports three installation models, depending on your cloud type and organizational setup.
+
+### Approach 1: LambdaTest's Marketplace GitHub App (Public Cloud)
+
+**Prerequisites :**
+
+- Admin permissions in your target GitHub organization
+
+**Installation Steps**
+
+1. Navigate to [GitHub Marketplace](https://github.com/marketplace)
+2. Search for "LambdaTest" or "HyperExecute"
+3. Open the LambdaTest GitHub App listing
+4. Click **Install**
+5. Select your target GitHub Organization
+   - For GitHub Enterprise, installation must be completed per organization
+6. Configure repository access:
+   - **All repositories** (recommended)
+   - **Select repositories**
+7. Review the required permissions:
+   - **Contents** (read/write)
+   - **Metadata** (read)
+8. Click **Install** to complete the installation
+
+**Post-Installation Configuration**
+
+After installation, GitHub automatically redirects you to: `https://{{accounts_base_url}}/org-settings/hyperexecute/git-integration`
+
+The redirect URL includes an `installation_id` parameter required for configuration.
+
+> **Note:** Only Org Admins can complete the registration. Organization users can view mappings but cannot modify them.
+
+### Approach 2: Your Existing GitHub App (On-Prem)
+
+**Prerequisites**
+
+- A GitHub App already exists in your GitHub organization
+- Admin access to the GitHub App
+- Required permissions are configured:
+  - **Contents** (read)
+  - **Metadata** (read)
+
+**Installation Steps**
+
+1. Obtain your app's installation ID from:
+   - Navigate to **GitHub App → Installations → Installation URL**
+   - Example URL format: `https://github.com/settings/installations/{installation_id}`
+
+2. Navigate to the LambdaTest setup page:
+```
+   https://{{accounts_base_url}}/org-settings/hyperexecute/git-integration
+```
+
+3. Manually enter:
+   - `installation_id`
+   - Additional app details as required
+
+> **Note:** For GitHub Enterprise setups with multiple organizations, repeat this setup for each organization.
+
+**Additional Required Configuration**
+
+Create an org-level secret via the Logistics Secret API:
+```
+github_app_private_key_{{git_tenant}}
+```
+
+This private key is used to generate short-lived tokens internally.
+
+### Approach 3: Private GitHub App (On-Prem Dedicated App)
+
+**Prerequisites**
+
+- Admin access in your target GitHub organization
+- Private GitHub App installation URL shared by the LambdaTest/Workflow team
+- Setup URL inside the GitHub App updated to the LambdaTest private setup URL
+
+**Installation Steps**
+
+1. Navigate to the private app installation URL:
+```
+   https://github.com/apps/{private-app-name}/installations/new
+```
+
+2. Select your GitHub organization
+   - Enterprise customers must repeat this process for each organization
+
+3. Configure repository access permissions
+
+4. Review and confirm the installation
+
+**Post-Installation Configuration**
+
+GitHub will redirect you to the private setup URL configured for your environment:
+```
+https://{{private_accounts_base_url}}/org-settings/hyperexecute/git-integration
+```
+
+The redirect contains the `installation_id` parameter, which is required for configuration.
+
+> **Note:** Only Org Admins can complete this configuration step.

docs/hyperexecute-github-app-integration.md

@@ -0,0 +1,47 @@
+---
+id: hyperexecute-release-notes-3-1-4
+title: Version 3.1.4
+hide_title: false
+sidebar_label: Version 3.1.4
+description: Version 3.1.4
+keywords:
+  - LambdaTest Hyperexecute
+  - LambdaTest Hyperexecute help
+  - LambdaTest Hyperexecute documentation
+  - FAQs
+url: https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-1-4/
+site_name: LambdaTest
+slug: hyperexecute-release-notes-3-1-4/
+---
+
+import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
+
+<script type="application/ld+json"
+      dangerouslySetInnerHTML={{ __html: JSON.stringify({
+       "@context": "https://schema.org",
+        "@type": "BreadcrumbList",
+        "itemListElement": [{
+          "@type": "ListItem",
+          "position": 1,
+          "name": "Home",
+          "item": "https://www.lambdatest.com"
+        },{
+          "@type": "ListItem",
+          "position": 2,
+          "name": "Support",
+          "item": "https://www.lambdatest.com/support/docs/"
+        },{
+          "@type": "ListItem",
+          "position": 3,
+          "name": "Version",
+          "item": "https://www.lambdatest.com/support/docs/hyperexecute-release-notes-3-1-4/"
+        }]
+      })
+    }}
+></script>
+## Enhanced Support for Azure Repositories in HyperExecute Projects
+We have introduced an enhancement to the HyperExecute [Custom Project feature](/support/docs/hyperexecute-projects/#setup-custom-project) to support Azure Repos. This enables you with code repositories hosted in Azure DevOps to execute tests directly on HyperExecute—without relying on Jenkins or any external CI/CD tool.
+
+With this update, you can now configure Azure Repos in the same intuitive manner as GitHub, or Bitbucket. Simply provide the repository details and Personal Access Token (PAT), and HyperExecute will fetch the code and trigger workflows seamlessly.
+
+> 📘 **Read More:** Learn more about configuring Azure Repos, project setup, workflows, and job triggers in the [HyperExecute documentation](https://www.lambdatest.com/support/docs/hyperexecute-projects/).

docs/hyperexecute-release-notes-3-1-4.md

@@ -59,6 +59,7 @@ HyperExecute is an AI Native Test Orchestration Cloud Platform, enabling test au
 #### November, 2025
 | Release Number | Release Date |
 |----------------|--------------|
+| [Version 3.1.4](/support/docs/hyperexecute-release-notes-3-1-4) | Nov 24, 2025|
 | [Version 3.1.2](/support/docs/hyperexecute-release-notes-3-1-2) | Nov 10, 2025|
 
 #### October, 2025