Bump @backstage/plugin-search-common from 1.0.1 to 1.1.0

[dependabot[bot]]

Bumps @backstage/plugin-search-common from 1.0.1 to 1.1.0.

Release notes

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

v1.1.0

These are the release notes for the v1.1.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

Auth

The auth backend and node package received a few BREAKING changes.

You are now required to always return a token from the result of a sign-in resolver, and all default sign-in resolvers have been removed. This means that you will have to make a conscious choice to use one of a few predefined resolver functions to be able to use a given auth provider for signing in, or to write your own. Don’t worry, it’s actually rather straightforward to do, and ends up clarifying responsibilities for safe authentication and catalog ownership.

There are also a number of deprecations among the exported auth backend types, which you may want to adapt to.

For more information, see the relevant documentation section about sign-in resolvers, and the backend/node changelogs.

CLI

The CLI has bumped the jest version from ^26.0.1 to ^27.5.1. You can find the complete list of breaking changes here.

We strongly recommend having completed the package role migration before upgrading to this version, as the package roles are used to automatically determine the testing environment for each package.

Note that one of the breaking changes of Jest 27 is that the jsdom environment no longer includes setImmediate and clearImmediate, which means you might need to update some of your frontend packages. Another notable change is that jest.useFakeTimers now defaults to the 'modern' implementation, which also mocks microtasks.

Kubernetes

The Kubernetes backend has a BREAKING change, in that cluster suppliers now need to cache their results to allow frequent calls to their methods. This was done to pave the way for custom suppliers that dynamically fetch results from the real authority, instead of hard coding them in config. Thanks @​heyLu! (#10428)

Permissions

The permission related packages received a number of BREAKING changes. Among other things, the names of types were settled to be made more crisp and clear. This will mostly apply to those who write custom permissions. This all goes to the common, node, and react packages, whose changelogs are linked here.

Stack Overflow

There’s a new Stack Overflow frontend plugin with a corresponding [backend](https://github.com/backstage/backstage/tree/master/plugins/stack-overflow-backend]!

Misc

• The CI/CD Statistics plugin now has GitLab support, through the new GitLab module. Thanks @​djamaile! (#10140)

• The catalog AWS module added a new AwsS3EntityProvider as a replacement for the AwsS3DiscoveryProcessor. Thanks @​pjungermann! (#10480)

• The permissions-related exports from the catalog backend have some breaking changes. These are all in alpha still, so this only applies to you if you are developing catalog permissions and import from @backstage/plugin-catalog-backend/alpha.

Security Fixes

This release does not contain any security fixes.

Upgrade path

... (truncated)

Changelog

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

1.1.0

Minor Changes

• a799972bb1: There is a new property called pageLimit on the SearchQuery interface that specifies how many results should be returned per page.

Patch Changes

• Updated dependencies
  • @​backstage/plugin-permission-common@​0.7.0
  • @​backstage/types@​1.0.0

1.1.0-next.2

Patch Changes

• Updated dependencies
  • @​backstage/plugin-permission-common@​0.7.0-next.2
  • @​backstage/types@​1.0.0

1.1.0-next.1

Minor Changes

• a799972bb1: There is a new property called pageLimit on the SearchQuery interface that specifies how many results should be returned per page.

Patch Changes

• Updated dependencies
  • @​backstage/types@​1.0.0
  • @​backstage/plugin-permission-common@​0.6.5-next.1

1.0.2-next.0

Patch Changes

• Updated dependencies
  • @​backstage/types@​1.0.0
  • @​backstage/plugin-permission-common@​0.6.5-next.0

Commits

• 3f7acfb Version Packages
• e6f3fb8 Version Packages (next)
• ad955c1 Version Packages (next)
• d48122a search: discourage use of IndexableDocument in the frontend
• a6d4022 search-common: restrict allowed type parameters for Result and ResultSet
• c8b295f search-common: introduce SearchDocument type
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

Looks like @backstage/plugin-search-common is up-to-date now, so this is no longer needed.