Version Packages

2026-03-17 21:39:07 +00:00
parent e704c00979
commit 5725b5fcfa
679 changed files with 6785 additions and 2555 deletions
@@ -1,30 +0,0 @@
---
-'@backstage/backend-plugin-api': minor
---
-
-Added optional `visibilityPermission` field to `ActionsRegistryActionOptions`, allowing actions to declare a `BasicPermission` that controls visibility and access.
-
-```typescript
-import { createPermission } from '@backstage/plugin-permission-common';
-
-const myPermission = createPermission({
-  name: 'myPlugin.myAction.use',
-  attributes: {},
-});
-
-actionsRegistry.register({
-  name: 'my-action',
-  title: 'My Action',
-  description: 'An action that requires permission',
-  visibilityPermission: myPermission,
-  schema: {
-    input: z => z.object({ name: z.string() }),
-    output: z => z.object({ ok: z.boolean() }),
-  },
-  action: async ({ input }) => {
-    return { output: { ok: true } };
-  },
-});
-```
-
-Actions without a `visibilityPermission` field continue to work as before.
@@ -1,5 +0,0 @@
---
-'@backstage/backend-defaults': patch
---
-
-Added permissions integration to the actions registry. Actions registered with a `visibilityPermission` field are now checked against the permissions framework when listing and invoking. Denied actions are filtered from list results, and invoking a denied action returns a `404 Not Found` as if the action does not exist. Permissions are automatically registered with the `PermissionsRegistryService` so they appear in the permission policy system.
@@ -1,7 +0,0 @@
---
-'@backstage/backend-plugin-api': patch
-'@backstage/backend-defaults': patch
-'@backstage/backend-test-utils': patch
---
-
-Added `pluginId` field to `ActionsServiceAction` type, populated from the registering plugin's metadata.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-module-actions': patch
---
-
-Added `actions` CLI module for listing and executing actions from the distributed actions registry. Includes `actions list`, `actions execute`, and `actions sources` commands for managing plugin sources.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-module-new': patch
---
-
-Added support for the `cli-module` template role for scaffolding new CLI module packages.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Added a new `cli-module` template for creating CLI module packages.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-node': patch
---
-
-Added a new `cli-module` package role for packages that provide CLI plugin extensions.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-react': minor
---
-
-Added `EntityDataTable`, `EntityRelationCard`, `entityDataTableColumns`, `entityColumnPresets`, and related types as alpha exports. These replace `EntityTable` and `RelatedEntitiesCard` (from `@backstage/plugin-catalog`) respectively, providing a unified BUI-based pattern for entity table cards.
@@ -1,5 +0,0 @@
---
-'@backstage/frontend-dev-utils': minor
---
-
-Added `@backstage/frontend-dev-utils`, a new package that provides a minimal helper for wiring up a development app for frontend plugins using the new frontend system. It exports a `createDevApp` function that handles creating and rendering a development app from a `dev/` entry point. The dev app automatically bypasses the sign-in page and loads the `@backstage/ui` CSS. The options interface accepts `features` together with route bindings through `bindRoutes`.
@@ -1,7 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Added `List` and `ListRow` components. These provide a standalone, accessible list of interactive rows built on top of React Aria's `GridList` and `GridListItem` primitives. Rows support icons, descriptions, actions, menus, and single or multiple selection modes.
-
-**Affected components:** List, ListRow
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend-module-gitlab': patch
---
-
-Added `maskedAndHidden` option to `gitlab:projectVariable:create` and `publish:gitlab` action to support creating GitLab project variables that are both masked and hidden. Updated gitbeaker to version 43.8.0 for proper type support.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': minor
---
-
-Added `query-catalog-entities` action to the catalog backend actions registry. Supports predicate-based filtering with `$all`, `$any`, `$not`, `$exists`, `$in`, `$contains`, and `$hasPrefix` operators.
@@ -1,5 +0,0 @@
---
-'@backstage/backend-test-utils': patch
---
-
-Added `cancelTask` to `MockSchedulerService` and mock scheduler service factory.
@@ -1,6 +0,0 @@
---
-'@backstage/backend-plugin-api': minor
-'@backstage/backend-defaults': patch
---
-
-Added `cancelTask` method to the `SchedulerService` interface and implementation, allowing cancellation of currently running scheduled tasks. For global tasks, the database lock is released and a periodic liveness check aborts the running task function. For local tasks, the task's abort signal is triggered directly. A new `POST /.backstage/scheduler/v1/tasks/:id/cancel` endpoint is also available.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-auth-backend': patch
---
-
-Added `who-am-i` action to the auth backend actions registry. Returns the catalog entity and user info for the currently authenticated user.
@@ -1,5 +0,0 @@
---
-'@backstage/core-compat-api': patch
---
-
-Added `withApis`, which is a Higher-Order Component for providing APIs as props to a component via `useApiHolder`.
@@ -1,5 +0,0 @@
---
-'@backstage/backend-defaults': minor
---
-
-The actions registry invoke endpoint now accepts direct user credentials in addition to service principals, enabling CLI and other direct user clients to invoke actions.
@@ -1,5 +0,0 @@
---
-'@backstage/frontend-app-api': patch
---
-
-Frontend apps now respect an explicit `pluginId` on `ApiRef`s when deciding which plugin owns an API factory.
@@ -1,5 +0,0 @@
---
-'@backstage/core-plugin-api': patch
---
-
-Updated `createApiRef` to preserve the direct config call without deprecation warnings while staying compatible with the new frontend API ref typing.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-app-visualizer': patch
---
-
-Switched dev entry point to use `createDevApp` from `@backstage/frontend-dev-utils`.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-auth-backend': patch
---
-
-Added optional client metadata document endpoint at `/.well-known/oauth-client/cli.json` relative to the auth backend base URL for CLI authentication. Enabled when `auth.experimentalClientIdMetadataDocuments.enabled` is set to `true`.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-auth': patch
---
-
-Migrated the ConsentPage UI from Material-UI and `@backstage/core-components` to `@backstage/ui`.
@@ -1,5 +0,0 @@
---
-'@backstage/core-components': patch
---
-
-The login request dialog now handles auth provider icons passed as `IconElement` in addition to `IconComponent`.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-user-settings': patch
---
-
-The `ProviderSettingsItem` `icon` prop now accepts `IconElement` in addition to `IconComponent`.
@@ -1,5 +0,0 @@
---
-'@backstage/frontend-plugin-api': patch
---
-
-The `icon` field on `AuthProviderInfo` now accepts `IconElement` in addition to `IconComponent`, letting you pass `<MyIcon />` instead of `MyIcon`.
@@ -1,5 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Made Accordion a `bg` provider so nested components like Button auto-increment their background level. Updated `useDefinition` to resolve `bg` `propDef` defaults for provider components.
@@ -1,5 +0,0 @@
---
-'@backstage/backend-dynamic-feature-service': patch
---
-
-Fixed `resolvePackagePath` resolution for bundled dynamic plugins. When a plugin bundles its own copy of `@backstage/backend-plugin-api` inside `node_modules`, the `CommonJSModuleLoader` fallback now correctly resolves the plugin's `package.json` by name. Previously the fallback only applied when the resolution originated from the host application; it now also applies when originating from a bundled dependency, which is the case for plugins produced by the `backstage-cli package bundle` command.
@@ -1,5 +0,0 @@
---
-'@backstage/repo-tools': patch
---
-
-Fixed `generate-catalog-info` command failing with "too many arguments" when invoked by lint-staged via the pre-commit hook.
@@ -1,6 +0,0 @@
---
-'@backstage/plugin-search-react': patch
-'@backstage/plugin-search': patch
---
-
-Fixes the search component not registering the first search on navigate to the search page.
@@ -1,5 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Added interactive support to the `Card` component. Pass `onPress` to make the entire card surface pressable, or `href` to make it navigate to a URL. A transparent overlay handles the interaction while nested buttons and links remain independently clickable.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-api-docs': patch
---
-
-Fixed invisible text in parameter input fields when using dark mode in OpenAPI definition pages
@@ -1,11 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Added analytics capabilities to the component library. Components with navigation behavior (Link, ButtonLink, Tab, MenuItem, Tag, Row) now fire analytics events on click when a `BUIProvider` is present.
-
-New exports: `BUIProvider`, `useAnalytics`, `getNodeText`, and associated types (`AnalyticsTracker`, `UseAnalyticsFn`, `BUIProviderProps`, `AnalyticsEventAttributes`).
-
-Components with analytics support now accept a `noTrack` prop to suppress event firing.
-
-**Affected components:** Link, ButtonLink, Tab, MenuItem, Tag, Row
@@ -1,7 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Added a `loading` prop and `data-loading` data attribute to `TableRoot`, allowing consumers to distinguish between stale data and initial loading states. Both `stale` and `loading` set `aria-busy` on the table.
-
-Affected components: TableRoot
@@ -1,7 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Improved the `Table` component loading state to show a skeleton UI with visible headers instead of plain "Loading..." text. The table now renders its full structure during loading, with animated skeleton rows in place of data. The loading state includes proper accessibility support with `aria-busy` on the table and screen reader announcements.
-
-Affected components: Table
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Updated dependency `bfj` to `^9.0.2`.
@@ -1,5 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Fixed neutral-1 hover & pressed state in light mode.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-backend-module-gitlab': patch
---
-
-Added new `gitlab:group:access` scaffolder action to add or remove users and groups as members of GitLab groups. The action supports specifying members via `userIds` and/or `groupIds` array parameters, configurable access levels (Guest, Reporter, Developer, Maintainer, Owner), and defaults to the 'add' action when not specified.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': minor
---
-
-Added support for predicate-based filtering on the `/entities/by-refs` endpoint via the `query` field in the request body. Supports `$all`, `$any`, `$not`, `$exists`, `$in`, `$contains`, and `$hasPrefix` operators.
@@ -1,5 +0,0 @@
---
-'@backstage/catalog-client': minor
---
-
-Added support for the `query` field in `getEntitiesByRefs` requests, enabling predicate-based filtering with `$all`, `$any`, `$not`, `$exists`, `$in`, `$contains`, and `$hasPrefix` operators.
@@ -1,7 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Migrated all components from `useStyles` to `useDefinition` hook. Exported `OwnProps` types for each component, enabling better type composition for consumers.
-
-**Affected components:** Avatar, Checkbox, Container, Dialog, FieldError, FieldLabel, Flex, FullPage, Grid, HeaderPage, Link, Menu, PasswordField, PluginHeader, Popover, RadioGroup, SearchField, Select, Skeleton, Switch, Table, TablePagination, Tabs, TagGroup, Text, TextField, ToggleButton, ToggleButtonGroup, Tooltip, VisuallyHidden
@@ -1,7 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Fixed interactive cards so that CardBody can scroll when the card has a constrained height. Previously, the overlay element blocked scroll events.
-
-**Affected components:** Card
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-catalog-backend': patch
---
-
-Improved catalog entity deletion so parent invalidation and deferred relation restitch scheduling are coordinated more safely.
@@ -1,7 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Removed the `transition` on `Container` padding to prevent an unwanted animation when the viewport is resized.
-
-Affected components: Container
@@ -1,5 +0,0 @@
---
-'@backstage/cli-common': patch
---
-
-The `findOwnRootDir` utility now searches for the monorepo root by traversing up the directory tree looking for a `package.json` with `workspaces`, instead of assuming a fixed `../..` relative path. If no workspaces root is found during this traversal, `findOwnRootDir` now throws to enforce stricter validation of the repository layout.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-module-maintenance': patch
---
-
-Added auto-fill of `backstage.pluginPackage` metadata for known plugins during `repo fix`.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': minor
---
-
-Added new `auth` command group for authenticating the CLI with Backstage instances using OAuth 2.0 with a pre-registered client metadata document. Commands include `login`, `logout`, `list`, `show`, `print-token`, and `select` for managing multiple authenticated instances.
@@ -1,28 +0,0 @@
---
-'@backstage/cli-common': minor
---
-
-Added `targetPaths` and `findOwnPaths` as replacements for `findPaths`, with a cleaner separation between target project paths and package-relative paths.
-
-To migrate existing `findPaths` usage:
-
-```ts
-// Before
-import { findPaths } from '@backstage/cli-common';
-const paths = findPaths(__dirname);
-
-// After — for target project paths (cwd-based):
-import { targetPaths } from '@backstage/cli-common';
-// paths.targetDir    → targetPaths.dir
-// paths.targetRoot   → targetPaths.rootDir
-// paths.resolveTarget('src')      → targetPaths.resolve('src')
-// paths.resolveTargetRoot('yarn.lock') → targetPaths.resolveRoot('yarn.lock')
-
-// After — for package-relative paths:
-import { findOwnPaths } from '@backstage/cli-common';
-const own = findOwnPaths(__dirname);
-// paths.ownDir       → own.dir
-// paths.ownRoot      → own.rootDir
-// paths.resolveOwn('config/jest.js')    → own.resolve('config/jest.js')
-// paths.resolveOwnRoot('tsconfig.json') → own.resolveRoot('tsconfig.json')
-```
@@ -1,5 +0,0 @@
---
-'@backstage/cli-common': patch
---
-
-Fixed `runCheck` to ignore stdio of the spawned process, preventing unwanted output from leaking to the terminal.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-defaults': patch
---
-
-Added `@backstage/cli-module-actions` to the default set of CLI modules.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-defaults': minor
---
-
-Introduced `@backstage/cli-defaults`, a convenience package that bundles all standard Backstage CLI modules. Install this single package as a `devDependency` to get the full default set of CLI commands without listing each module individually.
@@ -1,41 +0,0 @@
---
-'@backstage/cli': minor
---
-
-The CLI now automatically discovers CLI modules from the project root's `dependencies` and `devDependencies`. Any installed package with the `cli-module` Backstage role will be loaded automatically without needing to be hardcoded in the CLI itself.
-
-If no CLI modules are found in the project dependencies, the CLI falls back to the built-in set of modules and prints a deprecation warning. This fallback will be removed in a future release. To prepare for this, add `@backstage/cli-defaults` as a `devDependency` in your root `package.json`:
-
-```json
-{
-  "devDependencies": {
-    "@backstage/cli-defaults": "backstage:^"
-  }
-}
-```
-
-If you are not using the Backstage Yarn plugin, run the following instead:
-
-```sh
-yarn workspace root add --dev @backstage/cli-defaults
-```
-
-For fine-grained control you can instead install individual CLI modules:
-
-```json
-{
-  "devDependencies": {
-    "@backstage/cli-module-auth": "backstage:^",
-    "@backstage/cli-module-build": "backstage:^",
-    "@backstage/cli-module-config": "backstage:^",
-    "@backstage/cli-module-github": "backstage:^",
-    "@backstage/cli-module-info": "backstage:^",
-    "@backstage/cli-module-lint": "backstage:^",
-    "@backstage/cli-module-maintenance": "backstage:^",
-    "@backstage/cli-module-migrate": "backstage:^",
-    "@backstage/cli-module-new": "backstage:^",
-    "@backstage/cli-module-test-jest": "backstage:^",
-    "@backstage/cli-module-translations": "backstage:^"
-  }
-}
-```
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Internal refactor of CLI modularization, moving individual commands to be implemented with cleye.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Internal refactor of the CLI command registration
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Internal refactor to use new concurrency utilities from `@backstage/cli-node`.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Internal refactor to move shared utilities into their consuming modules, reducing cross-module dependencies.
@@ -1,16 +0,0 @@
---
-'@backstage/cli': minor
---
-
-**BREAKING**: The CLI templates for frontend plugins have been renamed:
-
- `new-frontend-plugin` → `frontend-plugin`
- `new-frontend-plugin-module` → `frontend-plugin-module`
- `frontend-plugin` (legacy) → `legacy-frontend-plugin`
-
-To smooth out this breaking change, the CLI now auto-detects which frontend system your app uses based on the dependencies in `packages/app/package.json`. When using the default templates (no explicit `templates` configuration):
-
- Apps using `@backstage/frontend-defaults` will see the new frontend system templates (`frontend-plugin`, `frontend-plugin-module`)
- Apps using `@backstage/app-defaults` will see the legacy template (displayed as `frontend-plugin`)
-
-This means existing projects that haven't migrated to the new frontend system will continue to create legacy plugins by default, while new projects will get the new frontend system templates. If you have explicit template configuration in your `package.json`, it will be used as-is without any auto-detection.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-node': minor
---
-
-Added `createCliModule` API and related types for building Backstage CLI plugins.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-node': patch
---
-
-Added `CliAuth` class for managing CLI authentication state. This provides a class-based API with a static `create` method that resolves the currently selected (or explicitly named) auth instance, transparently refreshes expired access tokens, and exposes helpers for other CLI modules to authenticate with a Backstage backend.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-node': patch
---
-
-Added `toString()` method to `Lockfile` for serializing lockfiles back to string format.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-node': patch
---
-
-Added `runConcurrentTasks` and `runWorkerQueueThreads` utilities, moved from the `@backstage/cli` internal code.
@@ -1,5 +0,0 @@
---
-'@backstage/cli-module-build': minor
---
-
-Added `package bundle` command to create self-contained plugin bundles for dynamic loading, to be used by the `backend-dynamic-feature-service`. Supports backend and frontend plugins, with optional `--pre-packed-dir` for batch bundling from a pre-built workspace.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': minor
---
-
-**BREAKING**: The `migrate package-exports` command has been removed. Use `repo fix` instead.
@@ -1,5 +0,0 @@
---
-'@backstage/repo-tools': patch
---
-
-Updated the CLI report parser to support cleye-style help output, and strip ANSI escape codes from captured output.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Internal refactor to split `loadCliConfig` into separate implementations for the build and config CLI modules, removing a cross-module dependency.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Added support for the new `cli-module` package role in the build system, ESLint configuration, Jest configuration, and maintenance commands.
@@ -1,9 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Added `translations export` and `translations import` commands for managing translation files.
-
-The `translations export` command discovers all `TranslationRef` definitions across frontend plugin dependencies and exports their default messages as JSON files. The `translations import` command generates `TranslationResource` wiring code from translated JSON files, ready to be plugged into the app.
-
-Both commands support a `--pattern` option for controlling the message file layout, for example `--pattern '{lang}/{id}.json'` for language-based directory grouping.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Migrated CLI plugin modules to use `createCliModule` from `@backstage/cli-node`.
@@ -1,5 +0,0 @@
---
-'@backstage/cli': patch
---
-
-Migrated internal versioning utilities to use `@backstage/cli-node` instead of a local implementation.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-devtools': patch
---
-
-Fixed URL encoding of task IDs for the trigger feature (tasks that contained a "/" in their ID were not triggered)
@@ -1,5 +0,0 @@
---
-'@backstage/core-app-api': patch
---
-
-Added `BUIProvider` from `@backstage/ui` to the app shell provider tree, enabling BUI components to fire analytics events through the Backstage analytics system.
@@ -1,5 +0,0 @@
---
-'@backstage/core-compat-api': patch
---
-
-Added a missing dependency on `@backstage/filter-predicates` to `@backstage/core-compat-api`. This fixes package metadata for consumers that use compatibility helpers relying on filter predicate support.
@@ -1,5 +0,0 @@
---
-'@backstage/core-components': patch
---
-
-Fixed the shared `Progress` component to provide an accessible name for its loading indicator by default.
@@ -1,6 +0,0 @@
---
-'@backstage/plugin-techdocs-backend': patch
-'@backstage/plugin-techdocs-node': patch
---
-
-Added `techdocs.generator.mkdocs.dangerouslyAllowAdditionalKeys` configuration option to explicitly bypass MkDocs configuration key restrictions. This enables support for additional MkDocs configuration keys beyond the default safe allow list, such as the `hooks` key which some MkDocs plugins require.
@@ -1,5 +0,0 @@
---
-'@backstage/create-app': patch
---
-
-The create-app templates now include `@backstage/cli-defaults` as a `devDependency`, enabling the CLI's automatic module discovery for newly created projects.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder-node': patch
---
-
-Added `removeFiles` helper function for staging file removals in Git.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-notifications-backend-module-slack': minor
---
-
-**BREAKING**: Only send direct messages to user entity recipients. Notifications sent to non-user entities no longer send Slack direct messages to resolved users.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-techdocs-node': patch
---
-
-Removed `INHERIT` from the `ALLOWED_MKDOCS_KEYS` set to address a security concern with MkDocs configuration inheritance.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-scaffolder': patch
---
-
-Removed check for deprecated `bitbucket` integration from `repoPickerValidation` function used by the `RepoUrlPicker`, it now validates the `bitbucketServer` and `bitbucketCloud` integrations instead.
@@ -1,21 +0,0 @@
---
-'@backstage/ui': minor
---
-
-**BREAKING**: Simplified the neutral background prop API for container components. The explicit `neutral-1`, `neutral-2`, `neutral-3`, and `neutral-auto` values have been removed from `ProviderBg`. They are replaced by a single `'neutral'` value that always auto-increments from the parent context, making it impossible to skip or pin to an explicit neutral level.
-
-**Migration:**
-
-Replace any explicit `bg="neutral-1"`, `bg="neutral-2"`, `bg="neutral-3"`, or `bg="neutral-auto"` props with `bg="neutral"`. To achieve a specific neutral level in stories or tests, use nested containers — each additional `bg="neutral"` wrapper increments by one level.
-
-```tsx
-// Before
-<Box bg="neutral-2">...</Box>
-
-// After
-<Box bg="neutral">
-  <Box bg="neutral">...</Box>
-</Box>
-```
-
-**Affected components:** Box, Flex, Grid, Card, Accordion, Popover, Tooltip, Dialog, Menu
@@ -1,5 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Fixed --bui-fg-success token in light mode to be more accessible.
@@ -1,5 +0,0 @@
---
-'@backstage/backend-defaults': minor
---
-
-The scheduler service now uses the metrics service to create metrics, providing plugin-scoped attribution.
@@ -1,5 +0,0 @@
---
-'@backstage/repo-tools': minor
---
-
-Added support for OpenAPI 3.1 to all `schema openapi` commands. The commands now auto-detect the OpenAPI version from the spec file and use the appropriate generator, supporting both OpenAPI 3.0.x and 3.1.x specifications.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-techdocs': patch
---
-
-chore(deps): bump `dompurify` from 3.3.1 to 3.3.2
@@ -1,5 +0,0 @@
---
-'@backstage/backend-defaults': patch
---
-
-chore(deps): bump `yauzl` from 3.2.0 to 3.2.1
@@ -1,11 +0,0 @@
---
-'@backstage/backend-defaults': patch
-'@backstage/cli': patch
-'@backstage/eslint-plugin': patch
-'@backstage/repo-tools': patch
-'@backstage/plugin-auth-backend': patch
-'@backstage/plugin-catalog-backend-module-github': patch
-'@backstage/plugin-catalog-backend': patch
---
-
-build(deps): bump `minimatch` from 9.0.5 to 10.2.1
@@ -1,5 +0,0 @@
---
-'@backstage/core-app-api': patch
---
-
-Deprecated `AlertApiForwarder` in favor of the new `ToastApi`. The `AlertApiForwarder` now emits a console warning on first use, guiding developers to migrate to `ToastApi` from `@backstage/frontend-plugin-api`.
@@ -1,5 +0,0 @@
---
-'@backstage/core-plugin-api': patch
---
-
-Deprecated `AlertApi`, `AlertMessage`, and `alertApiRef` in favor of the new `ToastApi` from `@backstage/frontend-plugin-api`.
@@ -1,55 +0,0 @@
---
-'@backstage/frontend-plugin-api': patch
---
-
-Deprecated `AlertApi` in favor of the new `ToastApi`.
-
-`AlertApi` is now deprecated and will be removed in a future release. Please migrate to `ToastApi` which provides richer notification features.
-
-**Why migrate?**
-
-`ToastApi` offers enhanced capabilities over `AlertApi`:
-
- **Title and Description**: Display a prominent title with optional description text
- **Action Links**: Include clickable links within notifications
- **Status Variants**: Support for neutral, info, success, warning, and danger statuses
- **Per-toast Timeout**: Control auto-dismiss timing for each notification individually
- **Programmatic Dismiss**: Close notifications via the `close()` handle returned from `post()`
-
-**Migration Guide**
-
-| AlertApi                                     | ToastApi                                   |
-| -------------------------------------------- | ------------------------------------------ |
-| `message: string`                            | `title: ReactNode`                         |
-| `severity: 'error'`                          | `status: 'danger'`                         |
-| `severity: 'success' \| 'info' \| 'warning'` | `status: 'success' \| 'info' \| 'warning'` |
-| `display: 'transient'`                       | `timeout: 5000` (or custom ms)             |
-| `display: 'permanent'`                       | omit `timeout`                             |
-| `post()` returns `void`                      | `post()` returns `{ close(): void }`       |
-
-**Example Migration**
-
-```typescript
-// Before (AlertApi)
-import { alertApiRef, useApi } from '@backstage/core-plugin-api';
-
-const alertApi = useApi(alertApiRef);
-alertApi.post({
-  message: 'Entity saved successfully',
-  severity: 'success',
-  display: 'transient',
-});
-
-// After (ToastApi)
-import { toastApiRef, useApi } from '@backstage/frontend-plugin-api';
-
-const toastApi = useApi(toastApiRef);
-const toast = toastApi.post({
-  title: 'Entity saved successfully',
-  status: 'success',
-  timeout: 5000,
-});
-// Later: toast.close() to dismiss programmatically
-```
-
-**Note**: During the migration period, both APIs work simultaneously. The `ToastDisplay` component subscribes to both `AlertApi` and `ToastApi`, so existing code continues to work while you migrate incrementally.
@@ -1,5 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Deprecated the `HeaderPage` component name in favor of `Header`. The old `HeaderPage`, `HeaderPageProps`, `HeaderPageOwnProps`, `HeaderPageBreadcrumb`, and `HeaderPageDefinition` exports are still available as deprecated aliases.
@@ -1,5 +0,0 @@
---
-'@backstage/frontend-test-utils': patch
---
-
-Deprecated standalone mock API exports in favor of the `mockApis` namespace. This includes the mock classes (`MockAlertApi`, `MockAnalyticsApi`, `MockConfigApi`, `MockErrorApi`, `MockFetchApi`, `MockFeatureFlagsApi`, `MockPermissionApi`, `MockStorageApi`, `MockTranslationApi`), their option types (`MockErrorApiOptions`, `MockFeatureFlagsApiOptions`), and the `ErrorWithContext` type. `MockFetchApiOptions` is kept as a non-deprecated export. Use the `mockApis` namespace instead, for example `mockApis.alert()` or `mockApis.alert.mock()`.
@@ -1,5 +0,0 @@
---
-'@backstage/frontend-plugin-api': patch
---
-
-Deprecated `NavItemBlueprint`. Nav items are now automatically inferred from `PageBlueprint` extensions based on their `title` and `icon` params.
@@ -1,5 +0,0 @@
---
-'@backstage/frontend-plugin-api': patch
---
-
-Deprecated `withApis`, use the `withApis` export from `@backstage/core-compat-api` instead.
@@ -1,6 +0,0 @@
---
-'@backstage/plugin-devtools-common': patch
-'@backstage/plugin-devtools': patch
---
-
-Added `cancelScheduledTask` to the DevTools API and a cancel button to the scheduled tasks UI.
@@ -1,16 +0,0 @@
---
-'@backstage/plugin-api-docs': patch
-'@backstage/plugin-catalog': patch
-'@backstage/plugin-catalog-graph': patch
-'@backstage/plugin-catalog-import': patch
-'@backstage/plugin-catalog-unprocessed-entities': patch
-'@backstage/plugin-devtools': patch
-'@backstage/plugin-home': patch
-'@backstage/plugin-kubernetes': patch
-'@backstage/plugin-mui-to-bui': patch
-'@backstage/plugin-org': patch
-'@backstage/plugin-scaffolder': patch
-'@backstage/plugin-user-settings': patch
---
-
-Updated installation documentation to use feature discovery as the default.
@@ -1,5 +0,0 @@
---
-'@backstage/ui': patch
---
-
-Added documentation for the table cell wrapper requirement to TSDoc comments for `Cell`, `CellText`, `CellProfile`, `ColumnConfig`, and `RowRenderFn`.
@@ -1,8 +0,0 @@
---
-'@backstage/core-plugin-api': patch
-'@backstage/core-app-api': patch
-'@backstage/frontend-plugin-api': patch
-'@backstage/frontend-app-api': patch
---
-
-Add optional `description` field to plugin-level feature flags.
@@ -1,16 +0,0 @@
---
-'@backstage/ui': minor
---
-
-**BREAKING**: Removed `--bui-bg-popover` CSS token. Popover, Tooltip, Menu, and Dialog now use `--bui-bg-app` for their outer shell and `Box bg="neutral-1"` for content areas, providing better theme consistency and eliminating a redundant token.
-
-**Migration:**
-
-Replace any usage of `--bui-bg-popover` with `--bui-bg-neutral-1` (for content surfaces) or `--bui-bg-app` (for outer shells):
-
-```diff
- background: var(--bui-bg-popover);
-+ background: var(--bui-bg-neutral-1);
-```
-
-**Affected components:** Popover, Tooltip, Menu, Dialog
@@ -1,6 +0,0 @@
---
-'@backstage/catalog-client': minor
-'@backstage/plugin-catalog-backend': minor
---
-
-Add an `onConflict` option to location creation that can refresh an existing location instead of throwing a conflict error.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-api-docs': patch
---
-
-Added default entity content groups for the API docs entity content tabs. The API definition tab defaults to the `documentation` group and the APIs tab defaults to the `development` group.
@@ -1,5 +0,0 @@
---
-'@backstage/plugin-techdocs': patch
---
-
-Added `documentation` as the default entity content group for the TechDocs entity content tab.
--- a/Show More
+++ b/Show More