Skip to content

fix(deps): update backstage monorepo #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 10, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 13, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@backstage/backend-defaults (source) ^0.5.0 -> ^0.7.0 age adoption passing confidence
@backstage/backend-plugin-api (source) 1.0.1 -> 1.1.1 age adoption passing confidence
@backstage/backend-test-utils (source) 1.0.2 -> 1.2.1 age adoption passing confidence
@backstage/catalog-client (source) 1.7.1 -> 1.9.1 age adoption passing confidence
@backstage/catalog-model (source) 1.7.0 -> 1.7.3 age adoption passing confidence
@backstage/cli (source) ^0.27.1 -> ^0.29.0 age adoption passing confidence
@backstage/config (source) 1.2.0 -> 1.3.2 age adoption passing confidence
@backstage/core-app-api (source) 1.15.1 -> 1.15.4 age adoption passing confidence
@backstage/core-components (source) ^0.15.0 -> ^0.16.0 age adoption passing confidence
@backstage/core-plugin-api (source) 1.10.0 -> 1.10.3 age adoption passing confidence
@backstage/dev-utils (source) 1.1.2 -> 1.1.6 age adoption passing confidence
@backstage/errors (source) 1.2.4 -> 1.2.7 age adoption passing confidence
@backstage/integration (source) 1.15.1 -> 1.16.1 age adoption passing confidence
@backstage/plugin-auth-backend (source) ^0.23.0 -> ^0.24.0 age adoption passing confidence
@backstage/plugin-auth-backend-module-guest-provider (source) 0.2.1 -> 0.2.4 age adoption passing confidence
@backstage/plugin-catalog (source) 1.24.0 -> 1.26.1 age adoption passing confidence
@backstage/plugin-catalog-node (source) 1.13.1 -> 1.15.1 age adoption passing confidence
@backstage/plugin-catalog-react (source) 1.14.0 -> 1.15.1 age adoption passing confidence
@backstage/test-utils (source) 1.7.0 -> 1.7.4 age adoption passing confidence
@backstage/theme (source) ^0.5.7 -> ^0.6.0 age adoption passing confidence
@backstage/types (source) 1.1.1 -> 1.2.1 age adoption passing confidence

Release Notes

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

v0.7.0

Compare Source

Minor Changes
  • ec547b8: Ensure that an error handler middleware exists at the end of each plugin httpRouter handler chain. This makes it so that exceptions thrown by plugin routes are caught and encoded in the standard error format.

    If you were using the standard MiddlewareFactory just to put an error middleware in you router, you can now remove that at your earliest convenience since it's redundant. If you have custom error handlers in your plugin router, those will continue to function as previously. If you were relying on thrown errors propagating all the way down to the root HTTP router, you will find that they no longer do that, and may want to hoist your error handling up to the plugin level instead.

Patch Changes

v0.6.2

Compare Source

v0.6.1

Compare Source

v0.6.0

Compare Source

Minor Changes
  • fd5d337: Added a new backend.health.headers configuration that can be used to set additional headers to include in health check responses.

    BREAKING CONSUMERS: As part of this change the createHealthRouter function exported from @backstage/backend-defaults/rootHttpRouter now requires the root config service to be passed through the config option.

  • 3f34ea9: Throttles Bitbucket Server API calls

  • de6f280: BREAKING Upgraded @​keyv/redis and keyv packages to resolve a bug related to incorrect resolution of cache keys.

    This is a breaking change for clients using the redis store for cache with useRedisSets option set to false since cache keys will be calculated differently (without the sets:namespace: prefix). For clients with default configuration (or useRedisSets set to false) the cache keys will stay the same, but since @​keyv/redis library no longer supports redis sets they won't be utilised anymore.

    If you were using useRedisSets option in configuration make sure to remove it from app-config.yaml:

    backend:
      cache:
        store: redis
        connection: redis://user:[email protected]:6379
    -   useRedisSets: false
  • 29180ec: BREAKING PRODUCERS: The LifecycleMiddlewareOptions.startupRequestPauseTimeout has been removed. Use the backend.lifecycle.startupRequestPauseTimeout setting in your app-config.yaml file to customize how the createLifecycleMiddleware function should behave. Also the root config service is required as an option when calling the createLifecycleMiddleware function:

    - createLifecycleMiddleware({ lifecycle, startupRequestPauseTimeout })
    + createLifecycleMiddleware({ config,  lifecycle })
  • 277092a: Implemented AzureBlobStorageUrlReader to read from the url of committed location from the entity provider

  • 18a2c00: All middleware used by the default coreServices.http is now exported for use by custom implementations.

Patch Changes

v0.5.3

Compare Source

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

v1.1.1

Compare Source

Patch Changes

v1.1.0

Compare Source

Minor Changes
  • 12eac85: EXPERIMENTAL: Adds a new instanceMetadataService to hold information about a specific backend instance.
Patch Changes

v1.0.2

Compare Source

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

v1.2.1

Compare Source

Patch Changes

v1.2.0

Compare Source

Minor Changes
  • de6f280: BREAKING Upgraded @​keyv/redis and keyv packages to resolve a bug related to incorrect resolution of cache keys.

    This is a breaking change for clients using the redis store for cache with useRedisSets option set to false since cache keys will be calculated differently (without the sets:namespace: prefix). For clients with default configuration (or useRedisSets set to false) the cache keys will stay the same, but since @​keyv/redis library no longer supports redis sets they won't be utilised anymore.

    If you were using useRedisSets option in configuration make sure to remove it from app-config.yaml:

    backend:
      cache:
        store: redis
        connection: redis://user:[email protected]:6379
    -   useRedisSets: false
Patch Changes

v1.1.0

Compare Source

Minor Changes
  • 5064827: Made it possible to construct mockServices.database with a given knex instance
Patch Changes
backstage/backstage (@​backstage/catalog-client)

v1.9.1

Compare Source

Patch Changes

v1.9.0

Compare Source

Minor Changes
  • 384e494: Internal updates to generated code.
Patch Changes

v1.8.0

Compare Source

Minor Changes
  • 656d1ef: Internal update to use the updated generated code from backstage-cli package schema openapi generate --client-package ....
  • 31c4fe0: The client now automatically splits up very large getEntitiesByRefs calls into several smaller requests behind the scenes when needed. This ensures that each individual request does not exceed common Express.js request body limits or overload the server.
Patch Changes
backstage/backstage (@​backstage/catalog-model)

v1.7.3

Compare Source

Patch Changes

v1.7.2

Compare Source

Patch Changes

v1.7.1

Compare Source

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

v0.29.6

Compare Source

v0.29.5

Compare Source

Patch Changes

v0.29.4

Compare Source

Patch Changes

v0.29.3

Compare Source

Patch Changes

v0.29.2

Compare Source

The @backstage/core package has been split into the following three packages, all published as part of this release.

Name Description
@backstage/core-app-api Core app API used by Backstage apps
@backstage/core-plugin-api Core API used by Backstage plugins and apps
@backstage/core-components Core components used by Backstage plugins and apps

The main purpose of the split is to decouple the plugin API versioning from the app. It is now possible to bring in multiple plugins that depend on different versions of the core API, without any significant overhead.

The existing @backstage/core package still works together with these new packages, meaning that there is no rush to migrate, and we do not recommend that projects are migrated just yet. In general migration will be done by simply replacing usages of @backstage/core with either @backstage/core-plugin-api, @backstage/core-app-api, or @backstage/core-components, depending on what's being imported, but more information will follow!

v0.29.1

Compare Source

Published a new @backstage/backend-test-utils package, which is a package for backend test utilities.

v0.29.0

[Compare Source](https://redirect.github.com/backstage/backsta


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 from 5871f77 to 0315e2f Compare November 21, 2024 20:55
@renovate renovate bot changed the title chore(deps): update backstage monorepo fix(deps): update backstage monorepo Nov 21, 2024
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch from 0315e2f to 73f9f77 Compare December 3, 2024 05:57
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch from 73f9f77 to 43291b5 Compare December 14, 2024 02:52
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from 4dbe660 to ec67d7d Compare December 25, 2024 05:27
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch from ec67d7d to aab8c03 Compare January 15, 2025 03:28
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch 2 times, most recently from ce3834c to 0f17433 Compare January 30, 2025 03:37
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch from 0f17433 to 6142082 Compare February 1, 2025 00:13
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch 3 times, most recently from a9a8d6f to 0452220 Compare February 10, 2025 21:10
@renovate renovate bot force-pushed the renovate/backstage-monorepo branch from 0452220 to f03b7a3 Compare February 10, 2025 21:25
@amber-beasley-liatrio amber-beasley-liatrio merged commit d30ec26 into main Feb 10, 2025
7 checks passed
@amber-beasley-liatrio amber-beasley-liatrio deleted the renovate/backstage-monorepo branch February 10, 2025 21:30
github-actions bot pushed a commit that referenced this pull request Feb 11, 2025
## [1.6.3](v1.6.2...v1.6.3) (2025-02-11)

### Bug Fixes

* **deps:** replace dependency @material-ui/core with @mui/material ^5.0.0 ([#25](#25)) ([2b1d627](2b1d627))
* **deps:** replace dependency @material-ui/core with @mui/material ^5.0.0 ([#53](#53)) ([b27c633](b27c633))
* **deps:** replace dependency @material-ui/icons with @mui/icons-material ^5.0.0 ([#26](#26)) ([bc5b13c](bc5b13c))
* **deps:** replace dependency @material-ui/icons with @mui/icons-material ^5.0.0 ([#54](#54)) ([8560d0d](8560d0d))
* **deps:** update backstage monorepo ([#32](#32)) ([d30ec26](d30ec26))
* **deps:** update dependency @backstage/theme to v0.6.3 ([#51](#51)) ([5fd79ea](5fd79ea))
* **deps:** update dependency express to v4.21.2 ([#52](#52)) ([bef69aa](bef69aa))
* **deps:** update dependency node-fetch to v2.7.0 ([#37](#37)) ([44dec2d](44dec2d))
* **deps:** update dependency styled-components to v6.1.15 ([#55](#55)) ([4bfe638](4bfe638))
* remove unneeded MSW dep ([#31](#31)) ([87791de](87791de))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant