Skip to content

fix(deps): update backstage monorepo#25

Merged
yumike merged 1 commit into
mainfrom
renovate/backstage-monorepo
Mar 23, 2026
Merged

fix(deps): update backstage monorepo#25
yumike merged 1 commit into
mainfrom
renovate/backstage-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 18, 2026 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@backstage/backend-defaults (source) ^0.15.2 → ^0.16.0 age confidence
@backstage/backend-plugin-api (source) 1.7.0 → 1.8.0 age confidence
@backstage/backend-test-utils (source) 1.11.0 → 1.11.1 age confidence
@backstage/catalog-model (source) 1.7.6 → 1.7.7 age confidence
@backstage/cli (source) ^0.35.0 → ^0.36.0 age confidence
@backstage/core-components (source) 0.18.7 → 0.18.8 age confidence
@backstage/core-plugin-api (source) 1.12.3 → 1.12.4 age confidence
@backstage/frontend-defaults (source) ^0.4.0 → ^0.5.0 age confidence
@backstage/frontend-plugin-api (source) ^0.14.0 → ^0.15.0 age confidence
@backstage/plugin-app-backend (source) 0.5.11 → 0.5.12 age confidence
@backstage/plugin-app-react (source) 0.2.0 → 0.2.1 age confidence
@backstage/plugin-auth-backend (source) 0.27.1 → 0.27.3 age confidence
@backstage/plugin-auth-backend-module-guest-provider (source) 0.2.16 → 0.2.17 age confidence
@backstage/plugin-catalog-backend (source) 3.4.0 → 3.5.0 age confidence
@backstage/plugin-catalog-backend-module-scaffolder-entity-model (source) 0.2.17 → 0.2.18 age confidence
@backstage/plugin-catalog-react (source) 2.0.0 → 2.1.0 age confidence
@backstage/plugin-permission-backend (source) 0.7.9 → 0.7.10 age confidence
@backstage/plugin-permission-backend-module-allow-all-policy (source) 0.2.16 → 0.2.17 age confidence
@backstage/plugin-user-settings (source) 0.9.0 → 0.9.1 age confidence
@backstage/test-utils (source) 1.7.15 → 1.7.16 age confidence

Release Notes

backstage/backstage (@​backstage/backend-defaults)

v0.16.0

Compare Source

Minor Changes
  • 42960f1: 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.
  • 0e7d8f9: The scheduler service now uses the metrics service to create metrics, providing plugin-scoped attribution.
  • 527cf88: BREAKING Removed deprecated BitbucketUrlReader. Use the BitbucketCloudUrlReader or the BitbucketServerUrlReader instead.
Patch Changes
  • cc8348e: 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.
  • dee4283: Added pluginId field to ActionsServiceAction type, populated from the registering plugin's metadata.
  • 015668c: 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.
  • 638e6c7: chore(deps): bump yauzl from 3.2.0 to 3.2.1
  • 6738cf0: build(deps): bump minimatch from 9.0.5 to 10.2.1
  • 62f0a53: Fixed error forwarding in the actions registry so that known errors like InputError and NotFoundError thrown by actions preserve their original status codes and messages instead of being wrapped in ForwardedError and coerced to 500.
  • d933f62: Add configurable throttling and retry mechanism for GitLab integration.
  • b99158a: Fixed yarn backstage-cli config:check --strict --config app-config.yaml config validation error by adding
    an optional default type discriminator to PostgreSQL connection configuration,
    allowing config:check to properly validate default connection configurations.
  • 1ee5b28: Adds an alpha MetricsService to provide a unified interface for metrics instrumentation across Backstage plugins.
  • 5fcbef2: Updated dependency express-rate-limit to ^8.0.0.
  • a49a40d: Updated dependency zod to ^3.25.76 || ^4.0.0 & migrated to /v3 or /v4 imports.
  • Updated dependencies
backstage/backstage (@​backstage/backend-plugin-api)

v1.8.0

Compare Source

Minor Changes

  • cc8348e: Added optional visibilityPermission field to ActionsRegistryActionOptions, allowing actions to declare a BasicPermission that controls visibility and access.

    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.

  • 015668c: 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.

Patch Changes
backstage/backstage (@​backstage/backend-test-utils)

v1.11.1

Compare Source

Patch Changes
backstage/backstage (@​backstage/catalog-model)

v1.7.7

Compare Source

Patch Changes
  • a49a40d: Updated dependency zod to ^3.25.76 || ^4.0.0 & migrated to /v3 or /v4 imports.
backstage/backstage (@​backstage/cli)

v0.36.0

Compare Source

Minor Changes

  • d0f4cd2: 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.

  • d806b0c: 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:

    {
  "devDependencies": {
    "@​backstage/cli-defaults": "backstage:^"
  }
}

    If you are not using the Backstage Yarn plugin, run the following instead:

    yarn workspace root add --dev @​backstage/cli-defaults

    For fine-grained control you can instead install individual CLI modules:

    {
  "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:^"
  }
}

  • 08d9770: 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.

  • b36a60d: BREAKING: The migrate package-exports command has been removed. Use repo fix instead.

Patch Changes

  • edf2b77: Added a new cli-module template for creating CLI module packages.

  • 246877a: Updated dependency bfj to ^9.0.2.

  • 0d2d0f2: Internal refactor of CLI modularization, moving individual commands to be implemented with cleye.

  • a4e5902: Internal refactor of the CLI command registration

  • bba2e49: Internal refactor to use new concurrency utilities from @backstage/cli-node.

  • 2fcba39: Internal refactor to move shared utilities into their consuming modules, reducing cross-module dependencies.

  • c85ac86: Internal refactor to split loadCliConfig into separate implementations for the build and config CLI modules, removing a cross-module dependency.

  • 94a885a: Added support for the new cli-module package role in the build system, ESLint configuration, Jest configuration, and maintenance commands.

  • fd50cb3: 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.

  • 0be3eab: Migrated CLI plugin modules to use createCliModule from @backstage/cli-node.

  • 61cb976: Migrated internal versioning utilities to use @backstage/cli-node instead of a local implementation.

  • 6738cf0: build(deps): bump minimatch from 9.0.5 to 10.2.1

  • ff4a45a: Migrated remaining CLI command handlers from commander to cleye for argument parsing. Several camelCase CLI flags have been deprecated in favor of their kebab-case equivalents (e.g. --successCache → --success-cache). The old camelCase forms still work but will now log a deprecation warning. Please update any scripts or CI configurations to use the kebab-case versions.

  • 70fc178: Migrated from deprecated findPaths to targetPaths and findOwnPaths from @backstage/cli-common.

  • 825c81d: Internal refactor of CLI command modules.

  • ea90ab0: The built-in yarn new templates have been moved to @backstage/cli-module-new. Existing references to @backstage/cli/templates/* in your root package.json will continue to work through a backwards compatibility rewrite in the new command.

  • ebeb0d4: Updated the new frontend plugin template to use @backstage/frontend-dev-utils in its dev/ entry point instead of wiring createApp manually. Generated plugins now get the same dev app helper setup as the built-in examples.

  • 971cc94: The new command now prompts for the plugin package name when creating plugin modules, in order to properly populate the package.json file.

  • de62a9d: Upgraded commander dependency from ^12.0.0 to ^14.0.3 across all CLI packages.

  • 092b41f: Updated dependency webpack to ~5.105.0.

  • 4a75544: Updated dependency react-refresh to ^0.18.0.

  • a9d23c4: Properly support package.json workspaces field

  • Updated dependencies

backstage/backstage (@​backstage/core-components)

v0.18.8

Compare Source

Patch Changes
  • e26e3de: The login request dialog now handles auth provider icons passed as IconElement in addition to IconComponent.
  • 8e09233: Fixed the shared Progress component to provide an accessible name for its loading indicator by default.
  • 8b1a847: Fixed Table component layout when both filters and title props are used together. The filter controls now use a dedicated CSS class (filterControls) instead of incorrectly reusing the root container class.
  • 3f36ce1: Clarified the IconElement sizing contract for the new frontend system and aligned legacy system icon rendering with the new icon API.
  • 0be2541: Promoted the plugin's translation ref to the stable package entry point. It was previously only available through the alpha entry point.
  • a49a40d: Updated dependency zod to ^3.25.76 || ^4.0.0 & migrated to /v3 or /v4 imports.
  • 470f72d: The LogViewer component from @backstage/core-components now supports downloading logs if a callback is passed to onDownloadLogs
  • Updated dependencies
backstage/backstage (@​backstage/core-plugin-api)

v1.12.4

Compare Source

Patch Changes
  • d911b72: Updated createApiRef to preserve the direct config call without deprecation warnings while staying compatible with the new frontend API ref typing.
  • 59752a2: Deprecated AlertApi, AlertMessage, and alertApiRef in favor of the new ToastApi from @backstage/frontend-plugin-api.
  • 0452d02: Add optional description field to plugin-level feature flags.
  • a49a40d: Updated dependency zod to ^3.25.76 || ^4.0.0 & migrated to /v3 or /v4 imports.
  • fe848e0: Changed useApiHolder to return an empty ApiHolder instead of throwing when used outside of an API context.
  • Updated dependencies
backstage/backstage (@​backstage/frontend-defaults)

v0.5.0

Compare Source

Minor Changes
  • 92af1ae: BREAKING: Removed the allowUnknownExtensionConfig option from createApp. This flag had no effect and was a no-op, so no behavioral changes are expected.
  • 33de79d: BREAKING: Removed the deprecated createPublicSignInApp function. Use createApp from @backstage/frontend-defaults with appModulePublicSignIn from @backstage/plugin-app/alpha instead.
Patch Changes
backstage/backstage (@​backstage/frontend-plugin-api)

v0.15.1

Compare Source

v0.15.0

Compare Source

Minor Changes

  • 5fd78ba: Renamed PluginOptions to CreateFrontendPluginOptions and deprecated the old name. Removed ResolvedExtensionInputs from the main entry point; it is still available as an inline type in extension factory signatures.

  • 72991a5: Removed the ResolvedExtensionInput and ExtensionDataRefToValue helper types from the public API surface to reduce top-level API clutter. These types were internal plumbing that are not needed by plugin authors. If you were relying on ResolvedExtensionInput, use the ResolvedExtensionInputs type instead, which maps a full set of inputs. If you were using ExtensionDataRefToValue, replace it with ExtensionDataValue combined with inferred types from your ExtensionDataRef.

  • 9508514: BREAKING: Promoted PluginWrapperApi, pluginWrapperApiRef, PluginWrapperBlueprint, and the new PluginWrapperDefinition type from @alpha to @public. These are now available from the main package entry point rather than only through /alpha.

    The PluginWrapperApi type now has a required getRootWrapper() method that returns a root wrapper component. The pluginWrapperApiRef ID changed from core.plugin-wrapper.alpha to core.plugin-wrapper.

    The PluginWrapperBlueprint now accepts PluginWrapperDefinition as the loader return type, which supports an optional useWrapperValue hook that allows sharing state between wrapper instances.

  • 6573901: BREAKING: Removed the deprecated AnyExtensionDataRef type. Use ExtensionDataRef without type parameters instead.

  • a9440f0: BREAKING: Simplified the ExtensionAttachTo type to only support a single attachment target. The array form for attaching to multiple extension points has been removed. Also removed the deprecated ExtensionAttachToSpec type alias.

Patch Changes

  • e26e3de: The icon field on AuthProviderInfo now accepts IconElement in addition to IconComponent, letting you pass <MyIcon /> instead of MyIcon.

  • eea95b8: 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

    // Before (AlertApi)
import { alertApiRef, useApi } from '@&#8203;backstage/core-plugin-api';

const alertApi = useApi(alertApiRef);
alertApi.post({
  message: 'Entity saved successfully',
  severity: 'success',
  display: 'transient',
});

// After (ToastApi)
import { toastApiRef, useApi } from '@&#8203;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.

  • 8a3a906: Deprecated NavItemBlueprint. Nav items are now automatically inferred from PageBlueprint extensions based on their title and icon params.

  • b15a685: Deprecated withApis, use the withApis export from @backstage/core-compat-api instead.

  • 0452d02: Add optional description field to plugin-level feature flags.

  • 1bec049: Fixed inconsistent JSX.Element type reference in the DialogApiDialog.update method signature.

  • 9c81af9: Made the pluginId property optional in the FrontendFeature type, allowing plugins published against older versions of the framework to be used without type errors.

  • 2c383b5: Deprecated AnalyticsImplementationBlueprint and AnalyticsImplementationFactory in favor of the exports from @backstage/plugin-app-react.

  • dab6c46: Deprecated the ExtensionFactoryMiddleware type, which has been moved to @backstage/frontend-app-api.

  • aa29b50: Pages created with PageBlueprint now render the plugin header by default in the new frontend system.

  • 3f36ce1: Clarified the IconElement sizing contract for the new frontend system and aligned legacy system icon rendering with the new icon API.

  • cc459f7: Added a builder form for createApiRef in the new frontend system and deprecated the direct createApiRef({ ... }) call in favor of createApiRef().with({ ... }). The builder form now also preserves literal API ref IDs in the resulting ApiRef type.

    The createApiRef().with({ ... }) form can also use an explicit pluginId to declare API ownership without encoding the plugin ID into the API ref ID, while keeping that metadata internal to runtime handling.

  • 5b160f9: Added support for if predicates on createFrontendPlugin and createFrontendModule, applying shared conditions to every extension in the feature. Plugin and extension overrides can now also replace or remove existing if predicates.

  • d0206c4: Removed the deprecated defaultPath migration helper from PageBlueprint params.

  • edb872c: Renamed the PageTab type to PageLayoutTab. The old PageTab name is now a deprecated type alias.

  • a49a40d: Updated dependency zod to ^3.25.76 || ^4.0.0 & migrated to /v3 or /v4 imports.

  • 7e743f4: Introduced a new ToastApi for displaying rich toast notifications in the new frontend system.

    The new ToastApi provides enhanced notification capabilities compared to the existing AlertApi:

    • Title and Description: Toasts support both a title and an optional description
    • Custom Timeouts: Each toast can specify its own timeout duration
    • Links: Toasts can include action links
    • Status Variants: Support for neutral, info, success, warning, and danger statuses
    • Programmatic Dismiss: Toasts can be dismissed programmatically using the close() handle returned from post()

    Usage:

    import { toastApiRef, useApi } from '@&#8203;backstage/frontend-plugin-api';

const toastApi = useApi(toastApiRef);

// Full-featured toast
toastApi.post({
  title: 'Entity saved',
  description: 'Your changes have been saved successfully.',
  status: 'success',
  timeout: 5000,
  links: [{ label: 'View entity', href: '/catalog/entity' }],
});

// Programmatic dismiss
const { close } = toastApi.post({ title: 'Uploading...', status: 'info' });
// Later...
close();

    The ToastDisplay component subscribes to both ToastApi and AlertApi, providing a migration path where both systems work side by side until AlertApi is fully deprecated.

  • fe848e0: Changed useApiHolder to return an empty ApiHolder instead of throwing when used outside of an API context.

  • Updated dependencies

backstage/backstage (@​backstage/plugin-app-backend)

v0.5.12

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-app-react)

v0.2.1

Compare Source

Patch Changes
  • 5f3f5d2: NavContentBlueprint nav item collections now keep previously collected rest() results in sync when additional items are taken later in the same render, making it easier to place items across multiple sidebar sections.
  • 2c383b5: Added AnalyticsImplementationBlueprint and AnalyticsImplementationFactory, migrated from @backstage/frontend-plugin-api.
  • Updated dependencies
backstage/backstage (@​backstage/plugin-auth-backend)

v0.27.3

Compare Source

v0.27.2

Compare Source

Patch Changes
  • 1ccad86: Added who-am-i action to the auth backend actions registry. Returns the catalog entity and user info for the currently authenticated user.
  • d0f4cd2: 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.
  • 6738cf0: build(deps): bump minimatch from 9.0.5 to 10.2.1
  • e9b6e97: Fixed a security vulnerability where the CIMD metadata fetch could follow HTTP redirects to internal hosts, bypassing SSRF protections.
  • 0f9d673: Improved redirect URI validation in the experimental OIDC provider to match against normalized URLs rather than raw strings.
  • a49a40d: Updated dependency zod to ^3.25.76 || ^4.0.0 & migrated to /v3 or /v4 imports.
  • 634eded: Fixed a foreign key constraint violation when issuing refresh tokens for CIMD clients, and
    prevented a failed refresh token issuance from failing the entire token exchange.
    Fixed AWS ALB auth provider incorrectly returning HTTP 500 instead of 401 for JWT validation failures,
    which caused retry loops and memory pressure under load.
  • 619be54: Update migrations to be reversible
  • Updated dependencies
backstage/backstage (@​backstage/plugin-auth-backend-module-guest-provider)

v0.2.17

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-catalog-backend)

v3.5.0

Compare Source

Minor Changes

  • a6b2819: 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.

  • 972f686: 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.

  • 5d95e8e: Add an onConflict option to location creation that can refresh an existing location instead of throwing a conflict error.

  • 56c908e: Added support for predicate-based filtering on the /entity-facets endpoint via a new POST method. Supports $all, $any, $not, $exists, $in, $contains, and $hasPrefix operators.

  • 0fbcf23: Migrated OpenAPI schemas to 3.1.

  • bf71677: Added opentelemetry metrics for SCM events:

    • catalog.events.scm.messages with attribute eventType: Counter for the number of SCM events actually received by the catalog backend. The eventType is currently either location or repository.

  • 51e23eb: Added predicate-based entity filtering via POST /entities/by-query endpoint.

    Supports $all, $any, $not, $exists, $in, $hasPrefix, and (partially) $contains operators for expressive entity queries. Integrated into the existing queryEntities flow with full cursor-based pagination, permission enforcement, and totalItems support.

    The catalog client's queryEntities() method automatically routes to the POST endpoint when a query predicate is provided.

Patch Changes
backstage/backstage (@​backstage/plugin-catalog-backend-module-scaffolder-entity-model)

v0.2.18

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from 643fce3 to 0b40b82 Compare March 22, 2026 17:22
@renovate renovate Bot force-pushed the renovate/backstage-monorepo branch from 0b40b82 to 6842d84 Compare March 23, 2026 17:46
@yumike yumike merged commit 1ff11cd into main Mar 23, 2026
1 check passed
@yumike yumike deleted the renovate/backstage-monorepo branch March 23, 2026 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@yumike