fix(deps): update backstage monorepo#115
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/backstage-monorepo
branch
from
563ef3c to
6fea26d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
1.7.8→1.7.90.17.2→0.17.41.9.1→1.9.20.36.2→0.36.31.20.1→1.20.20.18.10→0.18.111.12.6→1.12.70.17.1→0.17.21.2.18→1.2.190.14.1→0.14.20.5.14→0.5.150.29.0→0.29.10.5.3→0.5.40.2.19→0.2.200.4.16→0.4.170.7.1→0.7.22.0.5→2.0.63.7.1→3.8.00.1.22→0.1.230.2.20→0.2.210.6.4→0.6.50.13.13→0.13.140.12.19→0.12.200.21.4→0.21.50.5.17→0.5.180.6.5→0.6.60.7.4→0.7.50.7.12→0.7.130.2.19→0.2.200.11.0→0.11.10.5.1→0.5.20.6.13→0.6.141.37.0→1.38.00.9.9→0.9.100.1.22→0.1.230.13.3→0.13.41.7.4→1.7.52.1.2→2.1.30.3.15→0.3.160.5.55→0.5.560.4.14→0.4.151.4.4→1.4.51.11.4→1.11.5^0.0.31→^0.0.320.3.15→0.3.161.17.6→1.17.72.2.0→2.2.11.1.36→1.1.371.3.11→1.3.120.9.3→0.9.41.7.18→1.7.19^0.15.0→^0.16.0Release Notes
backstage/backstage (@backstage/app-defaults)
v1.7.9Compare Source
Patch Changes
74ed625: Provide toastApi for old frontend systemFixes 'No implementation available for apiRef{core.toast}' on old frontend system.
Updated dependencies
backstage/backstage (@backstage/backend-defaults)
v0.17.4Compare Source
Patch Changes
aaa7d65: Improved readability of the AWS S3 URL parser by splitting the single monolithic regex into two separate patterns (standard S3 and VPC PrivateLink) with named capture groups. Also made the VPC endpoint region mandatory in the regex, fixing a potential mis-parse when the region segment was absent.8419f51: Added support for AWS PrivateLink for Amazon S3.v0.17.3Compare Source
Patch Changes
4f4bcf5: Upgradedinfinispanfrom^0.12.0to^0.13.0to address known vulnerabilities.a07e6a3: UpdatedAzureBlobStorageUrlReaderto reference the correctly-namedAzureBlobStorageIntegrationtype from@backstage/integration. The previously-usedAzureBlobStorageIntergationis now an alias for the new type and remains a valid argument to the constructor.b75158b: Adapted Azure-related tests for the Azure SDK upgrade to ESM-style exports. TheAzureBlobStorageUrlReadernow accepts an optionalcreateContainerClientdependency for testability without needing to mock the@azure/storage-blobmodule.89a95ca: Fixed the task worker retry loop to respect the abort signal. Previously, when a task worker encountered an unexpected error, the retry loop would continue indefinitely even after the worker was signaled to stop. The retry loop now checks the abort signal before retrying and passes it to the retry delay, allowing the worker to shut down gracefully.def82d4: Fixed the built-in rate limiter throwing a validation error and refusing to start whenbackend.rateLimitis enabled. Requests are now keyed using the address normalization helper fromexpress-rate-limit, which is required by newer versions of that library and ensures IPv6 clients are grouped by their address block rather than by individual address.0211390: Added a newv2invoke endpoint (/.backstage/actions/v2/actions/:id/invoke) that accepts a wrapped body format{ input, secrets }with secrets validation. The existingv1invoke endpoint remains unchanged for backward compatibility. UpdatedDefaultActionsServiceto use thev2endpoint. UpdatedDefaultActionsRegistryServiceto expose secrets schema in the actions list response and validate secrets on invocation.34f21c3: Fix gitlabUrlReader issue with retrieving the repository archive treebackstage/backstage (@backstage/backend-plugin-api)
v1.9.2Compare Source
Patch Changes
02c4e8a: Removed unusedjson-schemaruntime dependency. The package was only used for TypeScript types from@types/json-schema; affected imports have been converted toimport typeto allow safe removal.0211390: Added optionalsecretsschema support toActionsRegistryActionOptionsandActionsRegistryActionContext. Actions can now declare a Zod secrets schema separate from the input schema, enabling surfaces to collect sensitive credentials independently from tool arguments. Added optionalsecretsfield toActionsServiceActionmetadata andActionsService.invoke()parameters.backstage/backstage (@backstage/cli)
v0.36.3Compare Source
Patch Changes
b521571: Improved validation of conflicting CLI module commands, including conflicts between parent and nested command paths.backstage/backstage (@backstage/core-app-api)
v1.20.2Compare Source
Patch Changes
backstage/backstage (@backstage/core-components)
v0.18.11Compare Source
Patch Changes
e0889a3: chore(deps): bumpqsfrom 6.15.1 to 6.15.2a07e6a3: Added the correctly-spelled'header'literal to theTableFiltersClassKeyunion type and deprecated the previous typoed'heder'literal. The generated CSS class with the old key is preserved for backwards compatibility; switch to'header'to avoid future removal.c161e1c: Lazy-loadreact-syntax-highlighterand@dagrejs/dagreso they are no longer pulled in eagerly through the barrel export. This reduces the upfront module cost of importing from@backstage/core-componentsby roughly 10 MB. The public API is unchanged.dbe93a7: Fix autologout not working correctly when closing all tabs8add9b9: Fixed the proxy-based sign-in page failing to read the session token when the proxy issues a token whose payload is encoded using the URL-safe base64 alphabet. Such tokens are now decoded correctly so sign-in no longer breaks.f35372d: Fixed text clipping in SidebarSubmenuItem by correcting line-height from 1 to 1.5backstage/backstage (@backstage/core-plugin-api)
v1.12.7Compare Source
Patch Changes
backstage/backstage (@backstage/frontend-plugin-api)
v0.17.2Compare Source
Patch Changes
378784e: Moved dependencies that are re-exported in the public API fromdevDependenciestodependencies. These were incorrectly demoted in #33936 because the source code only uses type imports, but the types still appear in the published API surface and need to be resolvable by consumers at build time.backstage/backstage (@backstage/integration-react)
v1.2.19Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-api-docs)
v0.14.2Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-app-backend)
v0.5.15Compare Source
Patch Changes
ca450be: Added a newapp.disablePublicEntryPointconfig option that allows you to opt out of the automatic public sign-in entry point. When set totrue, the app backend will skip serving the public entry point to unauthenticated users, even if the app was bundled with anindex-public-experimentalentry point.backstage/backstage (@backstage/plugin-auth-backend)
v0.29.1Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-backend-module-github-provider)
v0.5.4Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-backend-module-guest-provider)
v0.2.20Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-backend-module-oidc-provider)
v0.4.17Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-node)
v0.7.2Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog)
v2.0.6Compare Source
Patch Changes
7172386: Updated the new frontend system Catalog index page to use the current Backstage UI page header and content container.d8757b1: The entity list provider now fetches the entity list and the total count as two separate parallel requests when using cursor or offset pagination. The list query skips the expensive count computation (usingtotalItems: 'exclude'), so the table populates immediately. The count arrives asynchronously and updates the title. A newtotalItemsLoadingfield is exposed onEntityListContextPropsso consumers can distinguish a stale count from a fresh one.The catalog table now keeps stale rows visible during filter changes and page navigation instead of replacing the entire table body with a spinner. The full-table spinner is only shown on the very first load when no data exists yet. The entity count in the title is dimmed while the count is refreshing, and a small spinner appears next to the title while rows are loading.
82cf16f: AddedCatalogExportButton, which adds CSV and JSON export support to theCatalogIndexPage.d7c1dcf: Fixed a missing React key warning for context menu items on the entity page.a07e6a3: Added the correctly-spelledRelatedEntitiesCard.domainEntityColumnsstatic property and deprecated the previous typoedRelatedEntitiesCard.domainEntityColumsproperty. Existing references to the old property continue to work; switch todomainEntityColumnsto avoid future removal.Updated dependencies
backstage/backstage (@backstage/plugin-catalog-backend)
v3.8.0Compare Source
Minor Changes
8f20cc2:/entities/by-querynow accepts atotalItemsparameter ('include'or'exclude', default'include') that controls whether the response'stotalItemscount is computed. Pass'exclude'to skip the count entirely when the caller doesn't need it — useful for cursor-paginated user interfaces that only display the count cosmetically. The accepted values list is forward-compatible: future modes (e.g. approximate counts) can be added without breaking existing callers.The internal
QueryEntitiesInitialRequest.skipTotalItemsoption has been replaced bytotalItems: 'include' | 'exclude'. Note thatskipTotalItemswas never exposed as a REST API parameter, so this is only a TypeScript-level change affecting direct callers ofEntitiesCatalog.queryEntities.Sort field keys are now lowercased before comparing against
search.key, fixing silent mismatches for camelCase field names. TheNULLS LASTordering clause has been removed since NULL sort values are already excluded by theWHEREclause.dc7678c: Removed the immediate mode stitching strategy. All stitching now uses the deferred mode, which processes entities asynchronously via a worker queue. If your configuration includescatalog.stitchingStrategy.mode: 'immediate', it will be ignored with a deprecation warning. ThepollingIntervalandstitchTimeoutsettings continue to work as before.Patch Changes
9698738: Dropped the legacysearch_entity_id_idxindex which is now redundant with the covering unique index on(entity_id, key, value). The old index caused the query planner to choose an inefficient scan pattern for catalog list queries with multiple sort fields, leading to severely degraded performance on large catalogs.ccfa4f1: OptimizedentitiesBatchon PostgreSQL to use= ANY(array)instead ofWHERE IN ($1, $2, ...). This produces a single stable query plan regardless of batch size, instead of up to 200 different plans that pollute the query plan cache. On PostgreSQL, batching is no longer needed so all entity refs are fetched in a single query.750b310:HAS_LABELandHAS_ANNOTATIONpermission rules are now case insensitive.24775dc: Added a migration that tunes PostgreSQL automatic vacuum thresholds on thesearch,final_entities,relations, andrefresh_state_referencestables, and fixes column statistics forentity_idin thesearchtable. This prevents the query planner from falling back to sequential scans when table maintenance falls behind, keeping catalog queries fast on large installations.39c5fbb: Added extended multi-column statistics on(key, value)in thesearchtable (PostgreSQL only). This tells the query planner about the correlation between thekeyandvaluecolumns, fixing severe row count estimation errors on compound filter queries. Without this, the planner could choose to materialize and sort thousands of rows instead of using the LIMIT short-circuit index scan — causing 10-40x slower catalog list views when multiple filters are active.4829e89: Split thequeryEntitieslist and count into separate queries instead of a multi-reference CTE. When thefilteredCTE was referenced twice (once for the count, once for the data), PostgreSQL refused to inline it, forcing full materialization of the filtered set before applyingLIMIT. By running the count as a standalone query, the list CTE is only referenced once, allowing the planner to short-circuit onLIMITand return the first page in milliseconds instead of waiting for the full filtered set to materialize.The standalone count query also fixes a pre-existing bug where
totalItemswas inflated for entities with multi-valued sort fields (e.g. tags). The old CTE-based count counted search rows, so an entity with 3 tags would be counted 3 times. The new count usesEXISTSto count distinct entities, aligningtotalItemswith the number of entities actually reachable through cursor pagination.774d698: Fixed a race condition in the stitch queue and entity processing claim logic whereSELECT FOR UPDATE SKIP LOCKEDrow locks were released before the subsequent timestamp bump, allowing multiple workers to claim the same rows. Both the select and update now run inside a single transaction for MySQL and PostgreSQL.0b8b677: Improved stitch queue semantics to prevent overlapping stitches for the same entity. New stitch requests that arrive while a stitch is in progress now only update the ticket (not the timestamp), so the in-progress worker is not interrupted. When the worker completes and detects a pending re-stitch, the queue entry becomes immediately eligible for pickup instead of waiting for the timeout period.Updated dependencies
backstage/backstage (@backstage/plugin-catalog-backend-module-logs)
v0.1.23Compare Source
Patch Chang
Configuration
📅 Schedule: (UTC)
🚦 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.