Upgrade Geogirafe Version
-
If you need, change the target version in your
package.json. -
Run:
cd front
npm upgrade -
You'll probably need to update your files if breaking changes were introduced. To have the list of such changes, search for
@geogirafe/lib-geoportalin the diff of thepackage-lock.jsonto find which version you upgraded from."node_modules/@geogirafe/lib-geoportal": {
- "version": "1.0.0-2090024287",
- "resolved": "https://registry.npmjs.org/@geogirafe/lib-geoportal/-/lib-geoportal-1.0.0-2090024287.tgz",
- "integrity": "sha512-wR7+Kpp1C+I70NwI5uj/jBTWJqukvKYr2h0AdHgTCx21ctjpSjzVbqzqcjtfpQgMgHp3wuK6CNfuIs7GjbC0dw==",
+ "version": "1.0.2136394118",
+ "resolved": "https://registry.npmjs.org/@geogirafe/lib-geoportal/-/lib-geoportal-1.0.2136394118.tgz",
+ "integrity": "sha512-Qy6A1H03/Ahst1E0aRy6HXlNxe1JNE65UBtICvsYoTowZ3gTIGbV6mZi04FhXAX2acTBE+h9eDUalt4eqB1ewQ==",
}Check the changelog here between the two versions.
-
If breaking changes occurred between the two versions, you'll see this red message:
🛆 This version includes manual migration steps. See the Merge-Request details for more infos.Click on the corresponding merge request link and apply the manual steps listed under the Migration Steps / Breaking-Changes section, pay attention to not override some work you've already done. This is valid either common files like index.html but also for anything inherited in your custom components.