Merge pull request #7 from mekomsolutions/ft-node-ci

(fix): Fix CLI Release

.yarnrc.yml

@@ -8,4 +8,4 @@ plugins:
   - path: .yarn/plugins/@yarnpkg/plugin-outdated.cjs
     spec: "https://mskelton.dev/yarn-outdated/v3"
 
-yarnPath: .yarn/releases/yarn-4.3.1.cjs
+yarnPath: .yarn/releases/yarn-4.5.1.cjs

README.md

@@ -99,8 +99,8 @@ The module includes validation logic to prevent conflicting condition states, su
 ### Bumping the Common Lib version
 
 Make sure to bump the Common Lib version used here each time you cut a release of Patient Chart. Because Common Lib is
-marked as a peer dependency and a Webpack module federation shared dependency in
-the [Appointments app](packages/esm-appointments-app/package.json), the copy of the Common Lib that the framework loads
+marked as a peer dependency and a Webpack module federation shared dependency, the copy of the Common Lib that the
+framework loads
 is the first one that gets loaded at runtime when frontend modules are registered. If this happens to be a different
 version than what the Patient Chart expects, you might get some unexpected behavior in the Patient Chart. You can bump
 the Common Lib version by running the following command:

package.json

@@ -45,7 +45,8 @@
     "lodash-es": "^4.17.21"
   },
   "peerDependencies": {
-    "@openmrs/esm-framework": "*",
+    "@openmrs/esm-framework": "5.x",
+    "@openmrs/esm-patient-common-lib": "8.x",
     "dayjs": "1.x",
     "react": "18.x",
     "react-i18next": "11.x",
@@ -104,5 +105,5 @@
     "packages/**/src/**/*.{ts,tsx}": "eslint --cache --fix --max-warnings 0",
     "*.{css,scss,ts,tsx}": "prettier --write --list-different"
   },
-  "packageManager": "yarn@4.3.1"
+  "packageManager": "yarn@4.5.1"
 }