fix(deps): update backstage monorepo #145
Loading…
x
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.6.3
1.9.1
->1.10.1
1.7.3
->1.7.4
^0.30.0
->^0.33.0
^0.30.0
->^0.33.0
1.15.5
->1.17.1
1.15.5
->1.17.1
^0.16.0
->^0.17.0
1.10.4
->1.10.8
1.1.7
->1.1.11
1.2.4
->1.2.8
0.12.4
->0.12.8
^0.4.0
->^0.5.0
^0.24.0
->^0.25.0
1.27.0
->1.31.0
^1.2.0
->^2.0.0
^0.7.0
->^0.10.0
1.1.3
->1.1.4
0.4.16
->0.4.20
^0.12.0
->^0.13.0
1.15.2
->1.19.0
0.6.36
->0.6.40
^0.8.0
->^0.9.0
^0.8.0
->^0.10.0
0.4.31
->0.4.35
^0.5.0
->^0.6.0
1.28.0
->1.32.0
^1.3.0
->^2.0.0
1.4.23
->1.4.27
^1.0.0
->^2.0.0
0.5.41
->0.5.45
1.3.8
->1.3.12
1.8.6
->1.9.1
1.12.3
->1.13.1
^1.1.2
->^2.0.0
1.1.21
->1.1.25
1.2.14
->1.3.0
0.8.19
->0.8.23
1.7.5
->1.7.9
0.6.4
->0.6.6
Release Notes
backstage/backstage (@backstage/app-defaults)
v1.6.3
Compare Source
Patch Changes
v1.6.2
Compare Source
Patch Changes
v1.6.1
Compare 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.0
Compare Source
Minor Changes
12f8e01
: BREAKING: The defaultDiscoveryApi
implementation has been switched to useFrontendHostDiscovery
, which adds support for thediscovery.endpoints
configuration.This is marked as a breaking change because it will cause any existing
discovery.endpoints
configuration 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
catalog
plugin 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.endpoints
configuration to only override the internal URL of the plugin:Patch Changes
backstage/backstage (@backstage/catalog-client)
v1.10.1
Compare Source
Patch Changes
22fad0d
: FixedCatalogClient
error responses forrefreshEntity
andaddLocation
.v1.10.0
Compare Source
Minor Changes
1a003ff
: AddgetLocations
method toCatalogApi
andCatalogClient
. This method calls theGET /locations
endpoint from the catalog backend.Patch Changes
backstage/backstage (@backstage/catalog-model)
v1.7.4
Compare Source
Patch Changes
ed4e625
: Added support for icons containing colonsbackstage/backstage (@backstage/cli)
v0.33.0
Compare 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_CACHE
flag has been removed. Existing users are encouraged to switch toEXPERIMENTAL_RSPACK
instead.1d8f00b
: Switched to using theModuleFederationPlugin
from@module-federation/enhanced/rspack
for Rspack, rather than the built-in one.2b9633f
: The experimentalFORCE_REACT_DEVELOPMENT
flag 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 newzod
schemae36e855
: Addedbackstage.pluginId
field inpackage.json
to all default plugin package templates for thenew
command.1bab255
: Internal refactor to combine alphabuild
andstart
modules.713e957
: fix: merge eslint reports when using json format8a0164c
: Fix an issue where some commands were not usable because of missing dist filesv0.32.1
Compare Source
Patch Changes
674def9
: fix: enablelazyCompilation
andrefreshOptions
for 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
: Addedinfo
object to the context of the alpha CLI.6cc9507
: Updated dependency@octokit/request
to^8.0.0
.5cd3c54
: Updated dependencyreact-refresh
to^0.17.0
.72d019d
: Removed various typos19a4e7c
: Internal refactor to move things closer to homev0.32.0
Compare 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 thenew
andcreate-github-app
to their own module.c7254ae
: Internal update to move theclean
,pre/postpack
andfix
commands 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 lint
command to fail when the--max-warnings
option was used.6969f79
: Avoid trailing/*
when automatically adding imports for package with multiple entry points.98b7131
: Update theto do
plugin template to stop using the deprecated catalog alpha service reference.If you start seeing the
should create TODO item with catalog information
test failing, you have two options to fix this:Update the test to mock the legacy alpha catalog service, or migrate the
TODO
plugin 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 thestart
command did not correctly handle multiple--require
flags, ensuring all specified modules are now properly loaded.d2091c6
: Added a newrepo start
command to replace the existing pattern of usingyarn dev
scripts. Therepo start
command 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 start
being the only command needed for local development, similar to howrepo test
handles 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 start
script: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 --help
once 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.1
Compare Source
v0.31.0
Compare Source
Minor Changes
5b70679
: BREAKING: ESLint warnings no longer trigger system exit codes like errors do.Set the max number of warnings to
-1
during linting to enable the gradual adoption of new ESLint rules. To restore the previous behavior, include the--max-warnings 0
flag in thebackstage-cli <repo|package> lint
command.Patch Changes
0586d4c
: Internal change to move themigrate
andversion:*
commands into a new migrate module.e0b226b
: build(deps): bumpesbuild
from 0.24.2 to 0.25.04d45498
: Fixed the package prepack command so that it no longer produces unnecessaryindex
entries in thetypesVersions
map, which could cause/index
to be added when automatically adding imports.485b3ba
: Internal update to movetest
commands to a separate module.a76c482
: Internal change to migratelint
to the new module system.8df78bf
: Internal update to move build commands to a CLI module.d0fc357
: Internal update to moveinfo
commands to a separate module.f8bd342
: Fix a bug in the translation of the deprecated--scope
option for thenew
command that could cause plugins to havebackstage-backstage-plugin
in their name.backstage/backstage (@backstage/core-app-api)
v1.17.1
Compare Source
Patch Changes
v1.17.0
Compare Source
Minor Changes
1e0230e
: Support customAuthConnector
forOAuth2
.A user can pass their own
AuthConnector
implementation inOAuth2
constructor.In which case the session manager will use that instead of the
DefaultAuthConnector
to interact with theauthentication provider.
A custom
AuthConnector
may 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
AuthConnector
transforms scopes returned from the authentication provider,the transformation must be the same as
OAuth2CreateOptions#scopeTransform
passed toOAuth2
constructor.See creating
DefaultAuthConnector
inOAuth2#create(...)
for an example.Patch Changes
73f6cc3
: UpdatedI18nextTranslationApi
to support interpolation of JSX elements.cc119b2
: Fixed an issue causingOAuthRequestDialog
to re-render on mount.v1.16.1
Compare 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.0
Compare Source
Minor Changes
9262001
: The default auth injection middleware for theFetchApi
will now also take configuration underdiscovery.endpoints
into consideration when deciding whether to include credentials or not.12f8e01
: Thediscovery.endpoints
configuration no longer requires bothinternal
andexternal
target when using the object form, instead falling back to the default.Patch Changes
backstage/backstage (@backstage/core-components)
v0.17.3
Compare Source
Patch Changes
6232160
: table actions header support i18nv0.17.2
Compare Source
Patch Changes
e0d1025
:LogViewer
now supports atextWrap
prop 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.1
Compare 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 theAlertDisplay
where it was claiming that there were older messages available rather than newer.Updated dependencies
v0.17.0
Compare Source
Minor Changes
25300cb
:SimpleStepper
back button now works withactiveStep
property 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
: AddedclassNames
prop to thePage
componentdf3b9f0
: 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 forDismissableBanner
when using astorageApi
with latency (e.g.user-settings-backend
)Properly handle the
unknown
state 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.10.8
Compare Source
Patch Changes
c83cd8b
: Fixed some circular or otherwise unclear imports0169b23
: Internal tweak to avoid circular dependenciesv1.10.7
Compare Source
Patch Changes
73f6cc3
: TheTranslationApi
now 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.6
Compare 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.5
Compare 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 theBootErrorPage
app component.backstage/backstage (@backstage/dev-utils)
v1.1.11
Compare Source
Patch Changes
v1.1.10
Compare Source
Patch Changes
v1.1.9
Compare 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.8
Compare Source
Patch Changes
backstage/backstage (@backstage/integration-react)
v1.2.8
Compare Source
Patch Changes
v1.2.7
Compare Source
Patch Changes
v1.2.6
Compare 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 scopeproject
for Bitbucket Cloud.Updated dependencies
v1.2.5
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-api-docs)
v0.12.8
Compare Source
Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.v0.12.7
Compare Source
Patch Changes
fb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.72d019d
: Removed various typosv0.12.6
Compare 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.5
Compare Source
Patch Changes
74871cc
: Use consistent Typography in Entity HasApisCardbackstage/backstage (@backstage/plugin-app-backend)
v0.5.3
Compare Source
Patch Changes
v0.5.2
Compare Source
Patch Changes
v0.5.1
Compare Source
Patch Changes
v0.5.0
Compare Source
Minor Changes
32be48c
: BREAKING: Removed support for the old backend system.As part of this change the plugin export from
/alpha
as 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.1
Compare Source
Patch Changes
v0.25.0
Compare 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.omitIdentityTokenOwnershipClaim
that causes issued user tokens to no longer contain theent
claim 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/userinfo
endpoint 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
UserInfoService
which 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 newdangerousEntityRefFallback
option forsignInWithCatalogUser
inAuthResolverContext
.b128ed9
: Thestatic
key store now issues tokens with the same structure as other key stores. Tokens now include thetyp
field in the header and theuip
(user identity proof) in the payload.Updated dependencies
v0.24.5
Compare Source
Patch Changes
25d05f9
: Slight update to the config schemav0.24.4
Compare Source
Patch Changes
7956beb
: Marked the remaining exports related tocreateRouter
and 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
: DeprecatedgetDefaultOwnershipEntityRefs
in 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.31.0
Compare Source
Minor Changes
406acb6
: Add support to customize the about card icon links viaEntityIconLinkBlueprint
and provide a default catalog view catalog source, launch scaffolder template and read techdocs docs icon links extensions.BREAKING ALPHA
The
Scaffolder
launch template andTechDocs
read documentation icons have been extracted from the defaultCatalog
about card links and are now provided respectively by theScaffolder
andTechDocs
plugins in the new frontend system. It means that they will not be available unless you install theTechDocs
andScaffolder
plugins. 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.viewTechdocs
andaboutCard.launchTemplate
).ec7b35d
: Introducedbackstage.io/techdocs-entity-path
annotation which allows deep linking into another entities TechDocs in conjunction withbackstage.io/techdocs-entity
.Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.v1.30.0
Compare Source
Minor Changes
970cb48
: Show the pagination text for the offset-paginated catalog table, and remove the pagination bar from the top of theCatalogTable
when pagination is enabled.Patch Changes
fb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.2ddbc50
: A newfilter
parameter has been added toEntityContextMenuItemBlueprint
to make it easier to configure which entities a menu item should appear for. Thefilter
parameter is a function which accepts an entity and returns a boolean.bf85d37
: Fix for missingrouteRef
when usingcore-plugin-api
in a dialog contextv1.29.0
Compare 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
: AddsEntityContextMenuItemBlueprint
to 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.md
to useyarn start
instead 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 theinfo
card 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.0
Compare 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.info
are rendered in a fixed area on the right;peek
are rendered on top of the main content area;full
and 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
info
card: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 providingkind
parameters to replace the defaultComponent
kind forSubComponents
cardPatch Changes
31731b0
: Internal refactor to avoidexpiry-map
dependency.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)
v2.1.0
Compare Source
Minor Changes
2e7adf0
: Implement the actionget-catalog-entity
with theActionsRegistry
Patch Changes
2cac8b0
: You can now specify an optional value when applying theHAS_LABEL
permission rule, similar to theHAS_ANNOTATION
permission rule.c83cd8b
: Fixed some circular or otherwise unclear imports4654a78
: Updaterefresh_state_references.id
to be a big intv2.0.0
Compare Source
Major Changes
90ab044
: BREAKING: Removed all deprecated exports, and removed support for the old backend system.It also removes the
CodeOwnersProcessor
from 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 thecatalogProcessingExtensionPoint
if you wish to continue using it.The following removed exports are available from
@backstage/plugin-catalog-node
:locationSpecToMetadataName
locationSpecToLocationEntity
processingResult
EntitiesSearchFilter
EntityFilter
DeferredEntity
EntityRelationSpec
CatalogProcessor
CatalogProcessorParser
CatalogProcessorCache
CatalogProcessorEmit
CatalogProcessorLocationResult
CatalogProcessorEntityResult
CatalogProcessorRelationResult
CatalogProcessorErrorResult
CatalogProcessorRefreshKeysResult
CatalogProcessorResult
EntityProvider
EntityProviderConnection
EntityProviderMutation
AnalyzeOptions
LocationAnalyzer
ScmLocationAnalyzer
PlaceholderResolver
PlaceholderResolverParams
PlaceholderResolverRead
PlaceholderResolverResolveUrl
parseEntityYaml
The following removed exports are available from
@backstage/plugin-catalog-common
:LocationSpec
AnalyzeLocationRequest
AnalyzeLocationResponse
AnalyzeLocationExistingEntity
AnalyzeLocationGenerateEntity
AnalyzeLocationEntityField
The following removed exports are instead implemented in the new backend system by
@backstage/plugin-search-backend-module-catalog
:defaultCatalogCollatorEntityTransformer
CatalogCollatorEntityTransformer
DefaultCatalogCollator
The following exports are removed without a direct replacement:
DefaultCatalogCollatorFactory
DefaultCatalogCollatorFactoryOptions
LocationEntityProcessor
LocationEntityProcessorOptions
CatalogBuilder
CatalogEnvironment
CatalogPermissionRuleInput
CatalogProcessingEngine
createRandomProcessingInterval
ProcessingIntervalFunction
Minor Changes
6c9b88e
: BREAKING ALPHA: You can no longer import the catalog plugin from the/alpha
export; 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-fetch
audit events are not visible by default in the logs and are only displayed when the log severity level is adjusted."v1.32.1
Compare Source
Patch Changes
7cc4995
: Fix for duplicate results inqueryEntities
when providing anorderField
parameterv1.32.0
Compare 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-backend
to 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.useUrlReadersSearch
config.75cadc1
: Minor internal tweak torefreshByRefreshKeys
backstage/backstage (@backstage/plugin-catalog-backend-module-github)
v0.10.0
Compare Source
Minor Changes
7c0dfb0
: GitHub organization now matches in a case-insensitive manner when processing events.Patch Changes
v0.9.0
Compare Source
Minor Changes
ff335e5
: BREAKING TheGithubLocationAnalyzer
now requires theAuthService
and theCatalogService
when being constructed and theTokenManger
has been removed.Patch Changes
ee9f59f
: Added filter to include archived repositoriesv0.8.0
Compare 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
: AddedvalidateLocationsExist
to the config definition where it was missing.v0.7.11
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-common)
v1.1.4
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-graph)
v0.4.20
Compare Source
Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.v0.4.19
Compare Source
Patch Changes
fb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.72d019d
: Removed various typos1307f00
: Fix rendering of missing relationsv0.4.18
Compare 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.17
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-import)
v0.13.2
Compare Source
Patch Changes
406b8b8
: Fixed bug with error message since ResponseError is now thrown from CatalogClientv0.13.1
Compare Source
Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.5d7c539
: Catalog import plugin full support i18nv0.13.0
Compare Source
Minor Changes
e2fd549
: BREAKING:generateStepper
anddefaultGenerateStepper
now require a translation argument to be passed through for supporting translations.Patch Changes
fb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.66a1140
: Add i18n support forcatalog-import
plugin.v0.12.13
Compare 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 theUnpackNestedValue
type as it's been removed fromreact-hook-form
f1d9a64
: adding translation forRegister an existing component
textUpdated dependencies
v0.12.12
Compare Source
Patch Changes
5b9514f
: Expose theUnpackNestedValue
type as it's been removed fromreact-hook-form
f1d9a64
: adding translation forRegister an existing component
textv0.12.11
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-catalog-react)
v1.19.0
Compare Source
Minor Changes
406acb6
: Introduces a newEntityIconLinkBlueprint
that customizes theAbout
card icon links on theCatalog
entity page.The blueprint currently accepts a
useProps
hook asparam
and this function returns the following props that will be passed to the icon link component:icon
JSX.Element
label
string
title
string
disabled
boolean
false
href
string
onClick
() => void
Here is an usage example:
Additionally, the
app-config.yaml
file allows you to override some of the default icon link parameters, includinglabel
andtitle
values. 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.0
Compare 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
: AddgetLocations
method toCatalogApi
andCatalogClient
. This method calls theGET /locations
endpoint from the catalog backend.Patch Changes
2ddbc50
: A newfilter
parameter has been added toEntityContextMenuItemBlueprint
to make it easier to configure which entities a menu item should appear for. Thefilter
parameter 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.0
Compare Source
Minor Changes
0f37fa8
:entityRouteParams
now 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
: AddsEntityContextMenuItemBlueprint
to 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 newoverview
entity content group for the new frontend system.186d016
: Addoperation
to alphadefaultEntityContentGroups
.221ddba
: Fix offset pagination to reset when updating filters inuseEntityList
Updated dependencies
v1.16.0
Compare Source
Minor Changes
7f57365
: Add support for a new entity predicate syntax when definingfilter
s related to the blueprints exported via/alpha
for the new frontend system. For more information, see the entity filters documentation.ba9649a
: Add a newdefaultGroup
parameter 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.40
Compare Source
Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.4fe364f
: Org plugin support i18nv0.6.39
Compare Source
Patch Changes
fb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.02e8af1
: Enhance user profile card configuration:maxRelations
numerical configuration that controls over how many user groups are shown directly on the profile card:maxRelations
is set to0
, the list of user groups is not displayed.maxRelations
is 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.38
Compare 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.37
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-permission-common)
v0.9.0
Compare Source
Minor Changes
4da2965
: Fixed an issue causing thePermissionClient
to exhaust the request body size limit too quickly when making many requests.Patch Changes
37328b1
: Fixed an issue causingPermissionClient
to throw an error when authorizing basic permissions with thepermission.EXPERIMENTAL_enableBatchedRequests
config enabled.72d019d
: Removed various typosbackstage/backstage (@backstage/plugin-permission-node)
v0.10.1
Compare Source
Patch Changes
v0.10.0
Compare Source
Minor Changes
4da2965
: Fixed an issue causing thePermissionClient
to exhaust the request body size limit too quickly when making many requests.Patch Changes
v0.9.1
Compare Source
Patch Changes
v0.9.0
Compare Source
Minor Changes
22ace13
: BREAKING TheServerPermissionClient
can no longer be instantiated with atokenManager
and must instead be instantiated with anauth
service. If you are still on the legacy backend system, usecreateLegacyAuthAdapters()
from@backstage/backend-common
to create a compatibleauth
service.Patch Changes
728e3e1
: Improved type inference when passing aPermissionResourceRef
tocreatePermissionRule
.876f2e1
: DeprecatedcreatePermissionIntegrationRouter
and 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.35
Compare Source
Patch Changes
v0.4.34
Compare Source
Patch Changes
v0.4.33
Compare 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.32
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-proxy-backend)
v0.6.3
Compare Source
Patch Changes
v0.6.2
Compare Source
Patch Changes
v0.6.1
Compare Source
Patch Changes
9b5b744
: Fixed handling of proxied SSE connections when the upstream server closes the connectionv0.6.0
Compare Source
Minor Changes
2d8b0e4
: BREAKING: Removed support for the old backend system.As part of this change the plugin export from
/alpha
as 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.32.0
Compare Source
Minor Changes
6c972fe
: Added information about theentityRef
andtaskId
to the analytics events whenever is possible.3c59ece
: New Frontend System Only:The
Scaffolder
plugin 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.packageJson
option 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.0
Compare Source
Minor Changes
4235e87
: add templating extensions pagePatch Changes
92c3658
: Full support in EntityPicker (and derivatives) for default EntityPresentationApifb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.d7da01d
: Fix EntityPicker field to render description as markdown, matching other form components in the system.36ae651
: Fixing a bug where the name fortemplatingExtensions
was incorrectly set totemplateExtensions
72d019d
: 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.1
Compare Source
This release fixes an issue in techdocs where the cache sync would fail because of missing service token, and
auth.externalAccess
being mistakenly required in the config schema.v1.30.0
Compare 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.0
Compare Source
Minor Changes
9d864ff
: Allowed passingui:disabled
for 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:scaffolder
extension to acceptformFields
input, matching the updatedFormFieldBlueprint
.backstage/backstage (@backstage/plugin-scaffolder-backend)
v2.0.0
Compare Source
Major Changes
33394db
: BREAKING CHANGESRemoval of deprecated re-exports from module packages.
The following functions have been re-exported from the
scaffolder-backend
plugin for quite some time, and now it's time to clean them up. They've been moved as follows:createPublishAzureAction
should be imported from@backstage/plugin-scaffolder-backend-module-azure
instead.createPublishBitbucketCloudAction
should be imported from@backstage/plugin-scaffolder-backend-module-bitbucket-cloud
instead.createPublishBitbucketServerAction
andcreatePublishBitbucketServerPullRequestAction
can be imported from@backstage/plugin-scaffolder-backend-module-bitbucket-server
instead.createPublishBitbucketAction
should be imported from@backstage/plugin-scaffolder-backend-module-bitbucket
instead.createPublishGerritAction
andcreatePublishGerritReviewAction
can be imported from@backstage/plugin-scaffolder-backend-module-gerrit
instead.createGithubActionsDispatchAction
,createGithubDeployKeyAction
,createGithubEnvironmentAction
,createGithubIssuesLabelAction
,CreateGithubPullRequestActionOptions
,createGithubRepoCreateAction
,createGithubRepoPushAction
,createGithubWebhookAction
, andcreatePublishGithubAction
can be imported from@backstage/plugin-scaffolder-backend-module-github
instead.createPublishGitlabAction
should be imported from@backstage/plugin-scaffolder-backend-module-gitlab
instead.ActionContext
.createTemplateAction
,executeShellCommand
,ExecuteShellCommandOptions
,fetchContents
,TaskSecrets
, andTemplateAction
should be imported from@backstage/plugin-scaffolder-node
instead.ScaffolderEntitiesProcessor
should be imported from@backstage/plugin-catalog-backend-module-scaffolder-entity-model
instead.a8fcf04
: BREAKING ALPHA: The/alpha
export no longer exports the plugin. Please useimport('@​backstage/plugin-scaffolder-backend')
instead as this has been removed.BREAKING CHANGES: The old
createRouter
function which was used in the old backend system has been removed along with theRouterOptions
type.73b94d7
: BREAKING CHANGESThe following functions have been re-exported from the
scaffolder-backend
plugin 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
, andTemplateGlobal
should be imported from@backstage/plugin-scaffolder-node
instead.The deprecated
copyWithoutRender
option has been removed fromfetch:template
action. You should rename the option tocopyWithoutTemplating
instead.5863b04
: BREAKING CHANGESThe
createBuiltinActions
method 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
createCatalogRegisterAction
andcreateFetchCatalogEntityAction
actions no longer require anAuthService
, and now accepts aCatalogService
instead 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-backend
after2.0.0
will influence the changes to these API surfaces.CreateWorkerOptions
DatabaseTaskStore
DatabaseTaskStoreOptions
TaskManager
TaskStoreCreateTaskOptions
TaskStoreCreateTaskResult
TaskStoreEmitOptions
TaskStoreListEventsOptions
TaskStoreRecoverTaskOptions
TaskStoreShutDownTaskOptions
There 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 youreach
step like this:e92e481
: Add tests for ScaffolderUpdated dependencies
v1.33.0
Compare Source
Minor Changes
587cb05
: Addedworkspace:template
andworkspace:template:file
actions 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 fortemplatingExtensions
was incorrectly set totemplateExtensions
72d019d
: Removed various typosec42f8e
: Generating new tokens on each Scaffolder Task Retryv1.32.1
Compare 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.0
Compare Source
Minor Changes
75e4db4
: add template-extensions scaffolder service endpointPatch Changes
8685cab
: Addedtemplate
andstep
labels for scaffolder histogram metrics:scaffolder_task_duration
andscaffolder_step_duration
497d47a
: Document the internal built-in filters, and ensure that the types are validated when usingcreateTemplateFilter
andcreateTemplateGlobalFunction
from thezod
schema.v1.31.0
Compare Source
Minor Changes
36677bb
: Support newcreateTemplateAction
type, and convertcatalog:fetch
action to new way of defining actions.2b1e50d
: use CreatedTemplate[Filter|Global*] as canonical template extensions in scaffolder pluginPatch Changes
e0b226b
: build(deps): bumpesbuild
from 0.24.2 to 0.25.009cf038
: Got rid of most@backstage/backend-common
usages4f8b5b6
: 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.4.27
Compare Source
Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.v1.4.26
Compare Source
Patch Changes
fb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.fa48594
: search plugin support i18nv1.4.25
Compare Source
Patch Changes
e655f62
: UpdatedREADME.md
to useyarn start
instead 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.24
Compare 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.3
Compare Source
Patch Changes
c83cd8b
: Fixed some circular or otherwise unclear importsv2.0.2
Compare Source
Patch Changes
v2.0.1
Compare Source
Patch Changes
v2.0.0
Compare 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.45
Compare Source
Patch Changes
v0.5.44
Compare Source
Patch Changes
v0.5.43
Compare Source
Patch Changes
v0.5.42
Compare 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.12
Compare Source
Patch Changes
v1.3.11
Compare Source
Patch Changes
v1.3.10
Compare Source
Patch Changes
v1.3.9
Compare Source
Patch Changes
backstage/backstage (@backstage/plugin-search-react)
v1.9.1
Compare Source
Patch Changes
869fa46
: SearchBar clear button support i18nv1.9.0
Compare Source
Minor Changes
611c941
: Allow search filters to provide labels and values separately, and not only valuesPatch Changes
2c76614
: Fix memoization offilterValue
inSearchFilter.Autocomplete
to prevent unintended resetsfa48594
: search plugin support i18nv1.8.8
Compare 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.7
Compare 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.13.1
Compare Source
This release bumps the minimum required version of
vm2
to 3.9.17v1.13.0
Compare Source
Minor Changes
3c59ece
: New Frontend System Only:The
TechDocs
plugin is now responsible for providing an entity icon link extension to read documentation from the catalog entity page.ec7b35d
: Introducedbackstage.io/techdocs-entity-path
annotation which allows deep linking into another entities TechDocs in conjunction withbackstage.io/techdocs-entity
.Patch Changes
18c64e9
: Added theinfo.packageJson
option to the plugin instance for the new frontend system.9dde3ba
: Improved Keyboard accessibility in techdocs.v1.12.6
Compare Source
Patch Changes
fb58f20
: Internal update to use the newpluginId
option 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.5
Compare 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.4
Compare 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
: AddedTechDocsAddonsBlueprint
extension 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.0.3
Compare Source
Patch Changes
v2.0.2
Compare Source
Patch Changes
72d019d
: Removed various typosv2.0.1
Compare Source
Patch Changes
v2.0.0
Compare 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-techdocs
for this instead. Finally, deprecatedDocsBuildStrategy
andTechDocsDocument
were removed, use the versions in@backstage/plugin-techdocs-node
instead.Patch Changes
7828186
: Minor type fix8f03776
: Properly clean up temporary files on build failuresbackstage/backstage (@backstage/plugin-techdocs-module-addons-contrib)
v1.1.25
Compare Source
Patch Changes
9dde3ba
: Improved Keyboard accessibility in techdocs.v1.1.24
Compare Source
Patch Changes
v1.1.23
Compare 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 inReportIssue
addon 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.22
Compare Source
Patch Changes
b5a8208
: AddedTechDocsAddonsBlueprint
extension to allow adding of techdocs addons.backstage/backstage (@backstage/plugin-techdocs-react)
v1.3.0
Compare Source
Minor Changes
ec7b35d
: Introducedbackstage.io/techdocs-entity-path
annotation which allows deep linking into another entities TechDocs in conjunction withbackstage.io/techdocs-entity
.Patch Changes
v1.2.17
Compare Source
Patch Changes
72d019d
: Removed various typosv1.2.16
Compare 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.15
Compare Source
Patch Changes
b5a8208
: AddedTechDocsAddonsBlueprint
extension to allow adding of techdocs addons.backstage/backstage (@backstage/plugin-user-settings)
v0.8.23
Compare Source
Patch Changes
18c64e9
: Added theinfo.packageJson
option 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.22
Compare Source
Patch Changes
a7bfdb6
: plugin-user-settingsgs support i18nfb58f20
: Internal update to use the newpluginId
option ofcreateFrontendPlugin
.5b04b14
: Uppercase language name in language selectv0.8.21
Compare 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.20
Compare Source
Patch Changes
backstage/backstage (@backstage/test-utils)
v1.7.9
Compare Source
Patch Changes
v1.7.8
Compare Source
Patch Changes
b573341
: Added support for interpolating JSX elements with theMockTranslationApi
.v1.7.7
Compare 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.6
Compare Source
Patch Changes
37c6510
: Moved@types/jest
todevDependencies
.backstage/backstage (@backstage/theme)
v0.6.6
Compare Source
Patch Changes
1b14572
: Show arrow when MuiTableSortLabel receives focusv0.6.5
Compare 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.
e08caeae7e
to22ca21e44b
22ca21e44b
to0ad432ba1c
0ad432ba1c
tob27af21919
b27af21919
to9184db3c16
9184db3c16
to6a866e99a6
6a866e99a6
tob4cc567b11
Checkout
From your project repository, check out a new branch and test the changes.