[release-v1.16][npm]: Bump the minor group across 5 directories with 41 updates

[dependabot]

Bumps the minor group with 34 updates in the /backstage directory:

Package	From	To
@backstage/cli	0.24.0	0.31.0
@playwright/test	1.40.1	1.51.1
typescript	5.2.2	5.8.2
@backstage/app-defaults	1.4.5	1.6.0
@backstage/core-components	0.13.8	0.17.0
@backstage/integration-react	1.1.21	1.2.5
@backstage/plugin-api-docs	0.10.1	0.12.5
@backstage/plugin-catalog-graph	0.3.1	0.4.17
@backstage/plugin-catalog-import	0.10.3	0.12.11
@backstage/plugin-scaffolder	1.16.1	1.29.0
@backstage/plugin-search-react	1.7.3	1.8.7
@backstage/plugin-tech-radar	0.6.10	0.7.4
@backstage/plugin-techdocs	1.9.1	1.12.4
@backstage/plugin-user-settings	0.7.13	0.8.20
@backstage/theme	0.4.4	0.6.4
react-use	17.4.2	17.6.0
@backstage/test-utils	1.4.5	1.7.6
@testing-library/user-event	14.5.1	14.6.1
@backstage/backend-common	0.19.9	0.25.0
@backstage/backend-tasks	0.5.23	0.6.1
@backstage/plugin-app-backend	0.3.55	0.5.0
@backstage/plugin-auth-backend	0.20.0	0.24.4
@backstage/plugin-auth-node	0.4.13	0.6.1
@backstage/plugin-catalog-backend	1.22.0	1.32.0
@backstage/plugin-catalog-backend-module-scaffolder-entity-model	0.1.4	0.2.6
@backstage/plugin-permission-common	0.7.13	0.8.4
@backstage/plugin-permission-node	0.7.29	0.9.0
@backstage/plugin-proxy-backend	0.4.5	0.6.0
@backstage/plugin-scaffolder-backend	1.19.1	1.31.0
@backstage/plugin-search-backend-module-catalog	0.1.24	0.3.2
@backstage/plugin-search-backend-module-techdocs	0.1.11	0.4.0
pg	8.11.3	8.14.1
winston	3.11.0	3.17.0
@backstage/backend-dynamic-feature-service	0.2.10	0.6.1

Bumps the minor group with 8 updates in the /backstage/packages/app directory:

Package	From	To
@backstage/cli	0.24.0	0.31.0
@backstage/core-components	0.13.10	0.17.0
@backstage/plugin-api-docs	0.10.3	0.12.5
@backstage/plugin-catalog-graph	0.3.3	0.4.17
@backstage/plugin-catalog-import	0.10.10	0.12.11
@backstage/plugin-tech-radar	0.6.13	0.7.4
@backstage/plugin-user-settings	0.7.14	0.8.20
@backstage/theme	0.4.4	0.6.4

Bumps the minor group with 9 updates in the /backstage/packages/backend directory:

Package	From	To
@backstage/plugin-app-backend	0.3.76	0.5.0
@backstage/plugin-auth-backend	0.20.3	0.24.4
@backstage/plugin-auth-node	0.4.17	0.6.1
@backstage/plugin-catalog-backend-module-scaffolder-entity-model	0.1.22	0.2.6
@backstage/plugin-permission-common	0.7.14	0.8.4
@backstage/plugin-permission-node	0.7.32	0.9.0
@backstage/plugin-proxy-backend	0.4.16	0.6.0
@backstage/plugin-search-backend-module-catalog	0.1.28	0.3.2
@backstage/plugin-search-backend-module-techdocs	0.1.27	0.4.0

Bumps the minor group with 4 updates in the /backstage/plugins/knative-event-mesh-backend directory: @backstage/cli, @backstage/backend-common, @backstage/backend-tasks and @backstage/backend-dynamic-feature-service.
Bumps the minor group with 2 updates in the /backstage/plugins/knative-event-mesh-backend/dist-dynamic directory: express and winston.

Updates @backstage/cli from 0.24.0 to 0.31.0

Changelog

Sourced from @​backstage/cli's changelog.

0.31.0

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 the backstage-cli <repo|package> lint command.

Patch Changes

• 0586d4c: Internal change to move the migrate and version:* commands into a new migrate module.
• e0b226b: build(deps): bump esbuild from 0.24.2 to 0.25.0
• 4d45498: Fixed the package prepack command so that it no longer produces unnecessary index entries in the typesVersions map, which could cause /index to be added when automatically adding imports.
• 485b3ba: Internal update to move test commands to a separate module.
• a76c482: Internal change to migrate lint to the new module system.
• 8df78bf: Internal update to move build commands to a CLI module.
• d0fc357: Internal update to move info commands to a separate module.
• f8bd342: Fix a bug in the translation of the deprecated --scope option for the new command that could cause plugins to have backstage-backstage-plugin in their name.
• Updated dependencies
  • @​backstage/config-loader@​1.10.0
  • @​backstage/integration@​1.16.2
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/cli-common@​0.1.15
  • @​backstage/cli-node@​0.2.13
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/eslint-plugin@​0.1.10
  • @​backstage/release-manifests@​0.0.12
  • @​backstage/types@​1.2.1

0.31.0-next.1

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 the backstage-cli <repo|package> lint command.

Patch Changes

• e0b226b: build(deps): bump esbuild from 0.24.2 to 0.25.0
• 4d45498: Fixed the package prepack command so that it no longer produces unnecessary index entries in the typesVersions map, which could cause /index to be added when automatically adding imports.
• f8bd342: Fix a bug in the translation of the deprecated --scope option for the new command that could cause plugins to have backstage-backstage-plugin in their name.
• Updated dependencies
  • @​backstage/config-loader@​1.10.0-next.0
  • @​backstage/integration@​1.16.2-next.0
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/cli-common@​0.1.15
  • @​backstage/cli-node@​0.2.13
  • @​backstage/config@​1.3.2

... (truncated)

Commits

• 4a93128 Version Packages
• c8a7089 Merge pull request #5924 from backstage/rugvip/best
• 30627bd check array length and only add newlines if length > 0
• f3a3134 fix(cli): fix TypeError when formatting error messages
• 5da7171 fix(cli): fix TypeError when formatting error messages
• 9cd3c53 cli: switch to @​sucrase/plugin-jest instead of ts-jest
• cfc221b Merge pull request #5897 from backstage/dependabot/npm_and_yarn/typescript-es...
• 7f74433 chore(deps): bump @​typescript-eslint/eslint-plugin from 4.15.2 to 4.26.0
• fa92d70 Version Packages
• 644d315 Merge pull request #5877 from backstage/rugvip/cli-updates
• Additional commits viewable in compare view

Updates @playwright/test from 1.40.1 to 1.51.1

Release notes

Sourced from @​playwright/test's releases.

v1.51.1

Highlights

microsoft/playwright#35093 - [Regression]: TimeoutOverflowWarning: 2149630296.634 does not fit into a 32-bit signed integer microsoft/playwright#35138 - [Regression]: TypeError: Cannot read properties of undefined (reading 'expectInfo')

Browser Versions

• Chromium 134.0.6998.35
• Mozilla Firefox 135.0
• WebKit 18.4

This version was also tested against the following stable channels:

• Google Chrome 133
• Microsoft Edge 133

v1.51.0

StorageState for indexedDB

• New option indexedDB for browserContext.storageState() allows to save and restore IndexedDB contents. Useful when your application uses IndexedDB API to store authentication tokens, like Firebase Authentication.

  Here is an example following the authentication guide:

  // tests/auth.setup.ts
  import { test as setup, expect } from '@playwright/test';
  import path from 'path';
  const authFile = path.join(__dirname, '../playwright/.auth/user.json');
  setup('authenticate', async ({ page }) => {
  await page.goto('/');
  // ... perform authentication steps ...
  // make sure to save indexedDB
  await page.context().storageState({ path: authFile, indexedDB: true });
  });

Copy prompt

New "Copy prompt" button on errors in the HTML report, trace viewer and UI mode. Click to copy a pre-filled LLM prompt that contains the error message and useful context for fixing the error.

Filter visible elements

New option visible for locator.filter() allows matching only visible elements.

</tr></table> 

... (truncated)

Commits

• 0ad26b3 chore: mark v1.51.1 (#35098)
• 25c0deb cherry-pick(#35149): fix(expect): properly handle custom asymmetric matcher r...
• 4ecf5e0 cherry-pick(#35096): chore: do not use |0 for rounding large numbers
• 3707a93 cherry-pick(#35045): chore: hide indexedDB in BrowserContext.storageState() b...
• 52ddca4 cherry-pick(#35043): docs: release notes for 1.51 for java, python, csharp
• 1f13108 cherry-pick(#35058): chore: hide indexedDB from storageState() and BrowserCon...
• 9e9f0d1 cherry-pick(#35062): do not compute git diff on non! PRs
• 12835d6 cherry-pick(#35059): chore: typo in prompt (#35061)
• ef33c83 cherry-pick(#35057): chore: rename to copy prompt
• 224385a cherry-pick(#35050): docs: update Git information image in release notes
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by dgozman-ms, a new releaser for @​playwright/test since your current version.

Updates typescript from 5.2.2 to 5.8.2

Release notes

Sourced from typescript's releases.

TypeScript 5.8

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).
• fixed issues query for Typescript 5.8.2 (Stable).

Downloads are available on:

• npm

TypeScript 5.8 RC

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).
• fixed issues query for Typescript 5.8.1 (RC).

Downloads are available on:

• npm

TypeScript 5.8 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.8.0 (Beta).

Downloads are available on:

• npm

TypeScript 5.7.3

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.7.0 (Beta).
• fixed issues query for Typescript 5.7.1 (RC).
• fixed issues query for Typescript 5.7.2 (Stable).
• fixed issues query for Typescript 5.7.3 (Stable).

Downloads are available on npm

TypeScript 5.7

For release notes, check out the release announcement.

• fixed issues query for Typescript 5.7.0 (Beta).
• fixed issues query for Typescript 5.7.1 (RC).
• fixed issues query for Typescript 5.7.2 (Stable).

Downloads are available on:

• npm

TypeScript 5.7 RC

For release notes, check out the release announcement.

... (truncated)

Commits

• beb69e4 Bump version to 5.8.2 and LKG
• 8fdbd54 🤖 Pick PR #61210 (Fix mistakenly disallowed default e...) into release-5.8 (#...
• f4a3a8a 🤖 Pick PR #61175 (Ban import=require and export= unde...) into release-5.8 (#...
• 420ff06 Bump version to 5.8.1-rc and LKG
• 48eb13f Update LKG
• fb59c19 Merge remote-tracking branch 'origin/main' into release-5.8
• df342b7 Fixed rewriteRelativeImportExtensions for import() within call expression...
• 775412a Bump github/codeql-action from 3.28.8 to 3.28.9 in the github-actions group (...
• e1629e5 Pass ignoreErrors=true to more resolveEntityName callers (#61144)
• 6fd1799 Update LKG
• Additional commits viewable in compare view

Updates @backstage/app-defaults from 1.4.5 to 1.6.0

Changelog

Sourced from @​backstage/app-defaults's changelog.

1.6.0

Minor Changes

• 12f8e01: BREAKING: The default DiscoveryApi implementation has been switched to use FrontendHostDiscovery, which adds support for the discovery.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:

  app:
    baseUrl: https://backstage.acme.org
  backend:
  baseUrl: https://backstage.internal.acme.org
  discovery:
  endpoints:
  - target: https://catalog.internal.acme.org/api/{{pluginId}}
  plugins: [catalog]

  This will now cause requests from the frontend towards the catalog plugin to be routed to https://catalog.internal.acme.org/api/catalog, but this might not be reachable from the frontend. To fix this, you should update the discovery.endpoints configuration to only override the internal URL of the plugin:

  discovery:
    endpoints:
      - target:
          internal: https://catalog.internal.acme.org/api/{{pluginId}}
        plugins: [catalog]

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.17.0
  • @​backstage/core-plugin-api@​1.10.5
  • @​backstage/core-app-api@​1.16.0
  • @​backstage/plugin-permission-react@​0.4.32
  • @​backstage/theme@​0.6.4

1.6.0-next.1

Minor Changes

• 12f8e01: BREAKING: The default DiscoveryApi implementation has been switched to use FrontendHostDiscovery, which adds support for the discovery.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.

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/core-app-api from 1.11.1 to 1.16.0

Changelog

Sourced from @​backstage/core-app-api's changelog.

1.16.0

Minor Changes

• 9262001: The default auth injection middleware for the FetchApi will now also take configuration under discovery.endpoints into consideration when deciding whether to include credentials or not.
• 12f8e01: The discovery.endpoints configuration no longer requires both internal and external target when using the object form, instead falling back to the default.

Patch Changes

• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.5
  • @​backstage/config@​1.3.2
  • @​backstage/types@​1.2.1
  • @​backstage/version-bridge@​1.0.11

1.16.0-next.0

Minor Changes

• 9262001: The default auth injection middleware for the FetchApi will now also take configuration under discovery.endpoints into consideration when deciding whether to include credentials or not.
• 12f8e01: The discovery.endpoints configuration no longer requires both internal and external target when using the object form, instead falling back to the default.

Patch Changes

• Updated dependencies
  • @​backstage/config@​1.3.2
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/types@​1.2.1
  • @​backstage/version-bridge@​1.0.11

1.15.5

Patch Changes

• 58ec9e7: Removed older versions of React packages as a preparatory step for upgrading to React 19. This commit does not introduce any functional changes, but removes dependencies on previous React versions, allowing for a cleaner upgrade path in subsequent commits.
• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/version-bridge@​1.0.11
  • @​backstage/config@​1.3.2
  • @​backstage/types@​1.2.1

1.15.5-next.0

Patch Changes

• 58ec9e7: Removed older versions of React packages as a preparatory step for upgrading to React 19. This commit does not introduce any functional changes, but removes dependencies on previous React versions, allowing for a cleaner upgrade path in subsequent commits.
• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.4-next.0
  • @​backstage/version-bridge@​1.0.11-next.0
  • @​backstage/config@​1.3.2

... (truncated)

Commits

• 0abb3c3 Version Packages
• a77ddf7 feat: add login in popup options to config popup width and weigth
• 3cedd03 Version Packages (next)
• 823bf52 Merge pull request #18558 from oliviertassinari/mui-material-ui
• a51fb51 fix: use Material UI vs. MUI where relevant
• 2fc17fb Version Packages (next)
• bc0c4bc Version Packages
• 9a8d34a Merge pull request #17999 from backstage/analytics/handle-gathered-mountpoints
• 98ed4fe Merge pull request #18234 from backstage/blam/jsdom-env
• ac677bc expose discovery.endpoints to frontend
• Additional commits viewable in compare view

Updates @backstage/core-components from 0.13.8 to 0.17.0

Changelog

Sourced from @​backstage/core-components's changelog.

0.17.0

Minor Changes

• 25300cb: SimpleStepper back button now works with activeStep property set higher than 0
• 9545af2: 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: Added classNames prop to the Page component

• df3b9f0: 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 plugin

• 0a0ced6: Avoid Layout Shift for DismissableBanner when using a storageApi with latency (e.g. user-settings-backend)

  Properly handle the unknown state of the storageApi. 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/core-plugin-api@​1.10.5
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/theme@​0.6.4
  • @​backstage/version-bridge@​1.0.11

0.16.5-next.1

Patch Changes

• 48aab13: Add i18n support for scaffolder-react plugin
• Updated dependencies
  • @​backstage/config@​1.3.2
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/errors@​1.2.7
  • @​backstage/theme@​0.6.4
  • @​backstage/version-bridge@​1.0.11

0.16.5-next.0

Patch Changes

• fffe3c0: Added classNames prop to the Page component
• df3b9f0: 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.
• Updated dependencies
  • @​backstage/config@​1.3.2
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/errors@​1.2.7
  • @​backstage/theme@​0.6.4
  • @​backstage/version-bridge@​1.0.11

0.16.4

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/core-plugin-api from 1.8.0 to 1.10.5

Changelog

Sourced from @​backstage/core-plugin-api's changelog.

1.10.5

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 the BootErrorPage app component.
• Updated dependencies
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/types@​1.2.1
  • @​backstage/version-bridge@​1.0.11

1.10.4

Patch Changes

• 58ec9e7: Removed older versions of React packages as a preparatory step for upgrading to React 19. This commit does not introduce any functional changes, but removes dependencies on previous React versions, allowing for a cleaner upgrade path in subsequent commits.
• Updated dependencies
  • @​backstage/version-bridge@​1.0.11
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/types@​1.2.1

1.10.4-next.0

Patch Changes

• 58ec9e7: Removed older versions of React packages as a preparatory step for upgrading to React 19. This commit does not introduce any functional changes, but removes dependencies on previous React versions, allowing for a cleaner upgrade path in subsequent commits.
• Updated dependencies
  • @​backstage/version-bridge@​1.0.11-next.0
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/types@​1.2.1

1.10.3

Patch Changes

• b40eb41: Move Expand and ExpandRecursive to @backstage/types
• Updated dependencies
  • @​backstage/types@​1.2.1
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/version-bridge@​1.0.10

1.10.3-next.0

Patch Changes

• b40eb41: Move Expand and ExpandRecursive to @backstage/types
• Updated dependencies

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/integration-react from 1.1.21 to 1.2.5

Changelog

Sourced from @​backstage/integration-react's changelog.

1.2.5

Patch Changes

• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.5
  • @​backstage/integration@​1.16.2
  • @​backstage/config@​1.3.2

1.2.5-next.0

Patch Changes

• Updated dependencies
  • @​backstage/integration@​1.16.2-next.0
  • @​backstage/config@​1.3.2
  • @​backstage/core-plugin-api@​1.10.4

1.2.4

Patch Changes

• 58ec9e7: Removed older versions of React packages as a preparatory step for upgrading to React 19. This commit does not introduce any functional changes, but removes dependencies on previous React versions, allowing for a cleaner upgrade path in subsequent commits.
• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/config@​1.3.2
  • @​backstage/integration@​1.16.1

1.2.4-next.0

Patch Changes

• 58ec9e7: Removed older versions of React packages as a preparatory step for upgrading to React 19. This commit does not introduce any functional changes, but removes dependencies on previous React versions, allowing for a cleaner upgrade path in subsequent commits.
• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.4-next.0
  • @​backstage/config@​1.3.2
  • @​backstage/integration@​1.16.1

1.2.3

Patch Changes

• Updated dependencies
  • @​backstage/core-plugin-api@​1.10.3
  • @​backstage/integration@​1.16.1
  • @​backstage/config@​1.3.2

1.2.3-next.0

Patch Changes

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/plugin-api-docs from 0.10.1 to 0.12.5

Changelog

Sourced from @​backstage/plugin-api-docs's changelog.

0.12.5

Patch Changes

• 74871cc: Use consistent Typography in Entity HasApisCard
• Updated dependencies
  • @​backstage/core-components@​0.17.0
  • @​backstage/plugin-catalog@​1.28.0
  • @​backstage/core-plugin-api@​1.10.5
  • @​backstage/frontend-plugin-api@​0.10.0
  • @​backstage/plugin-catalog-react@​1.16.0
  • @​backstage/core-compat-api@​0.4.0
  • @​backstage/plugin-permission-react@​0.4.32
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/plugin-catalog-common@​1.1.3

0.12.5-next.2

Patch Changes

• 74871cc: Use consistent Typography in Entity HasApisCard
• Updated dependencies
  • @​backstage/plugin-catalog@​1.28.0-next.2
  • @​backstage/frontend-plugin-api@​0.10.0-next.2
  • @​backstage/plugin-catalog-react@​1.16.0-next.2
  • @​backstage/core-compat-api@​0.4.0-next.2
  • @​backstage/core-components@​0.16.5-next.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/plugin-catalog-common@​1.1.3
  • @​backstage/plugin-permission-react@​0.4.31

0.12.5-next.1

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.16.5-next.0
  • @​backstage/plugin-catalog-react@​1.16.0-next.1
  • @​backstage/core-compat-api@​0.3.7-next.1
  • @​backstage/plugin-catalog@​1.28.0-next.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/frontend-plugin-api@​0.9.6-next.1
  • @​backstage/plugin-catalog-common@​1.1.3
  • @​backstage/plugin-permission-react@​0.4.31

0.12.5-next.0

Patch Changes

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/plugin-catalog from 1.15.1 to 1.28.0

Release notes

Sourced from @​backstage/plugin-catalog's releases.

v1.28.0

These are the release notes for the v1.28.0 release of Backstage.

A huge thanks to the whole team of maintainers and contributors as well as the amazing Backstage Community for the hard work in getting this release developed and done.

Highlights

BREAKING: Proxy backend plugin protected by default

The proxy backend plugin is now protected by Backstage auth, by default. Unless specifically configured (see below), all proxy endpoints will reject requests immediately unless a valid Backstage user or service token is passed along with the request. This aligns the proxy with how other Backstage backends behave out of the box, and serves to protect your upstreams from unauthorized access.

Here's an example of how to configure:

  proxy:
    endpoints:
      '/pagerduty':
        target: https://api.pagerduty.com
+       credentials: require
        headers:
          Authorization: Token token=${PAGERDUTY_TOKEN}

There are three credentials settings:

• require: Callers need Backstage credentials. These are not forwarded to the target.
• forward: Callers need Backstage credentials, which are forwarded to the target.
• dangerously-allow-unauthenticated: No Backstage credentials needed. Target can apply its own checks. Incoming tokens of any sort will be allowed but ignored, and will also be forwarded if allowedHeaders: ['Authorization'] is included.

The new default is require, replacing the old dangerously-allow-unauthenticated. This means some previously permitted requests may now result in 401 Unauthorized responses. This does not apply if backend.auth.dangerouslyDisableDefaultAuthPolicy is set to true.

For proxy endpoints still requiring unauthenticated access, add credentials: dangerously-allow-unauthenticated in your app-config.

See the proxy documentation for more information.

BREAKING: Gerrit integration breaking changes

• The workdir argument have been removed from The GerritUrlReader constructor;
• The Gerrit readTree implementation will now only use the Gitiles api, so the support for using git to clone the repo has been removed;
• The gitilesBaseUrl is now mandatory for the Gerrit integration and the ability to override this requirement using the DISABLE_GERRIT_GITILES_REQUIREMENT environment variable has been removed.

Contributed by @​anicke in #25123.

BREAKING: Github integration breaking changes

• Removed deprecated code from when casing was changed from GitHub to Github nearly two years ago. The following items have been removed:
  • getGitHubFileFetchUrl (use getGithubFileFetchUrl instead)
  • GitHubIntegrationConfig (use GithubIntegrationConfig instead)
  • GitHubIntegration (use GithubIntegration instead)
  • readGitHubIntegrationConfig (use readGithubIntegrationConfig instead)

... (truncated)

Changelog

Sourced from @​backstage/plugin-catalog's changelog.

1.28.0

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.

  • Cards of type info are rendered in a fixed area on the right;
  • Cards of type peek are rendered on top of the main content area;
  • Cards of type 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:

  app:
    extensions:
      # Entity page cards
  +   - entity-card:catalog/about:
  +       config:
  +         type: info # or peek or full

• 93533bd: The order in which group tabs appear on the entity page has been changed.

  Before

  Previously, entity contents determined the order in which groups were rendered, so a group was rendered as soon as its first entity content was detected.

  After

  Groups are now rendered first by default based on their order in the app-config.yaml file:

  app:
    extensions:
      - page:catalog/entity:
  +       config:
  +         groups:
  +           # this will be the first tab of the default entity page
  +           - deployment:
  +               title: Deployment
  +           # this will be the second tab of the default entiy page
  +           - documentation:
  +               title: Documentation

  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).

  app:

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/plugin-catalog-graph from 0.3.1 to 0.4.17

Changelog

Sourced from @​backstage/plugin-catalog-graph's changelog.

0.4.17

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.17.0
  • @​backstage/core-plugin-api@​1.10.5
  • @​backstage/frontend-plugin-api@​0.10.0
  • @​backstage/plugin-catalog-react@​1.16.0
  • @​backstage/core-compat-api@​0.4.0
  • @​backstage/catalog-client@​1.9.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/types@​1.2.1

0.4.17-next.2

Patch Changes

• Updated dependencies
  • @​backstage/frontend-plugin-api@​0.10.0-next.2
  • @​backstage/plugin-catalog-react@​1.16.0-next.2
  • @​backstage/core-compat-api@​0.4.0-next.2
  • @​backstage/core-components@​0.16.5-next.1
  • @​backstage/catalog-client@​1.9.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/types@​1.2.1

0.4.17-next.1

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.16.5-next.0
  • @​backstage/plugin-catalog-react@​1.16.0-next.1
  • @​backstage/core-compat-api@​0.3.7-next.1
  • @​backstage/catalog-client@​1.9.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/frontend-plugin-api@​0.9.6-next.1
  • @​backstage/types@​1.2.1

0.4.17-next.0

Patch Changes

• Updated dependencies
  • @​backstage/plugin-catalog-react@​1.16.0-next.0
  • @​backstage/frontend-plugin-api@​0.9.6-next.0
  • @​backstage/core-compat-api@​0.3.7-next.0

... (truncated)

Commits

• See full diff in compare view

Updates @backstage/plugin-catalog-import from 0.10.3 to 0.12.11

Changelog

Sourced from @​backstage/plugin-catalog-import's changelog.

0.12.11

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.17.0
  • @​backstage/core-plugin-api@​1.10.5
  • @​backstage/integration@​1.16.2
  • @​backstage/frontend-plugin-api@​0.10.0
  • @​backstage/plugin-catalog-react@​1.16.0
  • @​backstage/core-compat-api@​0.4.0
  • @​backstage/integration-react@​1.2.5
  • @​backstage/catalog-client@​1.9.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/config@​1.3.2
  • @​backstage/errors@​1.2.7
  • @​backstage/plugin-catalog-common@​1.1.3

0.12.11-next.2

Patch Changes

• Updated dependencies
  • @​backstage/frontend-plugin-api@​0.10.0-next.2
  • @​backstage/plugin-catalog-react@​1.16.0-next.2
  • @​backstage/core-compat-api@​0.4.0-next.2
  • @​backstage/core-components@​0.16.5-next.1
  • @​backstage/integration@​1.16.2-next.0
  • @​backstage/catalog-client@​1.9.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/config@​1.3.2
  • @​backstage/core-plugin-api@​1.10.4
  • @​backstage/errors@​1.2.7
  • @​backstage/integration-react@​1.2.5-next.0
  • @​backstage/plugin-catalog-common@​1.1.3

0.12.11-next.1

Patch Changes

• Updated dependencies
  • @​backstage/core-components@​0.16.5-next.0
  • @​backstage/plugin-catalog-react@​1.16.0-next.1
  • @​backstage/core-compat-api@​0.3.7-next.1
  • @​backstage/catalog-client@​1.9.1
  • @​backstage/catalog-model@​1.7.3
  • @​backstage/config@​1Description has been truncated

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign cali0707 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a openshift-knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.