fix: regenerate pnpm-lock.yaml after conflict

4 weeks ago · a92fa8f6fb
parent 5ed3c3b916
commit a92fa8f6fb
1 changed files with 6 additions and 0 deletions
--- a/pnpm-lock.yaml
+++ b/pnpm-lock.yaml
@ -2655,6 +2655,10 @@ packages:
  minimist@1.2.8:
    resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==}

+  minipass@7.1.2:
+    resolution: {integrity: sha512-qOOzS1cBTWYF4BH8fVePDBOO9iptMnGUEZwNc/cMWnTV2nVLZ7VoNWEPHkYczZA0pdoA7dl6e7FL659nX9S2aw==}
+    engines: {node: '>=16 || 14 >=14.17'}
+
  minisearch@7.2.0:
    resolution: {integrity: sha512-dqT2XBYUOZOiC5t2HRnwADjhNS2cecp9u+TJRiJ1Qp/f5qjkeT5APcGPjHw+bz89Ms8Jp+cG4AlE+QZ/QnDglg==}

@ -5773,6 +5777,8 @@ snapshots:

  minimist@1.2.8: {}

+  minipass@7.1.2: {}
+
  minisearch@7.2.0: {}

  minizlib@3.1.0: