@backstage/config - npm Package Compare versions

CHANGELOG.md

		# @backstage/config

		## 0.0.0-nightly-202201422556
		## 0.0.0-nightly-202201921950

		@@ -23,2 +23,22 @@ ### Patch Changes

		## 0.1.13-next.0

		### 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.

		## 0.1.12
		@@ -25,0 +45,0 @@

package.json

		{
		"name": "@backstage/config",
		"description": "Config API used by Backstage core, backend, and CLI",
		"version": "0.0.0-nightly-202201422556",
		"version": "0.0.0-nightly-202201921950",
		"private": false,
		@@ -37,3 +37,3 @@ "publishConfig": {
		"devDependencies": {
		"@backstage/test-utils": "^0.2.2",
		"@backstage/test-utils": "^0.0.0-nightly-202201921950",
		"@types/jest": "^26.0.7",
		@@ -40,0 +40,0 @@ "@types/node": "^14.14.32"

New alerts