Merge remote-tracking branch 'origin/staging-new'

Signed-off-by: Alexander Onnikov <[email protected]>

Author: aonnikov

.github/workflows/main.yml

@@ -927,4 +927,4 @@ jobs:
         uses: actions/upload-artifact@v4
         with:
           name: TraceX-Linux
-          path: ./qms-desktop-package/deploy/TraceX-linux-*.zip
+          path: ./qms-desktop-package/deploy/TraceX-linux-*.zip

.vscode/launch.json

@@ -617,6 +617,7 @@
       },
       "runtimeArgs": ["--nolazy", "-r", "ts-node/register"],
       "sourceMaps": true,
+      "nodeVersionHint": 22,
       "cwd": "${workspaceRoot}/services/github/pod-github",
       "protocol": "inspector",
       "outputCapture": "std"

common/config/rush/.npmrc

@@ -4,20 +4,30 @@
 #
 # NOTE: The "rush publish" command uses .npmrc-publish instead.
 #
-# Before invoking the package manager, Rush will copy this file to the folder where installation
-# is performed.  The copied file will omit any config lines that reference environment variables
+# Before invoking the package manager, Rush will generate an .npmrc in the folder where installation
+# is performed.  This generated file will omit any config lines that reference environment variables
 # that are undefined in that session; this avoids problems that would otherwise result due to
 # a missing variable being replaced by an empty string.
 #
+# If "subspacesEnabled" is true in subspaces.json, the generated file will merge settings from
+# "common/config/rush/.npmrc" and "common/config/subspaces/<name>/.npmrc", with the latter taking
+# precedence.
+#
 # * * * SECURITY WARNING * * *
 #
 # It is NOT recommended to store authentication tokens in a text file on a lab machine, because
-# other unrelated processes may be able to read the file.  Also, the file may persist indefinitely,
+# other unrelated processes may be able to read that file.  Also, the file may persist indefinitely,
 # for example if the machine loses power.  A safer practice is to pass the token via an
 # environment variable, which can be referenced from .npmrc using ${} expansion.  For example:
 #
 #   //registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}
 #
+
+# Explicitly specify the NPM registry that "rush install" and "rush update" will use by default:
 registry=https://registry.npmjs.org/
-@hcengineering:registry=https://npm.pkg.github.com
 
+# Optionally provide an authentication token for the above registry URL (if it is a private registry):
+//registry.npmjs.org/:_authToken=${NPM_TOKEN}
+
+# Change this to "true" if your registry requires authentication for read-only operations:
+always-auth=false

common/config/rush/.npmrc-publish

@@ -18,3 +18,12 @@
 #
 #   //registry.npmjs.org/:_authToken=${NPM_AUTH_TOKEN}
 #
+
+# Explicitly specify the NPM registry that "rush publish" will use by default:
+registry=https://registry.npmjs.org/
+
+# Optionally provide an authentication token for the above registry URL (if it is a private registry):
+//registry.npmjs.org/:_authToken=${NPM_TOKEN}
+
+# Change this to "true" if your registry requires authentication for read-only operations:
+always-auth=false

common/config/rush/artifactory.json

@@ -65,40 +65,34 @@
        * "This monorepo consumes packages from an Artifactory private NPM registry."
        */
       // "introduction": "",
-
       /**
        * Overrides the message that normally says:
        * "Please contact the repository maintainers for help with setting up an Artifactory user account."
        */
       // "obtainAnAccount": "",
-
       /**
        * Overrides the message that normally says:
        * "Please open this URL in your web browser:"
        *
        * The "artifactoryWebsiteUrl" string is printed after this message.
        */
       // "visitWebsite": "",
-
       /**
        * Overrides the message that normally says:
        * "Your user name appears in the upper-right corner of the JFrog website."
        */
       // "locateUserName": "",
-
       /**
        * Overrides the message that normally says:
        * "Click 'Edit Profile' on the JFrog website.  Click the 'Generate API Key'
        * button if you haven't already done so previously."
        */
       // "locateApiKey": ""
-
       /**
        * Overrides the message that normally prompts:
        * "What is your Artifactory user name?"
        */
       // "userNamePrompt": ""
-
       /**
        * Overrides the message that normally prompts:
        * "What is your Artifactory API key?"

common/config/rush/cobuild.json

@@ -0,0 +1,22 @@
+/**
+ * This configuration file manages Rush's cobuild feature.
+ * More documentation is available on the Rush website: https://rushjs.io
+ */
+ {
+  "$schema": "https://developer.microsoft.com/json-schemas/rush/v5/cobuild.schema.json",
+
+  /**
+   * (Required) EXPERIMENTAL - Set this to true to enable the cobuild feature.
+   * RUSH_COBUILD_CONTEXT_ID should always be specified as an environment variable with an non-empty string,
+   * otherwise the cobuild feature will be disabled.
+   */
+  "cobuildFeatureEnabled": false,
+
+  /**
+   * (Required) Choose where cobuild lock will be acquired.
+   *
+   * The lock provider is registered by the rush plugins.
+   * For example, @rushstack/rush-redis-cobuild-plugin registers the "redis" lock provider.
+   */
+  "cobuildLockProvider": "redis"
+}

common/config/rush/custom-tips.json

@@ -0,0 +1,29 @@
+/**
+ * This configuration file allows repo maintainers to configure extra details to be
+ * printed alongside certain Rush messages.  More documentation is available on the
+ * Rush website: https://rushjs.io
+ */
+{
+  "$schema": "https://developer.microsoft.com/json-schemas/rush/v5/custom-tips.schema.json",
+
+  /**
+   * Custom tips allow you to annotate Rush's console messages with advice tailored for
+   * your specific monorepo.
+   */
+  "customTips": [
+    // {
+    //   /**
+    //    * (REQUIRED) An identifier indicating a message that may be printed by Rush.
+    //    * If that message is printed, then this custom tip will be shown.
+    //    * The list of available tip identifiers can be found on this page:
+    //    * https://rushjs.io/pages/maintainer/custom_tips/
+    //    */
+    //   "tipId": "TIP_RUSH_INCONSISTENT_VERSIONS",
+    // 
+    //   /**
+    //    * (REQUIRED) The message text to be displayed for this tip.
+    //    */
+    //   "message": "For additional troubleshooting information, refer this wiki article:\n\nhttps://intranet.contoso.com/docs/pnpm-mismatch"
+    // }
+  ]
+}

common/config/rush/experiments.json

@@ -3,7 +3,7 @@
  * Rush features.  More documentation is available on the Rush website: https://rushjs.io
  */
 {
-  "$schema": "https://developer.microsoft.com/json-schemas/rush/v5/experiments.schema.json",
+  "$schema": "https://developer.microsoft.com/json-schemas/rush/v5/experiments.schema.json"
 
   /**
    * By default, 'rush install' passes --no-prefer-frozen-lockfile to 'pnpm install'.
@@ -17,6 +17,13 @@
    */
   // "usePnpmPreferFrozenLockfileForRushUpdate": true,
 
+  /**
+   * By default, 'rush update' runs as a single operation.
+   * Set this option to true to instead update the lockfile with `--lockfile-only`, then perform a `--frozen-lockfile` install.
+   * Necessary when using the `afterAllResolved` hook in .pnpmfile.cjs.
+   */
+  // "usePnpmLockfileOnlyThenFrozenLockfileForRushUpdate": true,
+
   /**
    * If using the 'preventManualShrinkwrapChanges' option, restricts the hash to only include the layout of external dependencies.
    * Used to allow links between workspace projects or the addition/removal of references to existing dependency versions to not
@@ -34,7 +41,13 @@
    * If true, build caching will respect the allowWarningsInSuccessfulBuild flag and cache builds with warnings.
    * This will not replay warnings from the cached build.
    */
-  "buildCacheWithAllowWarningsInSuccessfulBuild": true,
+  // "buildCacheWithAllowWarningsInSuccessfulBuild": true,
+
+  /**
+   * If true, build skipping will respect the allowWarningsInSuccessfulBuild flag and skip builds with warnings.
+   * This will not replay warnings from the skipped build.
+   */
+  // "buildSkipWithAllowWarningsInSuccessfulBuild": true,
 
   /**
    * If true, perform a clean install after when running `rush install` or `rush update` if the
@@ -50,5 +63,58 @@
   /**
    * If true, Rush will not allow node_modules in the repo folder or in parent folders.
    */
-  // "forbidPhantomResolvableNodeModulesFolders": true
+  // "forbidPhantomResolvableNodeModulesFolders": true,
+
+  /**
+   * (UNDER DEVELOPMENT) For certain installation problems involving peer dependencies, PNPM cannot
+   * correctly satisfy versioning requirements without installing duplicate copies of a package inside the
+   * node_modules folder. This poses a problem for "workspace:*" dependencies, as they are normally
+   * installed by making a symlink to the local project source folder. PNPM's "injected dependencies"
+   * feature provides a model for copying the local project folder into node_modules, however copying
+   * must occur AFTER the dependency project is built and BEFORE the consuming project starts to build.
+   * The "pnpm-sync" tool manages this operation; see its documentation for details.
+   * Enable this experiment if you want "rush" and "rushx" commands to resync injected dependencies
+   * by invoking "pnpm-sync" during the build.
+   */
+  // "usePnpmSyncForInjectedDependencies": true,
+
+  /**
+   * If set to true, Rush will generate a `project-impact-graph.yaml` file in the repository root during `rush update`.
+   */
+  // "generateProjectImpactGraphDuringRushUpdate": true,
+
+  /**
+   * If true, when running in watch mode, Rush will check for phase scripts named `_phase:<name>:ipc` and run them instead
+   * of `_phase:<name>` if they exist. The created child process will be provided with an IPC channel and expected to persist
+   * across invocations.
+   */
+  // "useIPCScriptsInWatchMode": true,
+
+  /**
+   * (UNDER DEVELOPMENT) The Rush alerts feature provides a way to send announcements to engineers
+   * working in the monorepo, by printing directly in the user's shell window when they invoke Rush commands.
+   * This ensures that important notices will be seen by anyone doing active development, since people often
+   * ignore normal discussion group messages or don't know to subscribe.
+   */
+  // "rushAlerts": true,
+
+  /**
+   * When using cobuilds, this experiment allows uncacheable operations to benefit from cobuild orchestration without using the build cache.
+   */
+  // "allowCobuildWithoutCache": true,
+
+  /**
+   * By default, rush perform a full scan of the entire repository. For example, Rush runs `git status` to check for local file changes.
+   * When this toggle is enabled, Rush will only scan specific paths, significantly speeding up Git operations.
+   */
+  // "enableSubpathScan": true,
+
+  /**
+   * Rush has a policy that normally requires Rush projects to specify `workspace:*` in package.json when depending
+   * on other projects in the workspace, unless they are explicitly declared as `decoupledLocalDependencies`
+   * in rush.json.  Enabling this experiment will remove that requirement for dependencies belonging to a different
+   * subspace.  This is useful for large product groups who work in separate subspaces and generally prefer to consume
+   * each other's packages via the NPM registry.
+   */
+  // "exemptDecoupledDependenciesBetweenSubspaces": false
 }