Skip to content

fix(deps): update backstage core#974

Merged
secustor merged 2 commits intomainfrom
renovate/backstage-core
Feb 1, 2026
Merged

fix(deps): update backstage core#974
secustor merged 2 commits intomainfrom
renovate/backstage-core

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 1, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@backstage/backend-defaults (source) 0.15.0 → 0.15.1 age confidence dependencies patch
@backstage/cli (source) 0.35.2 → 0.35.3 age confidence devDependencies patch
@backstage/cli (source) 0.35.2 → 0.35.3 age confidence dependencies patch
@backstage/core-compat-api (source) 0.5.6 → 0.5.7 age confidence dependencies patch
@backstage/core-components (source) 0.18.5 → 0.18.6 age confidence dependencies patch
@backstage/core-plugin-api (source) 1.12.1 → 1.12.2 age confidence dependencies patch
@backstage/frontend-defaults (source) 0.3.5 → 0.3.6 age confidence dependencies patch
@backstage/frontend-plugin-api (source) 0.13.3 → 0.13.4 age confidence dependencies patch
@backstage/frontend-test-utils (source) 0.4.4 → 0.4.5 age confidence devDependencies patch
@backstage/plugin-auth-backend-module-github-provider (source) 0.4.0 → 0.4.1 age confidence dependencies patch
@backstage/plugin-auth-node (source) 0.6.11 → 0.6.12 age confidence dependencies patch
@backstage/plugin-catalog-backend (source) 3.3.1 → 3.3.2 age confidence dependencies patch
@backstage/plugin-permission-backend (source) 0.7.7 → 0.7.8 age confidence dependencies patch
@backstage/plugin-permission-common (source) 0.9.4 → 0.9.5 age confidence dependencies patch
@backstage/plugin-permission-node (source) 0.10.8 → 0.10.9 age confidence dependencies patch
@backstage/plugin-scaffolder (source) 1.35.1 → 1.35.2 age confidence dependencies patch
@backstage/plugin-search-backend (source) 2.0.10 → 2.0.11 age confidence dependencies patch
@backstage/ui (source) 0.11.1 → 0.11.2 age confidence dependencies patch
backstage/backstage 1.47.1 → 1.47.2 age confidence patch

Release Notes

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

v0.15.1

Compare Source

Patch Changes
backstage/backstage (@​backstage/cli)

v0.35.3

Compare Source

Patch Changes
backstage/backstage (@​backstage/core-compat-api)

v0.5.7

Compare Source

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

v0.18.6

Compare Source

Patch Changes
backstage/backstage (@​backstage/core-plugin-api)

v1.12.2

Compare Source

Patch Changes
backstage/backstage (@​backstage/frontend-defaults)

v0.3.6

Compare Source

Patch Changes
  • 17e0eb3: The API_FACTORY_CONFLICT error is now treated as a warning and will not prevent the app from starting.
  • 122d39c: Completely removed support for the deprecated app.experimental.packages configuration. Replace existing usage directly with app.packages.
  • c38b74d: Dependency update for tests.
  • 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.
  • Updated dependencies
backstage/backstage (@​backstage/frontend-plugin-api)

v0.13.4

Compare Source

backstage/backstage (@​backstage/frontend-test-utils)

v0.4.5

Compare Source

Patch Changes
backstage/backstage (@​backstage/plugin-auth-backend-module-github-provider)

v0.4.1

Compare Source

@​backstage/catalog-model@​0.6.0

Minor Changes
  • ac3560b: Remove implementsApis from Component entities. Deprecation happened in #​3449.
    Use providesApis instead.
Patch Changes
  • c911061: Introduce a profile section for group entities that can optional include a
    displayName, email and picture.
  • 0e6298f: Ignore relations when comparing entities. This stops the refresh loop from rewriting entities over and over.

@​backstage/techdocs-common@​0.2.0

Minor Changes

  • dae4f39: Breaking changes

    1. Added option to use Google Cloud Storage as a choice to store the static generated files for TechDocs.
      It can be configured using techdocs.publisher.type option in app-config.yaml.
      Step-by-step guide to configure GCS is available here https://backstage.io/docs/features/techdocs/using-cloud-storage
      Set techdocs.publisher.type to 'local' if you want to continue using local filesystem to store TechDocs files.

    2. techdocs.builder is now required and can be set to 'local' or 'external'. (Set it to 'local' for now, since CI/CD build
      workflow for TechDocs will be available soon (in few weeks)).
      If builder is set to 'local' and you open a TechDocs page, techdocs-backend will try to generate the docs, publish to storage and
      show the generated docs afterwords.
      If builder is set to 'external', techdocs-backend will only fetch the docs and will NOT try to generate and publish. In this case of 'external',
      we assume that docs are being built in the CI/CD pipeline of the repository.
      TechDocs will not assume a default value for techdocs.builder. It is better to explicitly define it in the app-config.yaml.

    3. When configuring TechDocs in your backend, there is a difference in how a new publisher is created.

      --- const publisher = new LocalPublish(logger, discovery);
      +++ const publisher = Publisher.fromConfig(config, logger, discovery);

    Based on the config techdocs.publisher.type, the publisher could be either Local publisher or Google Cloud Storage publisher.

    1. techdocs.storageUrl is now a required config. Should be http://localhost:7000/api/techdocs/static/docs in most setups.

    2. Parts of @backstage/plugin-techdocs-backend have been moved to a new package @backstage/techdocs-common to generate docs. Also to publish docs
      to-and-fro between TechDocs and a storage (either local or external). However, a Backstage app does NOT need to import the techdocs-common package -
      app should only import @backstage/plugin-techdocs and @backstage/plugin-techdocs-backend.

    Patch changes

    1. See all of TechDocs config options and its documentation https://backstage.io/docs/features/techdocs/configuration

    2. Logic about serving static files and metadata retrieval have been abstracted away from the router in techdocs-backend to the instance of publisher.

    3. Removed Material UI Spinner from TechDocs header. Spinners cause unnecessary UX distraction.
      Case 1 (when docs are built and are to be served): Spinners appear for a split second before the name of site shows up. This unnecessarily distracts eyes because spinners increase the size of the Header. A dot (.) would do fine. Definitely more can be done.
      Case 2 (when docs are being generated): There is already a linear progress bar (which is recommended in Storybook).

Patch Changes

@​backstage/plugin-catalog-backend@​0.5.0

Minor Changes

  • 6b37c95: Write relations directly as part of batch add / update of entities.

    Slight change of the CommonDatabase contract:

addEntity removed

This method was unused by the core, and rendered unnecessary when `addEntities`
exists.

If you were a user of `addEntity`, please call `addEntities` instead, with an
array of one element.

DbEntityRequest has a new field relations

This is the structure that is passed to `addEntities` and `updateEntity`. It
used to be the case that you needed to call `setRelations` separately, but now
this instead happens directly when you call `addEntities` or `updateEntity`.

If you were using `addEntities` or `updateEntity` directly, please adapt your
code to add the `relations` array to each request. If you were calling
`setRelations` separately next to these methods, you no longer need to do so,
after adding the relations to the `DbEntityRequest`s.
  • ac3560b: Remove implementsApis from Component entities. Deprecation happened in #​3449.
    Use providesApis instead.
Patch Changes
  • c6eeefa: Add support for Github Enterprise in GitHubOrgReaderProcessor so you can properly ingest users of a GHE organization.
  • fb386b7: Break the refresh loop into several smaller transactions
  • 7c3ffc0: Support profile of groups including displayName, email, and picture in
    LdapOrgReaderProcessor. The source fields for them can be configured in the
    ldapOrg provider.
  • e7496dc: Break out GithubOrgReaderProcessor config into its own file for consistency with the other org processors.
  • 8dd0a90: Support profile of groups including displayName and picture in
    GithubOrgReaderProcessor. Fixes the import of description for groups.
  • 8c31c68: Batch the writing of statuses after refreshes. This reduced the runtime on sqlite from 16s to 0.2s, and on pg from 60s to 1s on my machine, for the huge LDAP set.
  • 7b98e7f: Add index to foreign key columns. Postgres (and others) do not do this on the "source" side of a foreign key relation, which was what led to the slowness on large datasets. The full LDAP dataset ingestion now takes two minutes, which is not optimal yet but still a huge improvement over before when it basically never finished :)
  • 0097057: Support profile of groups including displayName and email in
    MicrosoftGraphOrgReaderProcessor. Importing picture doesn't work yet, as
    the Microsoft Graph API does not expose them correctly.
  • Updated dependencies [c911061]
  • Updated dependencies [1d1c286]
  • Updated dependencies [0e6298f]
  • Updated dependencies [4eafdec]
  • Updated dependencies [ac3560b]

@​backstage/plugin-techdocs@​0.5.0

Minor Changes

  • dae4f39: Breaking changes

    1. Added option to use Google Cloud Storage as a choice to store the static generated files for TechDocs.
      It can be configured using techdocs.publisher.type option in app-config.yaml.
      Step-by-step guide to configure GCS is available here https://backstage.io/docs/features/techdocs/using-cloud-storage
      Set techdocs.publisher.type to 'local' if you want to continue using local filesystem to store TechDocs files.

    2. techdocs.builder is now required and can be set to 'local' or 'external'. (Set it to 'local' for now, since CI/CD build
      workflow for TechDocs will be available soon (in few weeks)).
      If builder is set to 'local' and you open a TechDocs page, techdocs-backend will try to generate the docs, publish to storage and
      show the generated docs afterwords.
      If builder is set to 'external', techdocs-backend will only fetch the docs and will NOT try to generate and publish. In this case of 'external',
      we assume that docs are being built in the CI/CD pipeline of the repository.
      TechDocs will not assume a default value for techdocs.builder. It is better to explicitly define it in the app-config.yaml.

    3. When configuring TechDocs in your backend, there is a difference in how a new publisher is created.

      --- const publisher = new LocalPublish(logger, discovery);
      +++ const publisher = Publisher.fromConfig(config, logger, discovery);

    Based on the config techdocs.publisher.type, the publisher could be either Local publisher or Google Cloud Storage publisher.

    1. techdocs.storageUrl is now a required config. Should be http://localhost:7000/api/techdocs/static/docs in most setups.

    2. Parts of @backstage/plugin-techdocs-backend have been moved to a new package @backstage/techdocs-common to generate docs. Also to publish docs
      to-and-fro between TechDocs and a storage (either local or external). However, a Backstage app does NOT need to import the techdocs-common package -
      app should only import @backstage/plugin-techdocs and @backstage/plugin-techdocs-backend.

    Patch changes

    1. See all of TechDocs config options and its documentation https://backstage.io/docs/features/techdocs/configuration

    2. Logic about serving static files and metadata retrieval have been abstracted away from the router in techdocs-backend to the instance of publisher.

    3. Removed Material UI Spinner from TechDocs header. Spinners cause unnecessary UX distraction.
      Case 1 (when docs are built and are to be served): Spinners appear for a split second before the name of site shows up. This unnecessarily distracts eyes because spinners increase the size of the Header. A dot (.) would do fine. Definitely more can be done.
      Case 2 (when docs are being generated): There is already a linear progress bar (which is recommended in Storybook).

Patch Changes

@​backstage/plugin-techdocs-backend@​0.4.0

Minor Changes

  • dae4f39: Breaking changes

    1. Added option to use Google Cloud Storage as a choice to store the static generated files for TechDocs.
      It can be configured using techdocs.publisher.type option in app-config.yaml.
      Step-by-step guide to configure GCS is available here https://backstage.io/docs/features/techdocs/using-cloud-storage
      Set techdocs.publisher.type to 'local' if you want to continue using local filesystem to store TechDocs files.

    2. techdocs.builder is now required and can be set to 'local' or 'external'. (Set it to 'local' for now, since CI/CD build
      workflow for TechDocs will be available soon (in few weeks)).
      If builder is set to 'local' and you open a TechDocs page, techdocs-backend will try to generate the docs, publish to storage and
      show the generated docs afterwords.
      If builder is set to 'external', techdocs-backend will only fetch the docs and will NOT try to generate and publish. In this case of 'external',
      we assume that docs are being built in the CI/CD pipeline of the repository.
      TechDocs will not assume a default value for techdocs.builder. It is better to explicitly define it in the app-config.yaml.

    3. When configuring TechDocs in your backend, there is a difference in how a new publisher is created.

      --- const publisher = new LocalPublish(logger, discovery);
      +++ const publisher = Publisher.fromConfig(config, logger, discovery);

    Based on the config techdocs.publisher.type, the publisher could be either Local publisher or Google Cloud Storage publisher.

    1. techdocs.storageUrl is now a required config. Should be http://localhost:7000/api/techdocs/static/docs in most setups.

    2. Parts of @backstage/plugin-techdocs-backend have been moved to a new package @backstage/techdocs-common to generate docs. Also to publish docs
      to-and-fro between TechDocs and a storage (either local or external). However, a Backstage app does NOT need to import the techdocs-common package -
      app should only import @backstage/plugin-techdocs and @backstage/plugin-techdocs-backend.

    Patch changes

    1. See all of TechDocs config options and its documentation https://backstage.io/docs/features/techdocs/configuration

    2. Logic about serving static files and metadata retrieval have been abstracted away from the router in techdocs-backend to the instance of publisher.

    3. Removed Material UI Spinner from TechDocs header. Spinners cause unnecessary UX distraction.
      Case 1 (when docs are built and are to be served): Spinners appear for a split second before the name of site shows up. This unnecessarily distracts eyes because spinners increase the size of the Header. A dot (.) would do fine. Definitely more can be done.
      Case 2 (when docs are being generated): There is already a linear progress bar (which is recommended in Storybook).

Patch Changes

@​backstage/backend-common@​0.4.1

Patch Changes

@​backstage/catalog-client@​0.3.4

Patch Changes

@​backstage/cli@​0.4.2

Patch Changes
  • c36a01b: Re-enable symlink resolution during bundling, and switch to using a resolve plugin for external linked packages.

@​backstage/core@​0.4.1

Patch Changes

@​backstage/core-api@​0.2.6

Patch Changes
  • 7dd2ef7: Use auth provider ID to create unique session storage keys for GitHub and SAML Auth.

@​backstage/create-app@​0.2.5

Patch Changes

  • 2783ec0: In the techdocs-backend plugin (packages/backend/src/plugins/techdocs.ts), create a publisher using

      const publisher = Publisher.fromConfig(config, logger, discovery);

    instead of

      const publisher = new LocalPublish(logger, discovery);

    An instance of publisher can either be a local filesystem publisher or a Google Cloud Storage publisher.

    Read more about the configs here https://backstage.io/docs/features/techdocs/configuration
    (You will also have to update techdocs.storage.type to local or googleGcs. And techdocs.builder to either local or external.)

@​backstage/integration@​0.1.4

Patch Changes
  • 1d1c286: Implement readTree on BitBucketUrlReader and getBitbucketDownloadUrl
  • 4eafdec: Introduce readTree method for GitLab URL Reader
  • 178e093: Validate that integration config contains a valid host

@​backstage/plugin-api-docs@​0.4.1

Patch Changes

@​backstage/plugin-auth-backend@​0.2.7

Patch Changes

@​backstage/plugin-catalog@​0.2.7

Patch Changes

@​backstage/plugin-catalog-graphql@​0.2.5

Patch Changes

@​backstage/plugin-catalog-import@​0.3.2

Patch Changes

@​backstage/plugin-circleci@​0.2.5

Patch Changes

@​backstage/plugin-cloudbuild@​0.2.5

Patch Changes

@​backstage/plugin-cost-insights@​0.5.2

Patch Changes

@​backstage/plugin-github-actions@​0.2.5

Patch Changes

@​backstage/plugin-jenkins@​0.3.4

Patch Changes

@​backstage/plugin-kubernetes@​0.3.3

Patch Changes

@​backstage/plugin-kubernetes-backend@​0.2.3

Patch Changes

@​backstage/plugin-lighthouse@​0.2.6

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 is behind base branch, 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 added the renovate label Feb 1, 2026
@secustor secustor enabled auto-merge (squash) February 1, 2026 18:23
@secustor secustor merged commit 864a40c into main Feb 1, 2026
4 checks passed
@secustor secustor deleted the renovate/backstage-core branch February 1, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@secustor secustor secustor approved these changes

Assignees

No one assigned

Labels

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@secustor