Version Packages
This commit is contained in:
@@ -1,5 +1,25 @@
|
||||
# @backstage/config
|
||||
|
||||
## 0.1.13
|
||||
|
||||
### 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.13-next.0
|
||||
|
||||
### Patch Changes
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "@backstage/config",
|
||||
"description": "Config API used by Backstage core, backend, and CLI",
|
||||
"version": "0.1.13-next.0",
|
||||
"version": "0.1.13",
|
||||
"private": false,
|
||||
"publishConfig": {
|
||||
"access": "public",
|
||||
@@ -34,7 +34,7 @@
|
||||
"lodash": "^4.17.21"
|
||||
},
|
||||
"devDependencies": {
|
||||
"@backstage/test-utils": "^0.2.3-next.0",
|
||||
"@backstage/test-utils": "^0.2.3",
|
||||
"@types/jest": "^26.0.7",
|
||||
"@types/node": "^14.14.32"
|
||||
},
|
||||
|
||||
Reference in New Issue
Block a user