@backstage/config-loader - npm Package Compare versions

Comparing version 0.9.3-next.0 to 0.9.3

CHANGELOG.md

 # @backstage/config-loader
 
+## 0.9.3
+
+### Patch Changes
+
+- f685e1398f: Loading of app configurations now reference the `@deprecated` construct from
+  JSDoc to determine if a property in-use has been deprecated. Users are notified
+  of deprecated keys in the format:
+
+  ```txt
+  The configuration key 'catalog.processors.githubOrg' of app-config.yaml is deprecated and may be removed soon. Configure a GitHub integration instead.
+  ```
+
+  When the `withDeprecatedKeys` option is set to `true` in the `process` method
+  of `loadConfigSchema`, the user will be notified that deprecated keys have been
+  identified in their app configuration.
+
+  The `backend-common` and `plugin-app-backend` packages have been updated to set
+  `withDeprecatedKeys` to true so that users are notified of deprecated settings
+  by default.
+
+- Updated dependencies
+  - @backstage/config@0.1.13
+
 ## 0.9.3-next.0
@@ -4,0 +27,0 @@

package.json

 {
   "name": "@backstage/config-loader",
   "description": "Config loading functionality used by Backstage backend, and CLI",
-  "version": "0.9.3-next.0",
+  "version": "0.9.3",
   "private": false,
@@ -34,3 +34,3 @@ "publishConfig": {
     "@backstage/cli-common": "^0.1.6",
-    "@backstage/config": "^0.1.13-next.0",
+    "@backstage/config": "^0.1.13",
     "@backstage/errors": "^0.2.0",
@@ -62,4 +62,4 @@ "@backstage/types": "^0.1.1",
   ],
-  "gitHead": "31184691d5a38cb78b091c8f7ad6db80604519a6",
+  "gitHead": "600d6e3c854bbfb12a0078ca6f726d1c0d1fea0b",
   "module": "dist/index.esm.js"
 }

No alert changes

Improved metrics

Total package byte prevSize

209343

increased by0.4%

Dependency changes

• Updated@backstage/config@^0.1.13