Version Packages (next)

This commit is contained in:
github-actions[bot]
2026-01-27 15:51:11 +00:00
parent 35c5b64344
commit d4b85dddee
387 changed files with 5533 additions and 194 deletions
+28
View File
@@ -1,5 +1,33 @@
# @backstage/frontend-plugin-api
## 0.14.0-next.0
### Minor Changes
- c38b74d: **BREAKING**: The following blueprints have been removed and are now only available from `@backstage/plugin-app-react`:
- `IconBundleBlueprint`
- `NavContentBlueprint`
- `RouterBlueprint`
- `SignInPageBlueprint`
- `SwappableComponentBlueprint`
- `ThemeBlueprint`
- `TranslationBlueprint`
### Patch Changes
- 7edb810: Added a new `internal` option to `createExtensionInput` that marks the input as only allowing attachments from the same plugin.
- 9554c36: **DEPRECATED**: Multiple attachment points for extensions have been deprecated. The functionality continues to work for backward compatibility, but will log a deprecation warning and be removed in a future release.
Extensions using array attachment points should migrate to using Utility APIs instead. See the [Sharing Extensions Across Multiple Locations](https://backstage.io/docs/frontend-system/architecture/27-sharing-extensions) guide for the recommended pattern.
- 53b6549: Plugins in the new frontend system now have a `pluginId` field rather than `id` to better align with naming conventions used throughout the frontend and backend systems. The old field is still present but marked as deprecated. All internal code has been updated to prefer `pluginId` while maintaining backward compatibility by falling back to `id` when needed.
- 69d880e: Bump to latest zod to ensure it has the latest features
- Updated dependencies
- @backstage/errors@1.2.7
- @backstage/types@1.2.2
- @backstage/version-bridge@1.0.11
## 0.13.3
### Patch Changes
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@backstage/frontend-plugin-api",
"version": "0.13.3",
"version": "0.14.0-next.0",
"backstage": {
"role": "web-library"
},