Bump @backstage/plugin-catalog-node from 1.17.1 to 1.19.0

[dependabot]

Bumps @backstage/plugin-catalog-node from 1.17.1 to 1.19.0.

Changelog

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

1.19.0

Minor Changes

• 0e9ec44: Introduced new streamEntities async generator method for the catalog.

  Catalog API and Catalog Service now includes a streamEntities method 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:

  const pageStream = catalogClient.streamEntities({ pageSize: 100 }, { token });
  for await (const page of pageStream) {
    // Handle page of entities
    for (const entity of page) {
      console.log(entity);
    }
  }

Patch Changes

• 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 getPriority method in the processor class or by adding a catalog.processors.<processorName>.priority configuration in the app-config.yaml file. The configuration takes precedence over the method.

• Updated dependencies

  • @​backstage/catalog-client@​1.12.0
  • @​backstage/types@​1.2.2
  • @​backstage/backend-plugin-api@​1.4.3
  • @​backstage/plugin-permission-node@​0.10.4

1.19.0-next.1

Minor Changes

• 0e9ec44: Introduced new streamEntities async generator method for the catalog.

  Catalog API and Catalog Service now includes a streamEntities method 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

... (truncated)

Commits

• 8cdb8c2 Version Packages
• e43d3eb Version Packages (next)
• f95345c Version Packages (next)
• 7a2e292 Deprecated LocationEntityProcessor, added doc comments
• bea3617 Version Packages (next)
• b228d7d Version Packages
• a6d1580 Version Packages (next)
• 32a09ad Version Packages (next)
• fc1a38b Version Packages (next)
• 00beb2b Merge pull request #19485 from backstage/catalog-info/project-areas
• Additional commits viewable 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)