Conversation
6c3dec5 to
0c0f19d
Compare
0c0f19d to
4ca41aa
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:
0.15.1→0.15.20.35.3→0.35.40.35.3→0.35.40.5.7→0.5.80.18.6→0.18.71.12.2→1.12.30.1.1→0.1.2^0.3.4→^0.4.0^0.3.4→^0.4.0^0.13.2→^0.14.00.4.5→0.5.01.2.14→1.2.150.5.10→0.5.11^0.1.26→^0.2.0^0.26.0→^0.27.0^0.4.0→^0.5.00.2.15→0.2.160.6.12→0.6.131.32.2→1.33.13.3.2→3.4.00.1.18→0.1.190.2.16→0.2.17^1.21.4→^2.0.00.21.0→0.21.10.5.13→0.5.140.6.1→0.6.20.6.48→0.6.490.7.8→0.7.90.2.15→0.2.160.9.5→0.9.60.10.9→0.10.101.35.2→1.35.41.5.3→1.6.12.0.11→2.0.120.3.11→0.3.120.5.51→0.5.521.4.0→1.4.1^0.0.27→^0.0.280.3.11→0.3.12^0.8.30→^0.9.0^0.11.0→^0.12.01.47.3→1.48.3Release Notes
backstage/backstage (@backstage/backend-defaults)
v0.15.2Compare Source
Patch Changes
7455dae: Use node prefix on native imports44f5d04: Minor internal restructure of the postgres config loading code4fc7bf0: Bump to tar v75dd683f:createRateLimitMiddlewareis now exported from@backstage/backend-defaults/httpRouter8dd518a: Supportconnection.type: azurein database client to use Microsoft Entra authentication with Azure database for PostgreSQL69d880e: Bump to latest zod to ensure it has the latest featuresbackstage/backstage (@backstage/cli)
v0.35.4Compare Source
Patch Changes
cfd8103: Updated catalog provider module template to use stable catalog extension points from@backstage/plugin-catalog-nodeinstead of alpha exports.20131c5: Added support for CSS exports in package builds. When a package declares a CSS file in itsexportsfield (e.g.,"./styles.css": "./src/styles.css"), the CLI will automatically bundle it duringbackstage-cli package build, resolving any@importstatements. The export path is rewritten fromsrc/todist/at publish time.Fixed
backstage-cli repo fixto not addtypesVersionsentries for non-script exports like CSS files.7455dae: Use node prefix on native imports6ce4a13: Removed/alphafromscaffolderActionsExtensionPointimportfdbd404: Removed theEXPERIMENTAL_MODULE_FEDERATIONenvironment variable flag, making module federation host support always available duringpackage start. The host shared dependencies are now managed through@backstage/module-federation-commonand injected as a versioned runtime script at build time.fdbd404: Updated@module-federation/enhanced,@module-federation/runtime, and@module-federation/sdkdependencies from^0.9.0to^0.21.6.4fc7bf0: Bump to tar v75e3ef57: Added support for the newpeerModulesmetadata field inpackage.json. This field allows plugin packages to declare modules that should be installed alongside them for cross-plugin integrations. The field is validated bybackstage-cli repo fix --publish.122d39c: Completely removed support for the deprecatedapp.experimental.packagesconfiguration. Replace existing usage directly withapp.packages.73351c2: Updated dependencywebpackto~5.104.0.69d880e: Bump to latest zod to ensure it has the latest featuresUpdated dependencies
backstage/backstage (@backstage/core-compat-api)
v0.5.8Compare Source
Patch Changes
c38b74d: Internal updates for blueprint moves to@backstage/plugin-app-react.ef6916e: AddedIconElementtype as a replacement for the deprecatedIconComponent. TheIconsApinow has a newicon()method that returnsIconElement, while the existinggetIcon()method is deprecated. TheIconBundleBlueprintnow accepts bothIconComponentandIconElementvalues.53b6549: Plugins in the new frontend system now have apluginIdfield rather thanidto 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 preferpluginIdwhile maintaining backward compatibility by falling back toidwhen needed.a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.69d880e: Bump to latest zod to ensure it has the latest featuresbackstage/backstage (@backstage/core-components)
v0.18.7Compare Source
Patch Changes
7455dae: Use node prefix on native importsa7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.cebfea7: Removed link styles from LinkButton to avoid styling inconsistencies related to import order.69d880e: Bump to latest zod to ensure it has the latest featuresbackstage/backstage (@backstage/core-plugin-api)
v1.12.3Compare Source
Patch Changes
53b6549: Plugins in the new frontend system now have apluginIdfield rather thanidto 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 preferpluginIdwhile maintaining backward compatibility by falling back toidwhen needed.a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.69d880e: Bump to latest zod to ensure it has the latest featuresbackstage/backstage (@backstage/e2e-test-utils)
v0.1.2Compare Source
Patch Changes
b96c20e: Added optionalchanneloption togenerateProjects()to allow customizing the Playwright browser channel for testing against different browsers variants. When not provided, the function defaults to 'chrome' to maintain backward compatibility.Example usage:
7455dae: Use node prefix on native importsbackstage/backstage (@backstage/frontend-defaults)
v0.4.0Compare Source
Minor Changes
55b2ef6: BREAKING: TheAPI_FACTORY_CONFLICTwarning is now treated as an error and will prevent the app from starting.Patch Changes
122d39c: Completely removed support for the deprecatedapp.experimental.packagesconfiguration. Replace existing usage directly withapp.packages.c38b74d: Dependency update for tests.53b6549: Plugins in the new frontend system now have apluginIdfield rather thanidto 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 preferpluginIdwhile maintaining backward compatibility by falling back toidwhen needed.a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.backstage/backstage (@backstage/frontend-plugin-api)
v0.14.1Compare Source
v0.14.0Compare Source
Minor Changes
ef6916e: AddedIconElementtype as a replacement for the deprecatedIconComponent. TheIconsApinow has a newicon()method that returnsIconElement, while the existinggetIcon()method is deprecated. TheIconBundleBlueprintnow accepts bothIconComponentandIconElementvalues.bb9b471: Plugin IDs that do not match the standard format are deprecated (letters, digits, and dashes only, starting with a letter). Plugin IDs that do no match this format will be rejected in a future release.ef6916e: AddedSubPageBlueprintfor creating sub-page tabs,PluginHeaderActionBlueprintandPluginHeaderActionsApifor plugin-scoped header actions, andPageLayoutas a swappable component. ThePageBlueprintnow supports sub-pages with tabbed navigation, page title, icon, and header actions. Plugins can now specify atitleandiconincreateFrontendPlugin.c38b74d: BREAKING: The following blueprints have been removed and are now only available from@backstage/plugin-app-react:IconBundleBlueprintNavContentBlueprintRouterBlueprintSignInPageBlueprintSwappableComponentBlueprintThemeBlueprintTranslationBlueprint10ebed4: BREAKING: Removed type support for multiple attachment points in theExtensionDefinitionAttachTotype. Extensions can no longer specify an array of attachment points in theattachToproperty.The runtime still supports multiple attachment points for backward compatibility with existing compiled code, but new code will receive type errors if attempting to use this pattern.
Extensions that previously used multiple attachment points should migrate to using a Utility API pattern instead. See the Sharing Extensions Across Multiple Locations guide for the recommended approach.
Patch Changes
7edb810: Added a newinternaloption tocreateExtensionInputthat marks the input as only allowing attachments from the same plugin.9554c36: DEPRECATED: Multiple attachment points for extensions have been deprecated. The functionality continues to work for backward compatibility, but will log a deprecation warning and be removed in a future release.Extensions using array attachment points should migrate to using Utility APIs instead. See the Sharing Extensions Across Multiple Locations guide for the recommended pattern.
53b6549: Plugins in the new frontend system now have apluginIdfield rather thanidto 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 preferpluginIdwhile maintaining backward compatibility by falling back toidwhen needed.a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.69d880e: Bump to latest zod to ensure it has the latest featuresUpdated dependencies
backstage/backstage (@backstage/frontend-test-utils)
v0.5.0Compare Source
Minor Changes
09a6aad: BREAKING: Removed theTestApiRegistryclass, useTestApiProviderdirectly instead, storing reused APIs in a variable, e.g.const apis = [...] as const.d2ac2ec: AddedMockAlertApiandMockFeatureFlagsApiimplementations to themockApisnamespace. The mock implementations include useful testing methods likeclearAlerts(),waitForAlert(),getState(),setState(), andclearState()for better test ergonomics.09a6aad: BREAKING: ThemockApisnamespace is no longer a re-export from@backstage/test-utils. It's now a standalone namespace with mock implementations of most core APIs. Mock API instances can be passed directly toTestApiProvider,renderInTestApp, andrenderTestAppwithout needing[apiRef, impl]tuples. As part of this change, the.factory()method on some mocks has been removed, since it's now redundant.This change also adds
createApiMock, a public utility for creating mock API factories, intended for plugin authors to create their own.mock()variants.Patch Changes
22864b7: Added anapisoption tocreateExtensionTester,renderInTestApp, andrenderTestAppto override APIs when testing extensions. Use themockApishelpers to create mock implementations:15ed3f9: Addedsnapshot()method toExtensionTester, which returns a tree-shaped representation of the resolved extension hierarchy. Convenient to use withtoMatchInlineSnapshot().013ec22: AddedmountedRoutesoption torenderTestAppfor binding route refs to paths, matching the existing option inrenderInTestApp:d7dd5bd: Fixed Router deprecation warning and switched to using newRouterBlueprintfrom@backstage/plugin-app-api.a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.69d880e: Bump to latest zod to ensure it has the latest featuresUpdated dependencies
backstage/backstage (@backstage/integration-react)
v1.2.15Compare Source
Patch Changes
a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.backstage/backstage (@backstage/plugin-app-backend)
v0.5.11Compare Source
Patch Changes
7455dae: Use node prefix on native importsbackstage/backstage (@backstage/plugin-app-visualizer)
v0.2.0Compare Source
Minor Changes
ef6916e: Migrated to useSubPageBlueprintfor tabbed navigation and added a copy-tree-as-JSON plugin header action usingPluginHeaderActionBlueprint. The plugin now specifies atitleandicon.Patch Changes
cb090b4: Bump react-aria-components to v1.14.0c38b74d: Internal updates for blueprint moves to@backstage/plugin-app-react.4137a43: Updated CSS token references to use renamed--bui-border-2token.4d50e1f: Improved rendering performance of the details page.a7e0d50: Updatedreact-router-dompeer dependency to^6.30.2and explicitly disabled v7 future flags to suppress deprecation warnings.backstage/backstage (@backstage/plugin-auth-backend)
v0.27.0Compare Source
Minor Changes
31de2c9: Added experimental support for Client ID Metadata Documents (CIMD).This allows Backstage to act as an OAuth 2.0 authorization server that supports the IETF Client ID Metadata Document draft. External OAuth clients can use HTTPS URLs as their
client_id, and Backstage will fetch metadata from those URLs to validate the client.Configuration example:
Clients using CIMD must host a JSON metadata document at their
client_idURL containing at minimum:{ "client_id": "https://example.com/.well-known/oauth-client/my-app", "client_name": "My Application", "redirect_uris": ["http://localhost:8080/callback"], "token_endpoint_auth_method": "none" }d0786b9: Added experimental support for refresh tokens via theauth.experimentalRefreshToken.enabledconfiguration option. When enabled, clients can request theoffline_accessscope to receive refresh tokens that can be used to obtain new access tokens without re-authentication.Patch Changes
7dc3dfe: Removed theauth.experimentalDynamicClientRegistration.tokenExpirationconfig option. DCR tokens now use the default 1 hour expiration.If you need longer-lived access, use refresh tokens via the
offline_accessscope instead. DCR clients should already have theoffline_accessscope available. Enable refresh tokens by setting:7455dae: Use node prefix on native importsUpdated dependencies
backstage/backstage (@backstage/plugin-auth-backend-module-github-provider)
v0.5.0Compare Source
Minor Changes
ff07934: Added theuserIdMatchingUserEntityAnnotationsign-in resolver that matches users by their GitHub user ID.Patch Changes
69d880e: Bump to latest zod to ensure it has the latest featuresbackstage/backstage (@backstage/plugin-auth-backend-module-guest-provider)
v0.2.16Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-auth-node)
v0.6.13Compare Source
Patch Changes
7455dae: Use node prefix on native imports69d880e: Bump to latest zod to ensure it has the latest featuresbackstage/backstage (@backstage/plugin-catalog)
v1.33.1Compare 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.
This PR was generated by Mend Renovate. View the repository job log.