fix(deps): update backstage monorepo #145
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/backstage-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.5.17->1.7.21.9.1->1.12.11.7.3->1.7.6^0.30.0->^0.34.0^0.30.0->^0.34.01.3.2->1.3.61.15.5->1.19.21.15.5->1.19.2^0.16.0->^0.18.01.10.4->1.12.01.1.7->1.1.171.2.4->1.2.12^0.12.0->^0.13.0^0.4.0->^0.5.0^0.24.0->^0.25.01.27.0->1.32.0^1.2.0->^3.0.0^0.7.0->^0.11.01.1.3->1.1.7^0.4.0->^0.5.0^0.12.0->^0.13.01.15.2->1.21.30.6.36->0.6.46^0.8.0->^0.9.0^0.8.0->^0.10.00.4.31->0.4.38^0.5.0->^0.6.01.28.0->1.34.3^1.3.0->^3.0.01.4.23->1.5.0^1.0.0->^2.0.00.5.41->0.5.501.3.8->1.3.171.8.6->1.10.01.12.3->1.16.0^1.1.2->^2.0.01.1.21->1.1.301.2.14->1.3.50.8.19->0.8.291.7.5->1.7.13^0.6.0->^0.7.0Release Notes
backstage/backstage (@backstage/app-defaults)
v1.7.2Compare Source
Patch Changes
v1.7.1Compare Source
Patch Changes
v1.7.0Compare Source
Minor Changes
9956704: Add and configure the OpenShift authentication provider to the default APIs.Patch Changes
v1.6.5Compare Source
Patch Changes
v1.6.4Compare Source
Patch Changes
v1.6.3Compare Source
Patch Changes
v1.6.2Compare Source
Patch Changes
v1.6.1Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.6.0Compare Source
Minor Changes
12f8e01: BREAKING: The defaultDiscoveryApiimplementation has been switched to useFrontendHostDiscovery, which adds support for thediscovery.endpointsconfiguration.This is marked as a breaking change because it will cause any existing
discovery.endpointsconfiguration to be picked up and used, which may break existing setups.For example, consider the following configuration:
This will now cause requests from the frontend towards the
catalogplugin to be routed tohttps://catalog.internal.acme.org/api/catalog, but this might not be reachable from the frontend. To fix this, you should update thediscovery.endpointsconfiguration to only override the internal URL of the plugin:Patch Changes
backstage/backstage (@backstage/catalog-client)
v1.12.1Compare Source
Patch Changes
v1.12.0Compare Source
Minor Changes
0e9ec44: Introduced newstreamEntitiesasync generator method for the catalog.Catalog API and Catalog Service now includes a
streamEntitiesmethod that allows for streaming entities from the catalog.This method is designed to handle large datasets efficiently by processing entities in a stream rather than loading them
all into memory at once. This is useful when you need to fetch a large number of entities but do not want to use pagination
or fetch all entities at once.
Example usage:
Patch Changes
0efcc97: Updated generated schemasv1.11.0Compare Source
Minor Changes
6b608e7: Added the analyze-location endpoint to the CatalogClientv1.10.2Compare Source
Patch Changes
6fb4143: allow arrays in the InMemoryCatalogClient to filter entitiesv1.10.1Compare Source
Patch Changes
22fad0d: FixedCatalogClienterror responses forrefreshEntityandaddLocation.v1.10.0Compare Source
Minor Changes
1a003ff: AddgetLocationsmethod toCatalogApiandCatalogClient. This method calls theGET /locationsendpoint from the catalog backend.Patch Changes
backstage/backstage (@backstage/catalog-model)
v1.7.6Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.7.5Compare Source
Patch Changes
3507fcd: Just some more circular dep cleanupv1.7.4Compare Source
Patch Changes
ed4e625: Added support for icons containing colonsbackstage/backstage (@backstage/cli)
v0.34.5Compare Source
Patch Changes
fc7cbfc: The templates executed with theyarn newcommand now supports templating filenames.da19cb5: Fix inconsistent behavior in thenewcommand for the@internalscope: it now consistently defaults to thebackstage-plugin-infix whether the--scopeoption is not set or it's set tointernal.fc7cbfc: Added a template for theyarn newcommand to create an catalog entity provider. To add this template to an explicit list in the rootpackage.json, use@backstage/cli/templates/catalog-provider-module.b2bef92: Convert all enums to erasable-syntax compliant patterns279279c: Fixes an issue where using thebackstage-cli new --scopecommand with a scope that already includes the@symbol (e.g.,@backstage-community) would result in a double@@​prefix in the generated package name, causing invalidpackage.jsonfiles.05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v0.34.4Compare Source
Patch Changes
f2cf564: Removed the script transform cache from the default Jest configuration. The script cache provided a moderate performance boost, but it is incompatible with Jest 30.33faad2: Allow using custom manifest location in the yarn plugin and version bump.The Backstage yarn plugin and version bump allows two new environment variables to configure custom manifest location:
BACKSTAGE_VERSIONS_BASE_URL: The base URL for fetching the Backstage versionmanifest. Defaults to
https://versions.backstage.io/v1/releases/VERSION/manifest.json.Useful for running the plugin in environment without direct access to the internet,
for example by using a mirror of the versions API or a proxy.
Note that the environment variable is just the host name, and the path is appended by
the plugin. If you are using the yarn plugin, bump version command will also try
to fetch the new version of the yarn plugin from the same base URL (defaults to
https://versions.backstage.io/v1/releases/RELEASE/yarn-plugin)BACKSTAGE_MANIFEST_FILE: Path to a local manifest file. If set, the pluginwill not attempt to fetch the manifest from the network. Useful for running
the plugin in environment without internet access and without mirror of the
versions API.
6ebc1ea: Fixed module federation config by only settingimport: falseon shared libraries for remote.ab96bb7: Added a new--entrypointoption to thepackage startcommand, which allows you to specify a custom entry directory/file for development applications. This is particularly useful when maintaining separate dev apps for different versions of your plugin (e.g., stable and alpha).Example usage:
Consider the following plugin dev folder structure:
yarn package startcommand uses thedev/folder as the entry point and executesdev/index.tsxfile;yarn package start --entrypoint dev/alphawill instead usedev/alpha/as the entry point and executedev/alpha/index.tsfile.024645e: Remove unused @octokit modules from cli packaged14ef24: Added automatic detection and support for the Backstage Yarn plugin when generating new packages withyarn new. When the plugin is installed, new packages will automatically usebackstage:^ranges for@backstage/*dependencies.Updated dependencies
v0.34.3Compare Source
v0.34.2Compare Source
Patch Changes
e6f45dc: Updated the WebPack configuration to usecontenthash. This fixes an issue were builds would sometimes generate output files with the same name but different content across builds, leading to breakages when loading the frontend app.fffd434: Disallow import fallback of critical shared dependencies in module federation.080f252: Fixed thenew-frontend-plugintemplate that was incorrectly passingidinstead ofpluginIdtocreateFrontendPluginand unnecessarily importingReact.e0db9b8: Modify thebackstage.jsonalso for custom patterns if it extends the default pattern.Examples:
@backstage/*(default pattern)@{backstage,backstage-community}/*@{extra1,backstage,extra2}/*275bda8: Fixed an issue that could cause conflicts of detected modules in workspaces with multiple apps.e1adce4: Updated the backend plugin template to use a new pattern for theTodoListServicethat reduces boilerplate.Updated dependencies
v0.34.1Compare Source
Patch Changes
080f252: Fixed thenew-frontend-plugintemplate that was incorrectly passingidinstead ofpluginIdtocreateFrontendPluginand unnecessarily importingReact.275bda8: Fixed an issue that could cause conflicts of detected modules in workspaces with multiple apps.v0.34.0Compare Source
Minor Changes
38b4243: Added plugin and module templates for the new frontend system. These templates are not included by default, but can be included by adding@backstage/cli/templates/new-frontend-pluginand@backstage/cli/templates/new-frontend-plugin-moduleas custom templates.923ceb2: BREAKING: The new app build based on Rspack is now the default, and theEXPERIMENTAL_RSPACKflag has been removed. To revert to the old behavior, set theLEGACY_WEBPACK_BUILDenvironment flag and install the following optional dependencies:If you do encounter a blocking issue that forces you to use the old WebPack build, please open an issue explaining the problem. The WebPack build will be removed in a future release.
eda80c7: BREAKING: Removed support for.icon.svgimports, which have been deprecated since the 1.19 release.Patch Changes
2b8082a: Internal refactor of error handling8b1bf6e: Deprecated new frontend system config settingapp.experimental.packagesto justapp.packages. The old config will continue working for the time being, but may be removed in a future release.ead626f: The Node.js transform in@backstage/cli/config/nodeTransformHooks.mjsnow supports the built-in type stripping in Node.js, which is enabled by default from v22.18.0.a6af768: Allow js files to be processed by the nodeTransform loaderv0.33.1Compare Source
Patch Changes
50f0ce6: Fixes a module not found error when runningbackstage-cli info.v0.33.0Compare Source
Minor Changes
eef0e83: Internal update to promote the modular CLI entrypoint to stable.Patch Changes
d07fe35: Added user feedback when opening config docs in browser. The command now clearly indicates what it's doing and provides fallback instructions if the browser fails to open.ce70439: TheBACKSTAGE_CLI_EXPERIMENTAL_BUILD_CACHEflag has been removed. Existing users are encouraged to switch toEXPERIMENTAL_RSPACKinstead.1d8f00b: Switched to using theModuleFederationPluginfrom@module-federation/enhanced/rspackfor Rspack, rather than the built-in one.2b9633f: The experimentalFORCE_REACT_DEVELOPMENTflag has been removed.d8c4a54: Only use the caching Jest module loader for frontend packages in order to avoid breaking real ESM module imports.d6d63c7: Updating the scaffolder action boilerplate to use newzodschemae36e855: Addedbackstage.pluginIdfield inpackage.jsonto all default plugin package templates for thenewcommand.1bab255: Internal refactor to combine alphabuildandstartmodules.713e957: fix: merge eslint reports when using json format8a0164c: Fix an issue where some commands were not usable because of missing dist filesv0.32.1Compare Source
Patch Changes
674def9: fix: enablelazyCompilationandrefreshOptionsfor rspackd649df0: Internal code cleanupc2cae47: Add missing modules to the Backstage CLI alpha entrypoint.3f45861: Add a warning for React 17 deprecation that triggers when frontend packages and plugins start.9aaec54: Internal refactor of opaque type handling.9285385: Addedinfoobject to the context of the alpha CLI.6cc9507: Updated dependency@octokit/requestto^8.0.0.5cd3c54: Updated dependencyreact-refreshto^0.17.0.72d019d: Removed various typos19a4e7c: Internal refactor to move things closer to homev0.32.0Compare Source
Minor Changes
a47fd39: Removes default React imports from template files, aligning with the requirements for the upcoming React 19 migration. Introduces a new ESLint rule to disallowimport React from 'react'andimport * as React from 'react'.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
65b584c: Internal update to move thenewandcreate-github-appto their own module.c7254ae: Internal update to move theclean,pre/postpackandfixcommands into their own separate module.Patch Changes
4ea76f7: Bump @module-federation/enhanced ^0.9.0 to fix GHSA-593f-38f6-jp5m87a5cb4: Fixed an issue causing therepo lintcommand to fail when the--max-warningsoption was used.6969f79: Avoid trailing/*when automatically adding imports for package with multiple entry points.98b7131: Update theto doplugin template to stop using the deprecated catalog alpha service reference.If you start seeing the
should create TODO item with catalog informationtest failing, you have two options to fix this:Update the test to mock the legacy alpha catalog service, or migrate the
TODOplugin backend to use the new catalog service reference.We recommend the second option, see this pull request for an example of how to do the migration.
d5c4fed: make certificate strings optional for Dev environmentsd83f3f4: Resolved a problem where thestartcommand did not correctly handle multiple--requireflags, ensuring all specified modules are now properly loaded.d2091c6: Added a newrepo startcommand to replace the existing pattern of usingyarn devscripts. Therepo startcommand runs the app and/or backend package in the repo by default, but will also fall back to running other individual frontend or backend packages or even plugin dev entry points if the can be uniquely selected.The goal of this change is to reduce the number of different necessary scripts and align on
yarn startbeing the only command needed for local development, similar to howrepo testhandles testing in the repo. It also opens up for more powerful options, like the--plugin <pluginId>flag that runs the dev entry point of the selected plugin.The new script is installed as follows, replacing the existing
yarn startscript:In order to help users migrate in existing projects, it is recommended to add the following scripts to the root
package.json:For more information, run
yarn start --helponce the new command is installed.918c883: Included a reference to the JSX transform guide in the warning about using the default React import.Updated dependencies
v0.31.1Compare Source
v0.31.0Compare Source
Minor Changes
5b70679: BREAKING: ESLint warnings no longer trigger system exit codes like errors do.Set the max number of warnings to
-1during linting to enable the gradual adoption of new ESLint rules. To restore the previous behavior, include the--max-warnings 0flag in thebackstage-cli <repo|package> lintcommand.Patch Changes
0586d4c: Internal change to move themigrateandversion:*commands into a new migrate module.e0b226b: build(deps): bumpesbuildfrom 0.24.2 to 0.25.04d45498: Fixed the package prepack command so that it no longer produces unnecessaryindexentries in thetypesVersionsmap, which could cause/indexto be added when automatically adding imports.485b3ba: Internal update to movetestcommands to a separate module.a76c482: Internal change to migratelintto the new module system.8df78bf: Internal update to move build commands to a CLI module.d0fc357: Internal update to moveinfocommands to a separate module.f8bd342: Fix a bug in the translation of the deprecated--scopeoption for thenewcommand that could cause plugins to havebackstage-backstage-pluginin their name.backstage/backstage (@backstage/config)
v1.3.6Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.3.5Compare Source
Patch Changes
b45b094: Allow colon to be used as config key.v1.3.4Compare Source
Patch Changes
b45b094: Allow colon to be used as config key.v1.3.3Compare Source
Patch Changes
ff23618: Loosen the requirements for a key to be considered valid config.3507fcd: Just some more circular dep cleanupbackstage/backstage (@backstage/core-app-api)
v1.19.2Compare Source
Patch Changes
b2bef92: Convert all enums to erasable-syntax compliant patterns05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.19.1Compare Source
Patch Changes
v1.19.0Compare Source
Minor Changes
3fca906: AddOpenShiftAuthhelper to create default OAuth flow for OpenShift.Patch Changes
5ae6d9d: feat: support no en languagesv1.18.0Compare Source
Minor Changes
5ddc0fe: if session exists and refresh fails, then create a new session if not instant popupPatch Changes
v1.17.1Compare Source
Patch Changes
v1.17.0Compare Source
Minor Changes
1e0230e: Support customAuthConnectorforOAuth2.A user can pass their own
AuthConnectorimplementation inOAuth2constructor.In which case the session manager will use that instead of the
DefaultAuthConnectorto interact with theauthentication provider.
A custom
AuthConnectormay call the authentication provider from the front-end, store and retrieve tokensin the session storage, for example, and otherwise send custom requests to the authentication provider and
handle its responses.
Note, that if the custom
AuthConnectortransforms scopes returned from the authentication provider,the transformation must be the same as
OAuth2CreateOptions#scopeTransformpassed toOAuth2constructor.See creating
DefaultAuthConnectorinOAuth2#create(...)for an example.Patch Changes
73f6cc3: UpdatedI18nextTranslationApito support interpolation of JSX elements.cc119b2: Fixed an issue causingOAuthRequestDialogto re-render on mount.v1.16.1Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.16.0Compare Source
Minor Changes
9262001: The default auth injection middleware for theFetchApiwill now also take configuration underdiscovery.endpointsinto consideration when deciding whether to include credentials or not.12f8e01: Thediscovery.endpointsconfiguration no longer requires bothinternalandexternaltarget when using the object form, instead falling back to the default.Patch Changes
backstage/backstage (@backstage/core-components)
v0.18.3Compare Source
Patch Changes
1c7e1ce: - Revertviewboxback to old values.fullScreenprop toEntityCatalogGraphCard96ad674: Line numbers in LogViewer will not be selectable in UI anymoreb2bef92: Convert all enums to erasable-syntax compliant patterns05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v0.18.2Compare Source
Patch Changes
d493126: Swap base token for semantic token in ItemCardHeader to ensure readability in light mode.431130c: AddedrenderEdgeprop to<DependencyGraph />component in@backstage/core-componentsto allow custom rendering of graph edges.6981ae6: Fixed DependencyGraphsvgsize not adapting to the container size95935fb: Fixed dependency graph automatically scrolling foreverv0.18.1Compare Source
Added a new badges plugin, split into
@backstage/plugin-badgesand@backstage/plugin-badges-backend.The badges plugin offers a set of badges that can be used outside of your backstage deployment, showing information related to data in the catalog, such as entity owner and lifecycle data.
v0.18.0Compare Source
Minor Changes
b9a87f4: Add optionaldistanceproperty toDependencyEdgeto reflect the distance to a root.Patch Changes
1ad3d94: Dependency graph can now be opened in full screen modee409bec: Fixes for rendering initials in the avatar component.ae7d426: update about card links style for pretty display with other languagev0.17.5Compare Source
Patch Changes
1de1186: Added missing space for alert display component77467bb: Updated dependencylinkifyjsto4.3.2.5563605: AddedFavoriteToggleProps.v0.17.4Compare Source
Patch Changes
f6ffea6: Add optional message field for auth providers. This is intended to be a user friendly message that displays in the OAuth request dialog. A default message will be displayed if one is not provided.aa3b054: AddedsignInandsignOutanalytic events to the@backstage/core-componentsof sign in and sign out.v0.17.3Compare Source
Patch Changes
6232160: table actions header support i18nv0.17.2Compare Source
Patch Changes
e0d1025:LogViewernow supports atextWrapprop that wraps log lines to the next line for overflowing content instead of using horizontal scrollbb84534: Fix the hidden sidebar's sub-menu when the sidebar is scrollable72d019d: Removed various typosv0.17.1Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
5d7bad4: Fixed the messaging in theAlertDisplaywhere it was claiming that there were older messages available rather than newer.Updated dependencies
v0.17.0Compare Source
Minor Changes
25300cb:SimpleStepperback button now works withactiveStepproperty set higher than 09545af2: Declared CancelIcon explicitly on Chip component inside Select.tsx to disable onMouseDown event by default that creates the flaw of re-opening select component when user tries to remove a selected filter.Patch Changes
fffe3c0: AddedclassNamesprop to thePagecomponentdf3b9f0: Fixed a bug in the SidebarSubmenuItem within the core-components package that caused the dropdown button to be misaligned in the sidebar and the button text to appear in uppercase due to the default behavior. Also added an example dropdown menu to the app for reference.48aab13: Add i18n support for scaffolder-react plugin0a0ced6: Avoid Layout Shift forDismissableBannerwhen using astorageApiwith latency (e.g.user-settings-backend)Properly handle the
unknownstate of thestorageApi. There's a trade-off: this may lead to some Layout Shift if the banner has not been dismissed, but once it has been dismissed, you won't have any.Updated dependencies
backstage/backstage (@backstage/core-plugin-api)
v1.12.0Compare Source
Minor Changes
83439b1: All route references are now forwards compatible with the new frontend system, i.e.@backstage/frontend-plugin-api. This means they no longer need to be converted withconvertLegacyRouteReforconvertLegacyRouteRefsfrom@backstage/core-compat-api.Patch Changes
b2bef92: Convert all enums to erasable-syntax compliant patterns05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.11.1Compare Source
Patch Changes
v1.11.0Compare Source
Minor Changes
5114627: MakeopenshiftAuthApiRefavailable in@backstage/core-plugin-api.Patch Changes
v1.10.9Compare Source
Patch Changes
f6ffea6: Add optional message field for auth providers. This is intended to be a user friendly message that displays in the OAuth request dialog. A default message will be displayed if one is not provided.v1.10.8Compare Source
Patch Changes
c83cd8b: Fixed some circular or otherwise unclear imports0169b23: Internal tweak to avoid circular dependenciesv1.10.7Compare Source
Patch Changes
73f6cc3: TheTranslationApinow supports interpolation of JSX elements by passing them directly as values to the translation function. If any of the provided interpolation values are JSX elements, the translation function will return a JSX element instead of a string.v1.10.6Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.10.5Compare Source
Patch Changes
327d21e: Failure to lazy load an extension will now always result in an error being thrown to be forwarded to error boundaries, rather than being rendered using theBootErrorPageapp component.backstage/backstage (@backstage/dev-utils)
v1.1.17Compare Source
Patch Changes
b29a856: Fixed styling of the dev app by adding a lazy import of@backstage/ui/css/styles.css.v1.1.16Compare Source
v1.1.15Compare Source
Patch Changes
v1.1.14Compare Source
Patch Changes
v1.1.13Compare Source
Patch Changes
v1.1.12Compare Source
Patch Changes
v1.1.11Compare Source
Patch Changes
v1.1.10Compare Source
Patch Changes
v1.1.9Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.1.8Compare Source
Patch Changes
backstage/backstage (@backstage/integration-react)
v1.2.12Compare Source
Patch Changes
v1.2.11Compare Source
Patch Changes
v1.2.10Compare Source
Patch Changes
v1.2.9Compare Source
Patch Changes
998fd15: Separated gitlabwrite_repositoryandapiscope to pass checks inRefreshingAuthSessionManagerv1.2.8Compare Source
Patch Changes
v1.2.7Compare Source
Patch Changes
v1.2.6Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
5d10f99: Added scopeprojectfor Bitbucket Cloud.Updated dependencies
v1.2.5Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-api-docs)
v0.13.1Compare Source
Patch Changes
7c281a5: Add i18n support for Raw tab title and an error messagev0.13.0Compare Source
Minor Changes
b8a381e: Remove explicit dependency onisomorphic-form-data.This explicit dependency was added to address an issue in the
dependency
swagger-ui-react. That issue has since been resolved,and
isomorphic-form-datano longer needs to be declared.Additionally, this changeset updates the
swagger-ui-reactdependency to version5.19.0or higher, which includescompatibility with the latest versions of
the OpenAPI specification.
Patch Changes
v0.12.11Compare Source
Patch Changes
v0.12.10Compare Source
Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.f2f133c: Internal update to use the new variant ofApiBlueprint.633327c: Improved styling for dark mode8b1bf6e: Updated README instructions for the new frontend systemv0.12.9Compare Source
Patch Changes
v0.12.8Compare Source
Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.v0.12.7Compare Source
Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.72d019d: Removed various typosv0.12.6Compare Source
Patch Changes
317bc3d: api-docs plugin support i18na47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v0.12.5Compare Source
Patch Changes
74871cc: Use consistent Typography in Entity HasApisCardbackstage/backstage (@backstage/plugin-app-backend)
v0.5.8Compare Source
Patch Changes
v0.5.7Compare Source
Patch Changes
v0.5.6Compare Source
Patch Changes
afd368e: Internal update to not expose the oldcreateRouter.v0.5.5Compare Source
Patch Changes
v0.5.4Compare Source
Patch Changes
v0.5.3Compare Source
Patch Changes
v0.5.2Compare Source
Patch Changes
v0.5.1Compare Source
Patch Changes
v0.5.0Compare Source
Minor Changes
32be48c: BREAKING: Removed support for the old backend system.As part of this change the plugin export from
/alphaas been removed. If you are currently importing@backstage/plugin-app-backend/alpha, please update your import to@backstage/plugin-app-backend.Patch Changes
backstage/backstage (@backstage/plugin-auth-backend)
v0.25.6Compare Source
Patch Changes
a9315d0: Change internalstatecolumn totextto support state of over 255 characters05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.51ff7d8: Allow configuring dynamic client registration token expiration with configauth.experimentalDynamicClientRegistration.tokenExpiration.Maximum expiration for the DCR token is 24 hours. Default expiration is 1 hour.
Updated dependencies
v0.25.5Compare Source
Patch Changes
v0.25.4Compare Source
Patch Changes
1d47bf3: Implementing Dynamic Client Registration with the OIDC server. You can enable this by settingauth.experimentalDynamicClientRegistration.enabledinapp-config.yaml. This is highly experimental, but feedback welcome.54ddfef: Updating plugin metadatav0.25.3Compare Source
Patch Changes
v0.25.2Compare Source
Patch Changes
e88cb70: Small internal refactor to move out theuserInfodatabase from thetokenIssuer. Also removesexpfrom being stored inUserInfoand it's now replaced withcreated_atandupdated_atin the database instead.207778c: Internal refactor of OIDC endpoints andUserInfoDatabasev0.25.1Compare Source
Patch Changes
v0.25.0Compare Source
Minor Changes
57221d9: BREAKING: Removed support for the old backend system, and removed all deprecated exports.If you were using one of the deprecated imports from this package, you will have to follow the instructions in their respective deprecation notices before upgrading. Most of the general utilities are available from
@backstage/plugin-auth-node, and the specific auth providers are available from dedicated packages such as for example@backstage/plugin-auth-backend-module-github-provider. See the auth docs for specific instructions.Patch Changes
0d606ac: Added the configuration flagauth.omitIdentityTokenOwnershipClaimthat causes issued user tokens to no longer contain theentclaim that represents the ownership references of the user.The benefit of this new flag is that issued user tokens will be much smaller in
size, but they will no longer be self-contained. This means that any consumers
of the token that require access to the ownership claims now need to call the
/api/auth/v1/userinfoendpoint instead. Within the Backstage ecosystem this isdone automatically, as clients will still receive the full set of claims during
authentication, while plugin backends will need to use the
UserInfoServicewhich already calls the user info endpoint if necessary.
When enabling this flag, it is important that any custom sign-in resolvers directly return the result of the sign-in method. For example, the following would not work:
Instead, the sign-in resolver should directly return the result:
72d019d: Removed various typosab53e6f: Added support for the newdangerousEntityRefFallbackoption forsignInWithCatalogUserinAuthResolverContext.b128ed9: Thestatickey store now issues tokens with the same structure as other key stores. Tokens now include thetypfield in the header and theuip(user identity proof) in the payload.Updated dependencies
v0.24.5Compare Source
Patch Changes
25d05f9: Slight update to the config schemav0.24.4Compare Source
Patch Changes
7956beb: Marked the remaining exports related tocreateRouterand the old backend system as deprecated.For more information about migrating to the new backend system, see the migration guide.
Support for the old backend system will be removed in the next release of this plugin.
b6702ea: DeprecatedgetDefaultOwnershipEntityRefsin favor of the new.resolveOwnershipEntityRefs(...)method in theAuthResolverContext.The following code in a custom sign-in resolver:
Can be replaced with the following:
Updated dependencies
backstage/backstage (@backstage/plugin-catalog)
v1.32.0Compare Source
Minor Changes
a521911: Add support for customizable icons inSearchResultListItemBlueprintand related componentsPatch Changes
b500bcc: Fix React warnings for elements not having stable keys.a87c0a5: Fixed responsiveness issues with catalog entity content layout using the new frontend system.aff04d3: Fixed missing margins for entity warning content area on catalog entity page in NFS.v1.31.4Compare Source
Patch Changes
v1.31.3Compare Source
Patch Changes
4316c11: Catalog table columns support i18nce1239e: Auto-focus the first menu item inEntityContextMenu, and do not render a divider if an empty array is passed toUNSTABLE_extraContextMenuItems.85c5e04: Fix incorrectdefaultTargetoncreateComponentRouteRef.v1.31.2Compare Source
Patch Changes
c0ea01b: Fix card scrolling behavioure4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.f2f133c: Internal update to use the new variant ofApiBlueprint.f4622e8: Adding a more sensible default order to the default filters77eebdc: Support multiple headers in new frontend system, and don't render a header until the entity has finished loadingb158801: Fixed bug in EntityLayout that caused wiping existing query parameters when opening the InspectEntityDialog.v1.31.1Compare Source
Patch Changes
6991dab: Turn onpaginationby default in new frontend system, and also make configurable3ab9b96: Updated card extensions for the new frontend system to use the new entity predicates, and to not show the about card on User and Group pages.v1.31.0Compare Source
Minor Changes
406acb6: Add support to customize the about card icon links viaEntityIconLinkBlueprintand provide a default catalog view catalog source, launch scaffolder template and read techdocs docs icon links extensions.BREAKING ALPHA
The
Scaffolderlaunch template andTechDocsread documentation icons have been extracted from the defaultCatalogabout card links and are now provided respectively by theScaffolderandTechDocsplugins in the new frontend system. It means that they will not be available unless you install theTechDocsandScaffolderplugins. Also If you are using translation for these icon link titles other than the default, you should now translate them using the scaffolder translation reference or the TechDocs translation reference (the translation keys are still the same,aboutCard.viewTechdocsandaboutCard.launchTemplate).ec7b35d: Introducedbackstage.io/techdocs-entity-pathannotation which allows deep linking into another entities TechDocs in conjunction withbackstage.io/techdocs-entity.Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.v1.30.0Compare Source
Minor Changes
970cb48: Show the pagination text for the offset-paginated catalog table, and remove the pagination bar from the top of theCatalogTablewhen pagination is enabled.Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.2ddbc50: A newfilterparameter has been added toEntityContextMenuItemBlueprintto make it easier to configure which entities a menu item should appear for. Thefilterparameter is a function which accepts an entity and returns a boolean.bf85d37: Fix for missingrouteRefwhen usingcore-plugin-apiin a dialog contextv1.29.0Compare Source
Minor Changes
9454ef9: Added support of filtering based on system columns in catalog table61d350f: BREAKING ALPHA:CatalogFilterBlueprint, used in the new frontend system, is now exported under plugin-catalog-react instead of plugin-catalog.09afd67: AddsEntityContextMenuItemBlueprintto enable extending the entity page's context menu with user defined items.For example:
Patch Changes
3f7e4f1: Fixed the layout of summary cards in the new frontend system, ensuring that the horizontal scroll grid doesn't grow too large as well as tweaked its scrolling parameters.e655f62: UpdatedREADME.mdto useyarn startinstead ofyarn dev.a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
3f7e4f1: The about, links, and labels card now all have theinfocard type by default in the new frontend system.3f7e4f1: The overview content is now part of the overview group by default in the new frontend system.Updated dependencies
v1.28.0Compare Source
Minor Changes
247a40b: Now a custom entity page header can be passed as input to the default entity page.a3d93ca: The default layout of the entity page can now optionally be customized with 3 card types: info, peek and full.infoare rendered in a fixed area on the right;peekare rendered on top of the main content area;fulland cards with undefined type are rendered as they were before, in the main content area, below the peek cards.If you want to keep the layout as it was before, you don't need to do anything. But if you want to experiment with the card types and see how they render, here is an example setting the about card to be rendered as an
infocard:Entity page cards
If you wish to place a normal tab before a group, you must add the tab to a group and place the group in the order you wish it to appear on the entity page (groups that contains only one tab are rendered as normal tabs).
06d1226: Allow providingkindparameters to replace the defaultComponentkind forSubComponentscardPatch Changes
31731b0: Internal refactor to avoidexpiry-mapdependency.ba9649a: Update the default entity page extension component to support grouping multiple entity content items in the same tab.Disable all default groups:
backstage/backstage (@backstage/plugin-catalog-backend)
v3.2.0Compare Source
Minor Changes
2d229b2: Enable YAML merge keys in yamlPlaceholderResolver9d3ec06: Make YAML merge (<<:) support configurable in the Backstage Catalog instead of always being enabled8c26af4: Enable YAML merge keys in yamlPlaceholderResolverPatch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v3.1.2Compare Source
Patch Changes
9890488: Internal refactor to remove remnants of the old backend system6493c98: Log before provider-orphaning eviction happens2aaf01a: Fix for duplicate search results in entity-facets API calle489661: Moved catalog processor and provider disabling and priorities under own config objects.This is due to issue with some existing providers, such as GitHub, using array syntax for the provider configuration.
The new config format is not backwards compatible, so users will need to update their config files. The new format
is as follows:
77516c5: Added newcatalog:validate-entityaction to actions registry.This action can be used to validate entities against the software catalog.
This is useful for validating
catalog-info.yamlfile changes locally using theBackstage MCP server.
Updated dependencies
v3.1.1Compare Source
Patch Changes
v3.1.0Compare Source
Minor Changes
9b40a55: Add support for specifying an entityspec.typeincatalog.rulesandcatalog.locations.ruleswithin the catalog configuration.For example, this enables allowing all
Templateentities with the typewebsite:Patch Changes
37b4eaf: The 'get-catalog-entity' action now throws a ConflictError instead of generic Error if multiple entities are found, so MCP call doesn't fail with 500.2bbd24f: Order catalog processors by priority.This change enables the ordering of catalog processors by their priority,
allowing for more control over the catalog processing sequence.
The default priority is set to 20, and processors can be assigned a custom
priority to influence their execution order. Lower number indicates higher priority.
The priority can be set by implementing the
getPrioritymethod in the processor classor by adding a
catalog.processors.<processorName>.priorityconfigurationin the
app-config.yamlfile. The configuration takes precedence over the method.e934a27: Updatingcatalog:get-catalog-entityaction to bereadOnlyand non destructive0efcc97: Updated generated schemas2204f5b: Prevent deadlock in catalog deferred stitching58874c4: Add support to disable catalog providers and processors via configurationa4c82ad: Only run provider orphan cleanup if the engine is started in the first placeUpdated dependencies
v3.0.1Compare Source
Patch Changes
1752be6: Attempt to circumvent event listener memory leak in compression middleware9658703: Sort built-in relation fields for more stable entity hash in the processing engine9dd213c: Make the processing hash calculation not care about the order of the processors.This change does not affect the behavior of the catalog, but it will make the processing
hash calculation more robust against changes in the order of processors. This should lead to
more stable processing hashes, which in turn should lead to fewer unnecessary reprocessing
of entities.
After deploying this fix, you may see a period of increased processing and stitching, but
this should stabilize over time as the processing hashes become more consistent.
fa6fa60: Fixed getLocationByEntity to useoriginal_valueinstead ofvaluewhen querying search table3a7dad9: Updatedbetter-sqlite3to v12Updated dependencies
v3.0.0Compare Source
Major Changes
5127ebe: BREAKING: The defaultcatalog.stitchingStrategyhas been switched to{ mode: 'deferred' }.d675d96: BREAKING: The relations compatibility mode is no longer enabled by default, and thedisableRelationsCompatiblityflag has been removed. To re-enable relations compatibility, the newenableRelationsCompatibilityflag can be used instead.2339363: BREAKING: The experimentalcatalog.useUrlReadersSearchconfiguration flag (introduced in v1.36) has been removed.The
UrlReaderProcessornow always uses thesearchmethod ofUrlReaders. Built-inUrlReaderServiceimplementations have been updated accordingly.If you use custom
UrlReaderServiceimplementations, you need to adapt theirsearchmethod to correctly handle both specific URLs and potentialsearch patterns (see changes on built-in readers in the original PR).
Previous behavior was to call the
searchmethod only if the parsed Git URL's filename contained a wildcard and usereadUrlotherwise. EachUrlReaderServicemust implement this logic in thesearchmethod instead.This allows each
UrlReaderServiceimplementation to check whether it's a search URL (that contains a wildcard pattern) or not using logic that is specific to each provider.687bfc8: BREAKING: The defaultcatalog.orphanStrategyhas been switched to'delete'.5de7a9d: BREAKING: The defaultcatalog.orphanProviderStrategyhas been switched to'delete'.Patch Changes
v2.1.0Compare Source
Minor Changes
2e7adf0: Implement the actionget-catalog-entitywith theActionsRegistryPatch Changes
2cac8b0: You can now specify an optional value when applying theHAS_LABELpermission rule, similar to theHAS_ANNOTATIONpermission rule.c83cd8b: Fixed some circular or otherwise unclear imports4654a78: Updaterefresh_state_references.idto be a big intv2.0.0Compare Source
Major Changes
90ab044: BREAKING: Removed all deprecated exports, and removed support for the old backend system.It also removes the
CodeOwnersProcessorfrom the default set of processors, because it is expensive to run and has vague semantics. You need to update your backend to add it to thecatalogProcessingExtensionPointif you wish to continue using it.The following removed exports are available from
@backstage/plugin-catalog-node:locationSpecToMetadataNamelocationSpecToLocationEntityprocessingResultEntitiesSearchFilterEntityFilterDeferredEntityEntityRelationSpecCatalogProcessorCatalogProcessorParserCatalogProcessorCacheCatalogProcessorEmitCatalogProcessorLocationResultCatalogProcessorEntityResultCatalogProcessorRelationResultCatalogProcessorErrorResultCatalogProcessorRefreshKeysResultCatalogProcessorResultEntityProviderEntityProviderConnectionEntityProviderMutationAnalyzeOptionsLocationAnalyzerScmLocationAnalyzerPlaceholderResolverPlaceholderResolverParamsPlaceholderResolverReadPlaceholderResolverResolveUrlparseEntityYamlThe following removed exports are available from
@backstage/plugin-catalog-common:LocationSpecAnalyzeLocationRequestAnalyzeLocationResponseAnalyzeLocationExistingEntityAnalyzeLocationGenerateEntityAnalyzeLocationEntityFieldThe following removed exports are instead implemented in the new backend system by
@backstage/plugin-search-backend-module-catalog:defaultCatalogCollatorEntityTransformerCatalogCollatorEntityTransformerDefaultCatalogCollatorThe following exports are removed without a direct replacement:
DefaultCatalogCollatorFactoryDefaultCatalogCollatorFactoryOptionsLocationEntityProcessorLocationEntityProcessorOptionsCatalogBuilderCatalogEnvironmentCatalogPermissionRuleInputCatalogProcessingEnginecreateRandomProcessingIntervalProcessingIntervalFunctionMinor Changes
6c9b88e: BREAKING ALPHA: You can no longer import the catalog plugin from the/alphaexport; please use the regular root default export instead.d88b922: Adds the ability to disable the default entity processors using a new boolean app config itemcatalog.disableDefaultProcessors.Patch Changes
0e710fc: This patch addresses an issue identified in Backstage when configured with a MySQL database. If an entity of type location(e..all.yaml) has more than 70 referenced entities, clicking "Refresh" does not update the referenced entities as expected. This occurs because the TEXT type in MySQL has a limit of 65,535 bytes, which is insufficient to store all the referenced entities, causing the refresh operation to fail.
8e0f15f: "Added a note clarifying thatentity-fetchaudit events are not visible by default in the logs and are only displayed when the log severity level is adjusted."v1.32.1Compare Source
Patch Changes
7cc4995: Fix for duplicate results inqueryEntitieswhen providing anorderFieldparameterv1.32.0Compare Source
Minor Changes
ca9c51b: Added opt-in ability to evict entities from the catalog whose provider is no longer configured. See Catalog configuration documentationPatch Changes
4306303: Added a fix in@backstage/plugin-catalog-backendto prevent duplicate path keys in entity search if only casing is different.5243aa4: Fixed an issue occurred when authorizing permissions using custom rules passed via thePermissionsRegistryService.fbc1666: Correctly use thecatalog.useUrlReadersSearchconfig.75cadc1: Minor internal tweak torefreshByRefreshKeysbackstage/backstage (@backstage/plugin-catalog-backend-module-github)
v0.11.2Compare Source
Patch Changes
999d1c1: Added configurablepageSizesfor GitHub GraphQL API queries to preventRESOURCE_LIMITS_EXCEEDEDerrors with organizations with large number of repositories. Please see the GitHub Discovery documentation for new configuration options.v0.11.1Compare Source
Patch Changes
99fcf98: Removed unused dependenciesv0.11.0Compare Source
Minor Changes
03bdc68: Added support for discovery by appPatch Changes
v0.10.2Compare Source
Patch Changes
d421b16: This change introduces single user versions of the user group resolution code in the multi org provider that will not page through all membership when updating a single user.f6c64d1: Fix GitHub catalog entity provider branch matching on event processing.v0.10.1Compare Source
Patch Changes
v0.10.0Compare Source
Minor Changes
7c0dfb0: GitHub organization now matches in a case-insensitive manner when processing events.Patch Changes
v0.9.0Compare Source
Minor Changes
ff335e5: BREAKING TheGithubLocationAnalyzernow requires theAuthServiceand theCatalogServicewhen being constructed and theTokenMangerhas been removed.Patch Changes
ee9f59f: Added filter to include archived repositoriesv0.8.0Compare Source
Minor Changes
f0c22eb: BREAKING: Explicitly rejects branch names containing a slash character.The module now rejects any configuration that contains slashes in branch names. The reason for this is that the ingestion will run into downstream problems if they were let through. If you had configuration with a slash in the branch name in
filters.branch, your application may fail to start up.If you are affected by this, please move over to using branches that do not have slashes in them.
Patch Changes
16648ef: AddedvalidateLocationsExistto the config definition where it was missing.v0.7.11Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-common)
v1.1.7Compare Source
Patch Changes
v1.1.6Compare Source
Patch Changes
v1.1.5Compare Source
Patch Changes
v1.1.4Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-graph)
v0.5.3Compare Source
Patch Changes
a2d7ae7: Ensure the catalog graph entity card respects the height prop so the visualization scales down properly on wide screens.1c7e1ce: - Revertviewboxback to old values.fullScreenprop toEntityCatalogGraphCardb2bef92: Convert all enums to erasable-syntax compliant patternsv0.5.2Compare Source
Patch Changes
87b5e6e: Add missing API implementation for catalog graph plugin in NFS apps.431130c: AddedrenderEdgeprop to<DependencyGraph />component in@backstage/core-componentsto allow custom rendering of graph edges.6981ae6: Fixed DependencyGraphsvgsize not adapting to the container sizev0.5.1Compare Source
v0.5.0Compare Source
Minor Changes
ae6b606: Support custom relations by using an API to define known relations and which to show by defaultFixes "simplified" bug (#30121) which caused graphs not to be simplified
Patch Changes
v0.4.22Compare Source
Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.8b1bf6e: Updated README instructions for the new frontend systemv0.4.21Compare Source
Patch Changes
fe1a2f4: Catalog graph plugin support i18nv0.4.20Compare Source
Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.v0.4.19Compare Source
Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.72d019d: Removed various typos1307f00: Fix rendering of missing relationsv0.4.18Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v0.4.17Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-import)
v0.13.7Compare Source
Patch Changes
f987bfd: Fixed missingcatalog.entity.createpermission authorization in the default page extension.05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v0.13.6Compare Source
Patch Changes
v0.13.5Compare Source
Patch Changes
v0.13.4Compare Source
Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.f2f133c: Internal update to use the new variant ofApiBlueprint.v0.13.3Compare Source
Patch Changes
406b8b8: Fixed bug with error message since ResponseError is now thrown from CatalogClientv0.13.2Compare Source
Patch Changes
406b8b8: Fixed bug with error message since ResponseError is now thrown from CatalogClientv0.13.1Compare Source
Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.5d7c539: Catalog import plugin full support i18nv0.13.0Compare Source
Minor Changes
e2fd549: BREAKING:generateStepperanddefaultGenerateSteppernow require a translation argument to be passed through for supporting translations.Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.66a1140: Add i18n support forcatalog-importplugin.v0.12.13Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
5b9514f: Expose theUnpackNestedValuetype as it's been removed fromreact-hook-formf1d9a64: adding translation forRegister an existing componenttextUpdated dependencies
v0.12.12Compare Source
Patch Changes
5b9514f: Expose theUnpackNestedValuetype as it's been removed fromreact-hook-formf1d9a64: adding translation forRegister an existing componenttextv0.12.11Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-react)
v1.21.3Compare Source
Patch Changes
36d7582: Added missing i18n2b7924b: Apply default ordering of templates05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.904d136: Fixed catalog filter "all" not appearing as selected when set as the initially selected filter.v1.21.2Compare Source
Patch Changes
2a3704d: Correct translation key from "type" to "owner" for owner column in entity table to ensure the right translation is loaded.ace202e: Updatematerial-ui-popup-stateto latest available version.v1.21.1Compare Source
This release fixes the below issues:
getLocationByRefthat led to invalid backend calls with the Catalogv1.21.0Compare Source
Minor Changes
0e9ec44: Introduced newstreamEntitiesasync generator method for the catalog.Catalog API and Catalog Service now includes a
streamEntitiesmethod that allows for streaming entities from the catalog.This method is designed to handle large datasets efficiently by processing entities in a stream rather than loading them
all into memory at once. This is useful when you need to fetch a large number of entities but do not want to use pagination
or fetch all entities at once.
Example usage:
Patch Changes
0174799: Fix a potential race condition in EntityListProvider when selecting filters4316c11: Catalog table columns support i18n79ff318: Removed the deprecation warning when not passing an explicit type toEntityCardBlueprint. Omitting the type is now intended, allowing the layout to pick the default type instead, typicallycontent.ad0f58d: Supportdefault*for older packages as this package is in range for breaking/alphachangesv1.20.1Compare Source
This release fixes an issue where the
@backstage/plugin-search-reactpackage had an unnecessary dependency on@backstage/frontend-app-api.v1.20.0Compare Source
Minor Changes
3f4da39: Added theanalyzeLocationmethod tocatalogApiMocke4ddf22: BREAKING ALPHA: ThedefaultPath,defaultTitle, anddefaultGroupparams ofPageBlueprinthas been renamed topath,title, andgroup. TheconvertLegacyEntityContentExtensionutility has also received the same change. This change does not affect the compatibility of extensions created with older versions of this blueprint.Patch Changes
77eebdc: Supportfilterparameter on theEntityHeaderBlueprinta3a878d: Addingtypeas an override to theconvertLegacyEntityCardExtensiondefc243: hide paginationqueryparamsif pagination mode is set to nonev1.19.1Compare Source
Patch Changes
a07feb7: Fixed a but in the new alpha entity predicates where the$inoperator mistakenly case sensitive.3507fcd: Just some more circular dep cleanupv1.19.0Compare Source
Minor Changes
406acb6: Introduces a newEntityIconLinkBlueprintthat customizes theAboutcard icon links on theCatalogentity page.The blueprint currently accepts a
usePropshook asparamand this function returns the following props that will be passed to the icon link component:iconJSX.ElementlabelstringtitlestringdisabledbooleanfalsehrefstringonClick() => voidHere is an usage example:
Additionally, the
app-config.yamlfile allows you to override some of the default icon link parameters, includinglabelandtitlevalues. Here's how to set them:Finally, you can disable all links if you want to hide the About card header completely (useful, for example, when links are displayed on separate cards). The header is hidden when no icon links extensions are enabled.
Patch Changes
v1.18.0Compare Source
Minor Changes
d47aaa3: Added EntityOrderFilter to sort entities by different fields/columns. This new filter allows users to specify the order in which entities are displayed in the catalog.Example usage:
1a003ff: AddgetLocationsmethod toCatalogApiandCatalogClient. This method calls theGET /locationsendpoint from the catalog backend.Patch Changes
2ddbc50: A newfilterparameter has been added toEntityContextMenuItemBlueprintto make it easier to configure which entities a menu item should appear for. Thefilterparameter is a function which accepts an entity and returns a boolean.6d7f0d5: Fixed an issue causing entities of kind user and group to be empty when an owner was selectedv1.17.0Compare Source
Minor Changes
0f37fa8:entityRouteParamsnow also accepts entity refs, and can help with encoding the resulting parameters.61d350f: BREAKING ALPHA:CatalogFilterBlueprint, used in the new frontend system, is now exported under plugin-catalog-react instead of plugin-catalog.09afd67: AddsEntityContextMenuItemBlueprintto enable extending the entity page's context menu with user defined items.For example:
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
3f7e4f1: Added a newoverviewentity content group for the new frontend system.186d016: Addoperationto alphadefaultEntityContentGroups.221ddba: Fix offset pagination to reset when updating filters inuseEntityListUpdated dependencies
v1.16.0Compare Source
Minor Changes
7f57365: Add support for a new entity predicate syntax when definingfilters related to the blueprints exported via/alphafor the new frontend system. For more information, see the entity filters documentation.ba9649a: Add a newdefaultGroupparameter to theEntityContentBlueprint, here are usage examples:Set a default group while creating the extension:
Disassociate an entity content from a default group:
backstage/backstage (@backstage/plugin-org)
v0.6.46Compare Source
Patch Changes
6db9e7e: Improved responsiveness of GroupProfileCard componentv0.6.45Compare Source
Patch Changes
8b7351f: AddinitialRelationAggregationandshowAggregateMembersToggleoptions toEntityMembersListCardas well toEntityOwnershipCardv0.6.44Compare Source
Patch Changes
22b69f2: Fixing issue with extra slash in the routingv0.6.43Compare Source
v0.6.42Compare Source
Patch Changes
43cbb10: Added OwnershipCard, ComponentsGrid and UserProfileCard components to theoverridableComponents.8b1bf6e: Updated README instructions for the new frontend system4ee19ed: Added support for scrolling to OwnershipCard componentv0.6.41Compare Source
Patch Changes
3ab9b96: Updated card extensions for the new frontend system to use the new entity predicates, and switch the card type toinfofor the user and group profile cards.v0.6.40Compare Source
Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.4fe364f: Org plugin support i18nv0.6.39Compare Source
Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.02e8af1: Enhance user profile card configuration:maxRelationsnumerical configuration that controls over how many user groups are shown directly on the profile card:maxRelationsis set to0, the list of user groups is not displayed.maxRelationsis set to a positive number, up to that many groups are displayed.hideIcons, was added to optionally hide the visual icons associated with each group in the displayed list.Example in app-config.yaml
08ba448: display entity-ref in GroupProfileCard so groups can easily determine their Group ID18e84c9: Fixed missing spec.profile field on MyGroupsSidebarItem.tsx so the group spec.profile.displayName is shown on the sidebar"72d019d: Removed various typosv0.6.38Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v0.6.37Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-permission-common)
v0.9.3Compare Source
Patch Changes
b2bef92: Convert all enums to erasable-syntax compliant patternsv0.9.2Compare Source
Patch Changes
v0.9.1Compare Source
Patch Changes
3507fcd: Just some more circular dep cleanupv0.9.0Compare Source
Minor Changes
4da2965: Fixed an issue causing thePermissionClientto exhaust the request body size limit too quickly when making many requests.Patch Changes
37328b1: Fixed an issue causingPermissionClientto throw an error when authorizing basic permissions with thepermission.EXPERIMENTAL_enableBatchedRequestsconfig enabled.72d019d: Removed various typosbackstage/backstage (@backstage/plugin-permission-node)
v0.10.6Compare Source
Patch Changes
v0.10.5Compare Source
Patch Changes
v0.10.4Compare Source
Patch Changes
v0.10.3Compare Source
Patch Changes
v0.10.2Compare Source
Patch Changes
3507fcd: Just some more circular dep cleanupv0.10.1Compare Source
Patch Changes
v0.10.0Compare Source
Minor Changes
4da2965: Fixed an issue causing thePermissionClientto exhaust the request body size limit too quickly when making many requests.Patch Changes
v0.9.1Compare Source
Patch Changes
v0.9.0Compare Source
Minor Changes
22ace13: BREAKING TheServerPermissionClientcan no longer be instantiated with atokenManagerand must instead be instantiated with anauthservice. If you are still on the legacy backend system, usecreateLegacyAuthAdapters()from@backstage/backend-commonto create a compatibleauthservice.Patch Changes
728e3e1: Improved type inference when passing aPermissionResourceReftocreatePermissionRule.876f2e1: DeprecatedcreatePermissionIntegrationRouterand related types, which has been replaced byPermissionRegistryService. For more information, including how to migrate existing plugins, see the service docs.backstage/backstage (@backstage/plugin-permission-react)
v0.4.38Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v0.4.37Compare Source
Patch Changes
v0.4.36Compare Source
Patch Changes
v0.4.35Compare Source
Patch Changes
v0.4.34Compare Source
Patch Changes
v0.4.33Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v0.4.32Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-proxy-backend)
v0.6.8Compare Source
Patch Changes
v0.6.7Compare Source
Patch Changes
v0.6.6Compare Source
Patch Changes
v0.6.5Compare Source
Patch Changes
0810cd8: correct rewrite rule to avoid extra subpath in proxy pathv0.6.4Compare Source
Patch Changes
v0.6.3Compare Source
Patch Changes
v0.6.2Compare Source
Patch Changes
v0.6.1Compare Source
Patch Changes
9b5b744: Fixed handling of proxied SSE connections when the upstream server closes the connectionv0.6.0Compare Source
Minor Changes
2d8b0e4: BREAKING: Removed support for the old backend system.As part of this change the plugin export from
/alphaas been removed. If you are currently importing@backstage/plugin-proxy-backend/alpha, please update your import to@backstage/plugin-proxy-backend.Patch Changes
backstage/backstage (@backstage/plugin-scaffolder)
v1.34.3Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.34.2Compare Source
Patch Changes
e0ffe84: Add missingtemplatingExtensionsoption to RouterProps.contextMenu to allow global control across scaffolder pagesd9aed74: Forwardui:disabledinOwnedEntityPickerto allow disabling it075e064: Added missing form fields for the new frontend system.v1.34.1Compare Source
Patch Changes
0d415ae: Render a TechDocs link on the Scaffolder Template List page when templates include eitherbackstage.io/techdocs-reforbackstage.io/techdocs-entityannotations, using the sharedbuildTechDocsURLhelper. Also adds tests to verify both annotations and optionalbackstage.io/techdocs-entity-pathare respected.7151260: Prevent the MultiEntityPicker from removing options present in form state when new options are selectedv1.34.0Compare Source
Minor Changes
c08cbc4: Move Scaffolder API to OpenAPIb1c0696: Add resizable panels width for the editor and preview panels in the template editor and template form playground layouts. Users can now resize these panels by dragging the divider between the two areas.Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.f2f133c: Internal update to use the new variant ofApiBlueprint.b0dc9b8: differentiate between entirely and partially composite schemas in schema renderingc4b7c50: ExportFormFieldtype from/alphain-reactpackage, and internal refactor.v1.33.0Compare Source
Minor Changes
c1ce316: BREAKING/alpha: Convertedscaffolder.task.readandscaffolder.task.cancelinto Resource Permissions.BREAKING
/alpha: Added a new scaffolder ruleisTaskOwnerforscaffolder.task.readandscaffolder.task.cancelto allow for conditional permission policies such as restricting access to tasks and task events based on task creators.BREAKING
/alpha: Retrying a task now requires bothscaffolder.task.readandscaffolder.task.createpermissions, replacing the previous requirement ofscaffolder.task.readandscaffolder.task.cancel.Patch Changes
289e4a1: Filter MultiEntityPicker options based on rendered option valuev1.32.0Compare Source
Minor Changes
6c972fe: Added information about theentityRefandtaskIdto the analytics events whenever is possible.3c59ece: New Frontend System Only:The
Scaffolderplugin is now responsible for providing an entity icon link extension to launch templates from the catalog entity page.Patch Changes
d781b33: render details for composite property schemas18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.b00c160: Remove React import form notification and scaffolder plugin95a1d72: Added appropriate message when global templating function metadata is absent.v1.31.0Compare Source
Minor Changes
4235e87: add templating extensions pagePatch Changes
92c3658: Full support in EntityPicker (and derivatives) for default EntityPresentationApifb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.d7da01d: Fix EntityPicker field to render description as markdown, matching other form components in the system.36ae651: Fixing a bug where the name fortemplatingExtensionswas incorrectly set totemplateExtensions72d019d: Removed various typosa274e0a: Migrate custom fields to new schema factory function;standardize field descriptions to prefer ui:description and present consistently,
utilizing ScaffolderField component where possible.
v1.30.1Compare Source
This release fixes an issue in techdocs where the cache sync would fail because of missing service token, and
auth.externalAccessbeing mistakenly required in the config schema.v1.30.0Compare Source
Minor Changes
76681a5: BREAKING ALPHA: Extract out schema rendering components into their own Component. This means that the translation keys have changed foractionsPage.content.tableCell.*. They have moved to their own root keyrenderSchema.*instead.5890016: add api to retrieve template extensions info from scaffolder-backendPatch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
407eba1: Tweaked template editor tooltip to mention HTTPS requirement.Updated dependencies
v1.29.0Compare Source
Minor Changes
9d864ff: Allowed passingui:disabledfor disabling the input field of all the pickers.Patch Changes
3db64ba: Disable the submit button on creating6a3fa48: Fixes DryRunContext not forwarding the correct Scaffolder Secrets to the DryRun APIb3b7c9c: Updated the alphapage:scaffolderextension to acceptformFieldsinput, matching the updatedFormFieldBlueprint.backstage/backstage (@backstage/plugin-scaffolder-backend)
v3.0.1Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v3.0.0Compare Source
Major Changes
9b81a90: BREAKING - Removing the deprecated types and interfaces, there's no replacement for these types, and hopefully not currently used as they offer no value with the plugin being on the new backend system and no way to consume them.Affected types:
CreateWorkerOptions,CurrentClaimedTask,DatabaseTaskStore,DatabaseTaskStoreOptions,TaskManager,TaskStore,TaskStoreCreateTaskOptions,TaskStoreCreateTaskResult,TaskStoreEmitOptions,TaskStoreListEventsOptions,TaskStoreRecoverTaskOptions,TaskStoreShutDownTaskOptions,TaskWorkerandTemplateActionRegistry.Patch Changes
f222a2e: Fixed distributed actions not being visible in the scaffolder template actions.Depending on the plugin startup order, some of the distributed actions were not being registered correctly,
causing them to be invisible in the scaffolder template actions list.
Updated dependencies
v2.2.1Compare Source
Patch Changes
a57185f: Added support for executing actions from theActionsRegistryin thescaffolder-backendc3405db: Fixed a regression that prevented uploads greater than 100KB. Uploads up to 10MB are supported again.v2.2.0Compare Source
Minor Changes
c08cbc4: Move Scaffolder API to OpenAPI2032660: Fixed fs:readdir action example11dc90f: Implement max length for scaffolder auditor audit logging with default of 256812485c: Add step info to scaffolder action context to access the step id and name.Patch Changes
caee2eb: Fixed WinstonLogger throwing when redactions were null or undefined4ae87f5: addgetResourcesmethod topermissionIntegrationRouterfor frontend task permission checksb817c1d: Stop logging ofSPLATtwice in logsv2.1.1Compare Source
v2.1.0Compare Source
Minor Changes
c1ce316: BREAKING/alpha: Convertedscaffolder.task.readandscaffolder.task.cancelinto Resource Permissions.BREAKING
/alpha: Added a new scaffolder ruleisTaskOwnerforscaffolder.task.readandscaffolder.task.cancelto allow for conditional permission policies such as restricting access to tasks and task events based on task creators.BREAKING
/alpha: Retrying a task now requires bothscaffolder.task.readandscaffolder.task.createpermissions, replacing the previous requirement ofscaffolder.task.readandscaffolder.task.cancel.Patch Changes
424610a: Scaffolder audit Log now includes taskId and createdBydbde180: An internal refactor which adds additional types to experimental checkpointsfc70b43: Replaced deprecated uses of@backstage/backend-commonwith the equivalents in@backstage/backend-defaultsand@backstage/backend-plugin-api.v2.0.0Compare Source
Major Changes
33394db: BREAKING CHANGESRemoval of deprecated re-exports from module packages.
The following functions have been re-exported from the
scaffolder-backendplugin for quite some time, and now it's time to clean them up. They've been moved as follows:createPublishAzureActionshould be imported from@backstage/plugin-scaffolder-backend-module-azureinstead.createPublishBitbucketCloudActionshould be imported from@backstage/plugin-scaffolder-backend-module-bitbucket-cloudinstead.createPublishBitbucketServerActionandcreatePublishBitbucketServerPullRequestActioncan be imported from@backstage/plugin-scaffolder-backend-module-bitbucket-serverinstead.createPublishBitbucketActionshould be imported from@backstage/plugin-scaffolder-backend-module-bitbucketinstead.createPublishGerritActionandcreatePublishGerritReviewActioncan be imported from@backstage/plugin-scaffolder-backend-module-gerritinstead.createGithubActionsDispatchAction,createGithubDeployKeyAction,createGithubEnvironmentAction,createGithubIssuesLabelAction,CreateGithubPullRequestActionOptions,createGithubRepoCreateAction,createGithubRepoPushAction,createGithubWebhookAction, andcreatePublishGithubActioncan be imported from@backstage/plugin-scaffolder-backend-module-githubinstead.createPublishGitlabActionshould be imported from@backstage/plugin-scaffolder-backend-module-gitlabinstead.ActionContext.createTemplateAction,executeShellCommand,ExecuteShellCommandOptions,fetchContents,TaskSecrets, andTemplateActionshould be imported from@backstage/plugin-scaffolder-nodeinstead.ScaffolderEntitiesProcessorshould be imported from@backstage/plugin-catalog-backend-module-scaffolder-entity-modelinstead.a8fcf04: BREAKING ALPHA: The/alphaexport no longer exports the plugin. Please useimport('@​backstage/plugin-scaffolder-backend')instead as this has been removed.BREAKING CHANGES: The old
createRouterfunction which was used in the old backend system has been removed along with theRouterOptionstype.73b94d7: BREAKING CHANGESThe following functions have been re-exported from the
scaffolder-backendplugin for quite some time, and now it's time to clean them up. They've been moved as follows:SerializedTask,SerializedTaskEvent,TaskBroker,TaskBrokerDispatchOptions,TaskBrokerDispatchResult,TaskCompletionState,TaskContext,TaskEventType,TaskStatus,TemplateFilter, andTemplateGlobalshould be imported from@backstage/plugin-scaffolder-nodeinstead.The deprecated
copyWithoutRenderoption has been removed fromfetch:templateaction. You should rename the option tocopyWithoutTemplatinginstead.5863b04: BREAKING CHANGESThe
createBuiltinActionsmethod has been removed, as this should no longer be needed with the new backend system route, and was only useful when passing the default list of actions again in the old backend system. You should be able to rely on the default behaviour of the new backend system which is to merge the actions.The
createCatalogRegisterActionandcreateFetchCatalogEntityActionactions no longer require anAuthService, and now accepts aCatalogServiceinstead ofCatalogClient.Unless you're providing your own override action to the default, this should be a non-breaking change.
You can migrate using the following if you're getting typescript errors:
Minor Changes
73b94d7: DEPRECATIONSThe following types and implementations have been deprecated, either because they're no longer relevant, or because upcoming changes to the
scaffolder-backendafter2.0.0will influence the changes to these API surfaces.CreateWorkerOptionsDatabaseTaskStoreDatabaseTaskStoreOptionsTaskManagerTaskStoreCreateTaskOptionsTaskStoreCreateTaskResultTaskStoreEmitOptionsTaskStoreListEventsOptionsTaskStoreRecoverTaskOptionsTaskStoreShutDownTaskOptionsThere is no current path off deprecation, these types are going to be removed and rethought with a better way to define workers in the new backend system.
Patch Changes
89a941d: Migrating to latest action format023629e: Enable usage of secrets within 'each' step of software templates. For example, you can now structure youreachstep like this:e92e481: Add tests for ScaffolderUpdated dependencies
v1.33.0Compare Source
Minor Changes
587cb05: Addedworkspace:templateandworkspace:template:fileactions to complement respectivefetch:*actionsPatch Changes
eb39388: Fixed bug in fs:delete that prevented wildcard patterns from matching paths starting with "."36ae651: Fixing a bug where the name fortemplatingExtensionswas incorrectly set totemplateExtensions72d019d: Removed various typosec42f8e: Generating new tokens on each Scaffolder Task Retryv1.32.1Compare Source
This release fixes an issue where the scaffolder did not forward the token from the user to the task properly, and also fixes another issue where the scaffolder tasks page would not list correctly on PostgreSQL.
v1.32.0Compare Source
Minor Changes
75e4db4: add template-extensions scaffolder service endpointPatch Changes
8685cab: Addedtemplateandsteplabels for scaffolder histogram metrics:scaffolder_task_durationandscaffolder_step_duration497d47a: Document the internal built-in filters, and ensure that the types are validated when usingcreateTemplateFilterandcreateTemplateGlobalFunctionfrom thezodschema.v1.31.0Compare Source
Minor Changes
36677bb: Support newcreateTemplateActiontype, and convertcatalog:fetchaction to new way of defining actions.2b1e50d: use CreatedTemplate[Filter|Global*] as canonical template extensions in scaffolder pluginPatch Changes
e0b226b: build(deps): bumpesbuildfrom 0.24.2 to 0.25.009cf038: Got rid of most@backstage/backend-commonusages4f8b5b6: Allow signing git commits using configured private PGP key in scaffolder59dcf37: Fixed bug in fs:delete causing no files to be deleted on windows machinesbackstage/backstage (@backstage/plugin-search)
v1.5.0Compare Source
Minor Changes
a521911: Add support for customizable icons inSearchResultListItemBlueprintand related componentsPatch Changes
v1.4.31Compare Source
Patch Changes
67a3e1a: Implemented AbortController request cancellation for overlapping search requests. This change ensures that when users type quickly, previous search requests are properly canceled before new ones start.v1.4.30Compare Source
Patch Changes
v1.4.29Compare Source
Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.f2f133c: Internal update to use the new variant ofApiBlueprint.v1.4.28Compare Source
Patch Changes
v1.4.27Compare Source
Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.v1.4.26Compare Source
Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.fa48594: search plugin support i18nv1.4.25Compare Source
Patch Changes
e655f62: UpdatedREADME.mdto useyarn startinstead ofyarn dev.a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.4.24Compare Source
Patch Changes
49684fe: Expand the default kind filter to include all kinds from the System Model.backstage/backstage (@backstage/plugin-search-backend)
v2.0.8Compare Source
Patch Changes
b2bef92: Convert all enums to erasable-syntax compliant patterns05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v2.0.7Compare Source
Patch Changes
v2.0.6Compare Source
Patch Changes
0efcc97: Updated generated schemasv2.0.5Compare Source
Patch Changes
v2.0.4Compare Source
Patch Changes
69fb975: Error messages should not contain backend SQL query strings in the API response, this change will ensure that messages are logged and empty response is returned to the userv2.0.3Compare Source
Patch Changes
c83cd8b: Fixed some circular or otherwise unclear importsv2.0.2Compare Source
Patch Changes
v2.0.1Compare Source
Patch Changes
v2.0.0Compare Source
Major Changes
d5c4a9d: BREAKING Removed support for the legacy backend system and references to@backstage/backend-common, please migrate to the new backend system.Patch Changes
backstage/backstage (@backstage/plugin-search-backend-module-pg)
v0.5.50Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v0.5.49Compare Source
Patch Changes
a919ca3: Truncate long docs to fit PG index size limit8d15a51: Added the < character to the query filter regexpv0.5.48Compare Source
Patch Changes
v0.5.47Compare Source
Patch Changes
v0.5.46Compare Source
Patch Changes
v0.5.45Compare Source
Patch Changes
v0.5.44Compare Source
Patch Changes
v0.5.43Compare Source
Patch Changes
v0.5.42Compare Source
Patch Changes
8155b04: Enable normalization in postgres query to change the behavior of the search.backstage/backstage (@backstage/plugin-search-backend-node)
v1.3.17Compare Source
Patch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.3.16Compare Source
Patch Changes
v1.3.15Compare Source
Patch Changes
v1.3.14Compare Source
Patch Changes
v1.3.13Compare Source
Patch Changes
v1.3.12Compare Source
Patch Changes
v1.3.11Compare Source
Patch Changes
v1.3.10Compare Source
Patch Changes
v1.3.9Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-search-react)
v1.10.0Compare Source
Minor Changes
a521911: Add support for customizable icons inSearchResultListItemBlueprintand related componentsPatch Changes
05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v1.9.5Compare Source
Patch Changes
67a3e1a: Implemented AbortController request cancellation for overlapping search requests. This change ensures that when users type quickly, previous search requests are properly canceled before new ones start.v1.9.4Compare Source
Patch Changes
v1.9.3Compare Source
Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.v1.9.2Compare Source
Patch Changes
v1.9.1Compare Source
Patch Changes
869fa46: SearchBar clear button support i18nv1.9.0Compare Source
Minor Changes
611c941: Allow search filters to provide labels and values separately, and not only valuesPatch Changes
2c76614: Fix memoization offilterValueinSearchFilter.Autocompleteto prevent unintended resetsfa48594: search plugin support i18nv1.8.8Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.8.7Compare Source
Patch Changes
c37e480: Capture the number of search results in the search analytics event that correspond to the term entered.backstage/backstage (@backstage/plugin-techdocs)
v1.16.0Compare Source
Minor Changes
a521911: Add support for customizable icons inSearchResultListItemBlueprintand related componentsPatch Changes
71c22f3: Removed/moved unused dependenciesa4d4a70: Fixed an issue where the entire TechDocs page would re-render when navigating between pages within the same entity's documentation.v1.15.2Compare Source
Patch Changes
a4d4a70: Fixed an issue where the entire TechDocs page would re-render when navigating between pages within the same entity's documentation.v1.15.1Compare Source
Patch Changes
v1.15.0Compare Source
Minor Changes
a0b604c: Adding redirect handling for TechDocs URLs that reference entities that now reference an external entity for TechDocs. Including tests and documentation.Patch Changes
313cec7: Updated dependencydompurifyto^3.2.4.8d18d23: TechDocs page titles have been improved, especially for deeply nested pages.1dfee19: Reverts a change in CSS layout that shifted the content of the Techdocs too far to the left.4ce5831: Support Techdocs redirect with dompurify 3.2.6+v1.14.1Compare Source
This release fixes an issue where the
@backstage/plugin-kuberneteshas a cyclical dependency in the built packagev1.14.0Compare Source
Minor Changes
cb0541f: AddsadditionalAllowedURIProtocolsto sanitizer configPatch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.f2f133c: Internal update to use the new variant ofApiBlueprint.f231c2b: Fixes CSS to adjust based on whether or not the global Backstage sidebar is on the page.v1.13.2Compare Source
Patch Changes
1debf7f: Fixed an issue causing TechDocs to not properly handle initial redirect.v1.13.1Compare Source
This release bumps the minimum required version of
vm2to 3.9.17v1.13.0Compare Source
Minor Changes
3c59ece: New Frontend System Only:The
TechDocsplugin is now responsible for providing an entity icon link extension to read documentation from the catalog entity page.ec7b35d: Introducedbackstage.io/techdocs-entity-pathannotation which allows deep linking into another entities TechDocs in conjunction withbackstage.io/techdocs-entity.Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.9dde3ba: Improved Keyboard accessibility in techdocs.v1.12.6Compare Source
Patch Changes
fb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.7d445da: Update keyboard focus on when clicking hash links. This fixes the issue where the "skip to content" link rendered by Material MkDocs isn't focused when used.72d019d: Removed various typos2ffd273: Add hover and focus styling to the "copy to clipboard" button within codeblocks in techdocs. Also added an aria-label to the button for accessibility.v1.12.5Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.12.4Compare Source
Patch Changes
fffe3c0: Fixed double scrollbar issue that would appear on the Entity TechDocs view page that would stop the page from full scrolling to the top when navigating to a new page065e6b9: Excludes SVG styling from sanitizationb5a8208: AddedTechDocsAddonsBlueprintextension to allow adding of techdocs addons.ed1cb3e: Adds the page name of techdocs to the document's title.fe4abb8: Updates logic to check for SVG sources when inlining them.backstage/backstage (@backstage/plugin-techdocs-backend)
v2.1.2Compare Source
Patch Changes
71c22f3: Removed/moved unused dependenciesv2.1.1Compare Source
Patch Changes
v2.1.0Compare Source
Minor Changes
063cdc5: Techdocs: support HumanDuration for cache TTL and timeout configurationa0b604c: Adding new entity that specifies an external entity in the techdocs-entity annotation and updates to documentation regarding TechDocs redirects.Patch Changes
v2.0.5Compare Source
Patch Changes
484e500: Updated CachedEntityLoader to use BackstageCredentials instead of raw tokens for cache key generation. It now uses principal-based identification (user entity ref for users, subject for services) instead of token-based keys, providing more consistent caching behavior.v2.0.4Compare Source
Patch Changes
v2.0.3Compare Source
Patch Changes
v2.0.2Compare Source
Patch Changes
72d019d: Removed various typosv2.0.1Compare Source
Patch Changes
v2.0.0Compare Source
Major Changes
d5c4a9d: BREAKING Removed support for the legacy backend, please migrate to the new backend system. Also removed deprecatedDefaultTechDocsCollatorFactory. Use the@backstage/plugin-search-backend-module-techdocsfor this instead. Finally, deprecatedDocsBuildStrategyandTechDocsDocumentwere removed, use the versions in@backstage/plugin-techdocs-nodeinstead.Patch Changes
7828186: Minor type fix8f03776: Properly clean up temporary files on build failuresbackstage/backstage (@backstage/plugin-techdocs-module-addons-contrib)
v1.1.30Compare Source
Patch Changes
6929480: ExpandableCollapse Techdocs Addon was breaking native sidebar collapse on Firefoxv1.1.29Compare Source
Patch Changes
v1.1.28Compare Source
Patch Changes
v1.1.27Compare Source
Patch Changes
v1.1.26Compare Source
Patch Changes
v1.1.25Compare Source
Patch Changes
9dde3ba: Improved Keyboard accessibility in techdocs.v1.1.24Compare Source
Patch Changes
v1.1.23Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
9c12a76: Fixed rendering issues inReportIssueaddon for unsupported repository types and improved shadow DOM event handling. The addon now properly prevents initialization when encountering unsupported repository types and correctly handles selection events within the shadow DOM.Updated dependencies
v1.1.22Compare Source
Patch Changes
b5a8208: AddedTechDocsAddonsBlueprintextension to allow adding of techdocs addons.backstage/backstage (@backstage/plugin-techdocs-react)
v1.3.5Compare Source
Patch Changes
v1.3.4Compare Source
Patch Changes
v1.3.3Compare Source
Patch Changes
a0b604c: Update to documentation regarding TechDocs redirects.v1.3.2Compare Source
Patch Changes
v1.3.1Compare Source
Patch Changes
v1.3.0Compare Source
Minor Changes
ec7b35d: Introducedbackstage.io/techdocs-entity-pathannotation which allows deep linking into another entities TechDocs in conjunction withbackstage.io/techdocs-entity.Patch Changes
v1.2.17Compare Source
Patch Changes
72d019d: Removed various typosv1.2.16Compare Source
Patch Changes
0e9f7fe: Fix catalog entity docs page not loading due to multiple addons data attachment in the New Frontend System.a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.2.15Compare Source
Patch Changes
b5a8208: AddedTechDocsAddonsBlueprintextension to allow adding of techdocs addons.backstage/backstage (@backstage/plugin-user-settings)
v0.8.29Compare Source
Patch Changes
2b6fda3: RevertstorageApiRefimplementation05f60e1: Refactored constructor parameter properties to explicit property declarations for compatibility with TypeScript'serasableSyntaxOnlysetting. This internal refactoring maintains all existing functionality while ensuring TypeScript compilation compatibility.v0.8.28Compare Source
v0.8.27Compare Source
Patch Changes
52fa068: Added user settings storage API blueprintv0.8.26Compare Source
Patch Changes
320a9ac: Add the OpenShift authenticator provider to the defaultuser-settingsproviders page.b713b54: Tool-tip text correction for the Theme selection in settings pagev0.8.25Compare Source
Patch Changes
e4ddf22: Internal update to align with new blueprint parameter naming in the new frontend system.v0.8.24Compare Source
Patch Changes
aa3b054: AddedsignInandsignOutanalytic events to the@backstage/core-componentsof sign in and sign out.v0.8.23Compare Source
Patch Changes
18c64e9: Added theinfo.packageJsonoption to the plugin instance for the new frontend system.ab6d3dd: Add some translation to user-setting pluginc83cd8b: Fixed some circular or otherwise unclear importsv0.8.22Compare Source
Patch Changes
a7bfdb6: plugin-user-settingsgs support i18nfb58f20: Internal update to use the newpluginIdoption ofcreateFrontendPlugin.5b04b14: Uppercase language name in language selectv0.8.21Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v0.8.20Compare Source
Patch Changes
backstage/backstage (@backstage/test-utils)
v1.7.13Compare Source
Patch Changes
v1.7.12Compare Source
Patch Changes
v1.7.11Compare Source
Patch Changes
v1.7.10Compare Source
Patch Changes
v1.7.9Compare Source
Patch Changes
v1.7.8Compare Source
Patch Changes
b573341: Added support for interpolating JSX elements with theMockTranslationApi.v1.7.7Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Updated dependencies
v1.7.6Compare Source
Patch Changes
37c6510: Moved@types/jesttodevDependencies.backstage/backstage (@backstage/theme)
v0.7.0Compare Source
Minor Changes
865bce8: BREAKING: Removed the built-inCssBaselinefromUnifiedThemeProvider. If your Backstage instance looks broken after this update, you likely forgot to add our new Backstage UI global CSS. To do that, please import@backstage/ui/css/styles.cssinpackages/app/src/index.tsx:This change also removes the
noCssBaselineprop, which became redundant.Patch Changes
d5cbdba: TheUnifiedThemeProvidernow coordinates theme attributes on the documentbodyin case multiple theme providers are rendered.v0.6.8Compare Source
Patch Changes
b731527: We are introducing two new data attributes on thebodyto support Backstage UI (BUI) new theming system.v0.6.7Compare Source
Patch Changes
373486e: Add a different background colour to focusedMenuItems to fix a bug in MUI 4 (which is fixed in MUI 5)b68d269: Update uncomfortably bright color in recently visited and top visited home page cardsv0.6.6Compare Source
Patch Changes
1b14572: Show arrow when MuiTableSortLabel receives focusv0.6.5Compare Source
Patch Changes
a47fd39: Removes instances of default React imports, a necessary update for the upcoming React 19 migration.https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Renovate Bot.
e08caeae7eto22ca21e44b22ca21e44bto0ad432ba1c0ad432ba1ctob27af21919b27af21919to9184db3c169184db3c16to6a866e99a66a866e99a6tob4cc567b11b4cc567b11toc81dd87afcc81dd87afcto87d5c5964387d5c59643toec96213cb7View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.