fix(deps): update backstage monorepo #32
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.5.0
->^0.7.0
1.0.1
->1.1.1
1.0.2
->1.2.1
1.7.1
->1.9.1
1.7.0
->1.7.3
^0.27.1
->^0.29.0
1.2.0
->1.3.2
1.15.1
->1.15.4
^0.15.0
->^0.16.0
1.10.0
->1.10.3
1.1.2
->1.1.6
1.2.4
->1.2.7
1.15.1
->1.16.1
^0.23.0
->^0.24.0
0.2.1
->0.2.4
1.24.0
->1.26.1
1.13.1
->1.15.1
1.14.0
->1.15.1
1.7.0
->1.7.4
^0.5.7
->^0.6.0
1.1.1
->1.2.1
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 pluginhttpRouter
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 anerror
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
575613f
: Go back to usingnode-fetch
for gitlabd2b16db
: TheGerritUrlReader
can now read content from a commit and not only from the top of a branch. TheGitiles URL must contain the full commit
SHA
hash like:https://gerrit.com/gitiles/repo/+/2846e8dc327ae2f60249983b1c3b96f42f205bae/catalog-info.yaml
.8ecf8cb
: Exclude@backstage/backend-common
from schema collection if@backstage/backend-defaults
is present8379bf4
: Remove usages ofPluginDatabaseManager
andPluginEndpointDiscovery
and replace with their equivalent service typesv0.6.2
Compare Source
v0.6.1
Compare Source
v0.6.0
Compare Source
Minor Changes
fd5d337
: Added a newbackend.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 theconfig
option.3f34ea9
: Throttles Bitbucket Server API callsde6f280
: 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 withuseRedisSets
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 fromapp-config.yaml
:29180ec
: BREAKING PRODUCERS: TheLifecycleMiddlewareOptions.startupRequestPauseTimeout
has been removed. Use thebackend.lifecycle.startupRequestPauseTimeout
setting in yourapp-config.yaml
file to customize how thecreateLifecycleMiddleware
function should behave. Also the root config service is required as an option when calling thecreateLifecycleMiddleware
function:277092a
: ImplementedAzureBlobStorageUrlReader
to read from the url of committed location from the entity provider18a2c00
: All middleware used by the defaultcoreServices.http
is now exported for use by custom implementations.Patch Changes
dfc8b41
: Updated dependency@opentelemetry/api
to^1.9.0
.5b1e68c
: Immediately close all connections when shutting down in local development.8863b38
: ExportPluginTokenHandler
andpluginTokenHandlerDecoratorServiceRef
to allow for custom decoration of the plugin token handler without having to re-implement the entire handler.29180ec
: Fix server response time by moving the lifecycle startup hooks back to the plugin lifecycle service.57e0b11
: The user and plugin token verification in the defaultAuthService
implementation will no longer forward verification errors to the caller, and instead log them as warnings.97c6837
: ExportDefaultHttpAuthService
to allow for custom token extraction logic.e5255f1
: Log request and response metadata so it can be used for filtering log messages.The format of the request date was also changed from
clf
toutc
.57e0b11
: The defaultauthServiceFactory
now correctly depends on the plugin scopedLogger
services rather than the root scoped one.fe87fbf
: Add task metrics as two gauges that track the last start and end timestamps as epoch seconds.1ac6b72
: Supportconnection.type: cloudsql
in database client for usage with@google-cloud/cloud-sql-connector
andiam
auth0e9c9fa
: Implements theDefaultRootLifecycleService.addBeforeShutdownHook
method, and updatesDefaultRootHttpRouterService
andDefaultRootHealthService
to listen to that event to stop accepting traffic and close service connections.d0cbd82
: Remove use of thestoppable
library on theDefaultRootHttpRouterService
as Node's native http server close method already drains requests.5c9cc05
: Use native fetch instead of node-fetchcf627c6
: Fixed an issue in the WinstonLogger where Errors thrown and given to logger.error with field values that could not be cast to a string would throw a TypeErrorv0.5.3
Compare Source
Patch Changes
bf306cb
: Removed dependency@backstage/backend-common
.e30bb46
: Disabling database migrations now correctly uses thebackend.default.skipMigrations
config value.d52d7f9
: Support ISO and ms string forms of durations in config toof6eaec2
: Link to proper package inrootLoggerServiceFactory
doc string.ecf6b39
: Usenode-fetch
instead of native fetch, as per https://backstage.io/docs/architecture-decisions/adrs-adr0134e58bc7
: Upgrade to uuid v11 internallybackstage/backstage (@backstage/backend-plugin-api)
v1.1.1
Compare Source
Patch Changes
v1.1.0
Compare Source
Minor Changes
12eac85
: EXPERIMENTAL: Adds a newinstanceMetadataService
to hold information about a specific backend instance.Patch Changes
eef3ef1
: Removed unusedexpress
dependencies.0e9c9fa
: TheRootLifecycleService
now has a newaddBeforeShutdownHook
method, and hooks added through this method will run immediately when a termination event is received.The backend will not proceed with the shutdown and run the
Shutdown
hooks until allBeforeShutdown
hooks have completed.Updated dependencies
v1.0.2
Compare Source
Patch Changes
d52d7f9
: Support ISO and ms string forms of durations in config toobackstage/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 withuseRedisSets
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 fromapp-config.yaml
:Patch Changes
0e9c9fa
: Mock the newRootLifecycleService.addBeforeShutdownHook
method.v1.1.0
Compare Source
Minor Changes
5064827
: Made it possible to constructmockServices.database
with a given knex instancePatch Changes
7aae8e3
: ThemockServices.discovery.factory()
factory now uses the mocked discovery service as its implementation, avoid the need for configuration.eb82994
: Removed unusedmsw
dependency.4e58bc7
: Upgrade to uuid v11 internallybackstage/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
d7e7836
: Fixed a bug in thequeryEntities
method where errors were not being handled properly.v1.8.0
Compare Source
Minor Changes
656d1ef
: Internal update to use the updated generated code frombackstage-cli package schema openapi generate --client-package ...
.31c4fe0
: The client now automatically splits up very largegetEntitiesByRefs
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
873f89a
: Fix for certain filter fields in thecatalogApiMock
being case sensitive.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
e937ce0
: Fixed incompatible@typescript-eslint
versions with current[email protected]
8557e09
: Removed theEXPERIMENTAL_VITE
flag for using Vite as a dev server. If you were using this feature, we recommend switching to Rspack via theEXPERIMENTAL_RSPACK
flag.v0.29.4
Compare Source
Patch Changes
2b6c1ea
: If the Backstage yarn plugin is installed, it will now be automatically updated as part ofversions:bump
.7dcff85
: Remove special-casing for@types
packages when generating dependency entriesduring templating
3c3a7e6
: Revertcss-loader@v7
bump0aff006
: Bumped the version range forhtml-webpack-plugin
to fix thehtmlPluginExports.getCompilationHooks is not a function
error when using experimental Rspack.583f3d4
: Added@backstage/cli/config/prettier
as a replacement for@spotify/prettier-config
, but with the same configuration.62a9062
: Updated dependency@module-federation/enhanced
to^0.8.0
.5f04976
: Updaterollup
to avoid issues with build output when runningbackstage-cli package build
.5f04976
: Fixed a bug that caused missing code in published packages.a49030a
: Add support for--output-file
option from ESLint topackage lint
andrepo lint
commands.96331fa
: Enhance the behavior of the experimental support for module federation in the backstage CLI,by using the
package.json
exports (when present) to complete the list of exposed modules.This allows, for example, using exported
alpha
definitions through module federation.5c9cc05
: Use native fetch instead of node-fetchdcd99d2
: added experimental RSPack support for build command in the repo scopev0.29.3
Compare Source
Patch Changes
62a9062
: Updated dependency@module-federation/enhanced
to^0.8.0
.v0.29.2
Compare Source
The
@backstage/core
package has been split into the following three packages, all published as part of this release.@backstage/core-app-api
@backstage/core-plugin-api
@backstage/core-components
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.
This PR was generated by Mend Renovate. View the repository job log.