Sign presentation patch

common/config/rush/pnpm-config.json

@@ -0,0 +1,77 @@
+{
+  /**
+   * Specifies the location of the PNPM store.  There are two possible values:
+   *
+   * - "local" - use the "pnpm-store" folder in the current configured temp folder:
+   *   "common/temp/pnpm-store" by default.
+   * - "global" - use PNPM's global store, which has the benefit of being shared
+   *    across multiple repo folders, but the disadvantage of less isolation for builds
+   *    (e.g. bugs or incompatibilities when two repos use different releases of PNPM)
+   *
+   * RUSH_PNPM_STORE_PATH will override the directory that will be used as the store
+   *
+   * In all cases, the store path will be overridden by the environment variable RUSH_PNPM_STORE_PATH.
+   *
+   * The default value is "local".
+   */
+  // "pnpmStore": "local",
+  /**
+   * If true, then Rush will add the "--strict-peer-dependencies" option when invoking PNPM.
+   * This causes "rush install" to fail if there are unsatisfied peer dependencies, which is
+   * an invalid state that can cause build failures or incompatible dependency versions.
+   * (For historical reasons, JavaScript package managers generally do not treat this invalid
+   * state as an error.)
+   *
+   * The default value is false to avoid legacy compatibility issues.
+   * It is strongly recommended to set strictPeerDependencies=true.
+   */
+  // "strictPeerDependencies": true,
+  /**
+   * Configures the strategy used to select versions during installation.
+   *
+   * This feature requires PNPM version 3.1 or newer.  It corresponds to the "--resolution-strategy" command-line
+   * option for PNPM.  Possible values are "fast" and "fewer-dependencies".  PNPM's default is "fast", but this may
+   * be incompatible with certain packages, for example the "@types" packages from DefinitelyTyped.  Rush's default
+   * is "fewer-dependencies", which causes PNPM to avoid installing a newer version if an already installed version
+   * can be reused; this is more similar to NPM's algorithm.
+   *
+   * After modifying this field, it's recommended to run "rush update --full" so that the package manager
+   * will recalculate all version selections.
+   */
+  // "resolutionStrategy": "fast",
+  /**
+   * If true, then `rush install` will report an error if manual modifications
+   * were made to the PNPM shrinkwrap file without running "rush update" afterwards.
+   *
+   * This feature protects against accidental inconsistencies that may be introduced
+   * if the PNPM shrinkwrap file ("pnpm-lock.yaml") is manually edited.  When this
+   * feature is enabled, "rush update" will append a hash to the file as a YAML comment,
+   * and then "rush update" and "rush install" will validate the hash.  Note that this does not prohibit
+   * manual modifications, but merely requires "rush update" be run
+   * afterwards, ensuring that PNPM can report or repair any potential inconsistencies.
+   *
+   * To temporarily disable this validation when invoking "rush install", use the
+   * "--bypass-policy" command-line parameter.
+   *
+   * The default value is false.
+   */
+  // "preventManualShrinkwrapChanges": true,
+  /**
+   * If true, then `rush install` will use the PNPM workspaces feature to perform the
+   * install.
+   *
+   * This feature uses PNPM to perform the entire monorepo install. When using workspaces, Rush will
+   * generate a "pnpm-workspace.yaml" file referencing all local projects to install. Rush will
+   * also generate a "pnpmfile.js" which is used to provide preferred versions support. When install
+   * is run, this pnpmfile will be used to replace dependency version ranges with a smaller subset
+   * of the original range. If the preferred version is not fully a subset of the original version
+   * range, it will be left as-is. After this, the pnpmfile.js provided in the repository (if one
+   * exists) will be called to further modify package dependencies.
+   *
+   * This option is experimental. The default value is false.
+   */
+  "useWorkspaces": true,
+  "globalPatchedDependencies": {
+    "@credo-ts/core@0.5.10": "patches/@credo-ts__core@0.5.10.patch"
+  }
+}

common/pnpm-patches/@credo-ts__core@0.5.10.patch

@@ -0,0 +1,13 @@
+diff --git a/build/modules/vc/data-integrity/W3cJsonLdCredentialService.js b/build/modules/vc/data-integrity/W3cJsonLdCredentialService.js
+index c833d0108e8852127afac1c87cffca0aba1268dc..e3391b11fd9b7b7fe85b027eb68ea110e4324499 100644
+--- a/build/modules/vc/data-integrity/W3cJsonLdCredentialService.js
++++ b/build/modules/vc/data-integrity/W3cJsonLdCredentialService.js
+@@ -179,7 +179,7 @@ let W3cJsonLdCredentialService = class W3cJsonLdCredentialService {
+             domain: options.domain,
+             documentLoader: this.w3cCredentialsModuleConfig.documentLoader(agentContext),
+         });
+-        return utils_1.JsonTransformer.fromJSON(result, W3cJsonLdVerifiablePresentation_1.W3cJsonLdVerifiablePresentation);
++        return utils_1.JsonTransformer.fromJSON(result, W3cJsonLdVerifiablePresentation_1.W3cJsonLdVerifiablePresentation, { validate: !(result.verifiableCredential === undefined) });
+     }
+     /**
+      * Verifies a presentation including the credentials it includes

rush.json

@@ -28,83 +28,6 @@
   // "npmVersion": "6.14.15",
   // "yarnVersion": "1.9.4",
 
-  /**
-   * Options that are only used when the PNPM package manager is selected
-   */
-  "pnpmOptions": {
-    /**
-     * Specifies the location of the PNPM store.  There are two possible values:
-     *
-     * - "local" - use the "pnpm-store" folder in the current configured temp folder:
-     *   "common/temp/pnpm-store" by default.
-     * - "global" - use PNPM's global store, which has the benefit of being shared
-     *    across multiple repo folders, but the disadvantage of less isolation for builds
-     *    (e.g. bugs or incompatibilities when two repos use different releases of PNPM)
-     *
-     * RUSH_PNPM_STORE_PATH will override the directory that will be used as the store
-     *
-     * In all cases, the store path will be overridden by the environment variable RUSH_PNPM_STORE_PATH.
-     *
-     * The default value is "local".
-     */
-    // "pnpmStore": "local",
-    /**
-     * If true, then Rush will add the "--strict-peer-dependencies" option when invoking PNPM.
-     * This causes "rush install" to fail if there are unsatisfied peer dependencies, which is
-     * an invalid state that can cause build failures or incompatible dependency versions.
-     * (For historical reasons, JavaScript package managers generally do not treat this invalid
-     * state as an error.)
-     *
-     * The default value is false to avoid legacy compatibility issues.
-     * It is strongly recommended to set strictPeerDependencies=true.
-     */
-    // "strictPeerDependencies": true,
-    /**
-     * Configures the strategy used to select versions during installation.
-     *
-     * This feature requires PNPM version 3.1 or newer.  It corresponds to the "--resolution-strategy" command-line
-     * option for PNPM.  Possible values are "fast" and "fewer-dependencies".  PNPM's default is "fast", but this may
-     * be incompatible with certain packages, for example the "@types" packages from DefinitelyTyped.  Rush's default
-     * is "fewer-dependencies", which causes PNPM to avoid installing a newer version if an already installed version
-     * can be reused; this is more similar to NPM's algorithm.
-     *
-     * After modifying this field, it's recommended to run "rush update --full" so that the package manager
-     * will recalculate all version selections.
-     */
-    // "resolutionStrategy": "fast",
-    /**
-     * If true, then `rush install` will report an error if manual modifications
-     * were made to the PNPM shrinkwrap file without running "rush update" afterwards.
-     *
-     * This feature protects against accidental inconsistencies that may be introduced
-     * if the PNPM shrinkwrap file ("pnpm-lock.yaml") is manually edited.  When this
-     * feature is enabled, "rush update" will append a hash to the file as a YAML comment,
-     * and then "rush update" and "rush install" will validate the hash.  Note that this does not prohibit
-     * manual modifications, but merely requires "rush update" be run
-     * afterwards, ensuring that PNPM can report or repair any potential inconsistencies.
-     *
-     * To temporarily disable this validation when invoking "rush install", use the
-     * "--bypass-policy" command-line parameter.
-     *
-     * The default value is false.
-     */
-    // "preventManualShrinkwrapChanges": true,
-    /**
-     * If true, then `rush install` will use the PNPM workspaces feature to perform the
-     * install.
-     *
-     * This feature uses PNPM to perform the entire monorepo install. When using workspaces, Rush will
-     * generate a "pnpm-workspace.yaml" file referencing all local projects to install. Rush will
-     * also generate a "pnpmfile.js" which is used to provide preferred versions support. When install
-     * is run, this pnpmfile will be used to replace dependency version ranges with a smaller subset
-     * of the original range. If the preferred version is not fully a subset of the original version
-     * range, it will be left as-is. After this, the pnpmfile.js provided in the repository (if one
-     * exists) will be called to further modify package dependencies.
-     *
-     * This option is experimental. The default value is false.
-     */
-    "useWorkspaces": true
-  },
   /**
    * Older releases of the Node.js engine may be missing features required by your system.
    * Other releases may have bugs.  In particular, the "latest" version will not be a