Skip to content

Latest commit

 

History

History
4281 lines (3264 loc) · 141 KB

v1.24.0-next.0-changelog.md

File metadata and controls

4281 lines (3264 loc) · 141 KB

Release v1.24.0-next.0

Minor Changes

  • 4a3d434: BREAKING: For users that have migrated to the new backend system, incoming requests will now be rejected if they are not properly authenticated (e.g. with a Backstage bearer token or a backend token). Please see the Auth Service Migration tutorial for more information on how to circumvent this behavior in the short term and how to properly leverage it in the longer term.

    Added service factories for the new auth, httpAuth, and userInfo services that were created as part of BEP-0003.

Patch Changes

Minor Changes

  • 293c835: Add support for Service Tokens to Cloudflare Access auth provider
  • 492fe83: BREAKING: The CatalogIdentityClient constructor now also requires the discovery service to be forwarded from the plugin environment. This is part of the migration to support the new auth services, which has also been done for the createRouter function.

Patch Changes

Minor Changes

  • 1bedb23: Adds a new guest provider that maps guest users to actual tokens. This also shifts the default guest login to user:development/guest to reduce overlap with your production/real data. To change that (or set it back to the old default, use the new auth.providers.guest.userEntityRef config key) like so,

    auth:
      providers:
        guest:
          userEntityRef: user:default/guest

    This also adds a new property to control the ownership entity refs,

    auth:
      providers:
        guest:
          ownershipEntityRefs:
            - guests
            - development/custom

Patch Changes

Minor Changes

  • 9fdb86a: Ability to fetch the README file from a different Azure DevOps path.

    Defaults to the current, Azure DevOps default behaviour (README.md in the root of the git repo); to use a different path, add the annotation dev.azure.com/readme-path

    Example:

    dev.azure.com/readme-path: /my-path/README.md
  • a9e7bd6: BREAKING The AzureDevOpsClient no longer requires identityAPi but now requires fetchApi.

    Updated to use fetchApi as per ADR013

Patch Changes

Minor Changes

  • 9fdb86a: Ability to fetch the README file from a different Azure DevOps path.

    Defaults to the current, Azure DevOps default behaviour (README.md in the root of the git repo); to use a different path, add the annotation dev.azure.com/readme-path

    Example:

    dev.azure.com/readme-path: /my-path/README.md

Patch Changes

Minor Changes

  • 9fdb86a: Ability to fetch the README file from a different Azure DevOps path.

    Defaults to the current, Azure DevOps default behaviour (README.md in the root of the git repo); to use a different path, add the annotation dev.azure.com/readme-path

    Example:

    dev.azure.com/readme-path: /my-path/README.md

Minor Changes

  • 6b802a2: BREAKING: The createRouter method now requires the discovery service to be forwarded from the plugin environment. This is part of the migration to support new auth services.

Patch Changes

Minor Changes

  • df12231: Allow setting EntityDataParser using CatalogModelExtensionPoint
  • 15ba00f: Migrated to support new auth services. The CatalogBuilder.create method now accepts a discovery option, which is recommended to forward from the plugin environment, as it will otherwise fall back to use the HostDiscovery implementation.

Patch Changes

Minor Changes

  • 9e527c9: BREAKING CHANGE: Migrates the BitbucketCloudEntityProvider to use the EventsService; fix new backend system support.

    BitbucketCloudEntityProvider.fromConfig accepts events: EventsService as optional argument to its options. With provided events, the event-based updates/refresh will be available. However, the EventSubscriber interface was removed including its supportsEventTopics() and onEvent(params).

    The event subscription happens on connect(connection) if the events is available.

    Migration:

      const bitbucketCloudProvider = BitbucketCloudEntityProvider.fromConfig(
        env.config,
        {
          catalogApi: new CatalogClient({ discoveryApi: env.discovery }),
    +     events: env.events,
          logger: env.logger,
          scheduler: env.scheduler,
          tokenManager: env.tokenManager,
        },
      );
    - env.eventBroker.subscribe(bitbucketCloudProvider);

    New Backend System:

    Before this change, using this module with the new backend system was broken. Now, you can add the catalog module for Bitbucket Cloud incl. event support backend. Event support will always be enabled. However, no updates/refresh will happen without receiving events.

    backend.add(
      import('@backstage/plugin-catalog-backend-module-bitbucket-cloud/alpha'),
    );

Patch Changes

Minor Changes

  • df12231: Allow setting EntityDataParser using CatalogModelExtensionPoint

Patch Changes

Minor Changes

  • 4dc5b48: BREAKING: The createRouter method now requires the discovery service to be forwarded from the plugin environment. This is part of the migration to support new auth services.

Patch Changes

Minor Changes

  • c4bd794: BREAKING CHANGE: Migrate HttpPostIngressEventPublisher and eventsPlugin to use EventsService.

    Uses the EventsService instead of EventBroker at HttpPostIngressEventPublisher, dropping the use of EventPublisher including setEventBroker(..).

    Now, HttpPostIngressEventPublisher.fromConfig requires events: EventsService as option.

      const http = HttpPostIngressEventPublisher.fromConfig({
        config: env.config,
    +   events: env.events,
        logger: env.logger,
      });
      http.bind(eventsRouter);
    
      // e.g. at packages/backend/src/plugins/events.ts
    - await new EventsBackend(env.logger)
    -   .setEventBroker(env.eventBroker)
    -   .addPublishers(http)
    -   .start();
    
      // or for other kinds of setups
    - await Promise.all(http.map(publisher => publisher.setEventBroker(eventBroker)));

    eventsPlugin uses the eventsServiceRef as dependency. Unsupported (and deprecated) extension point methods will throw an error to prevent unintended behavior.

    import { eventsServiceRef } from '@backstage/plugin-events-node';

Patch Changes

  • 56969b6: Add new EventsService as well as eventsServiceRef for the new backend system.

    Summary:

    • new: EventsService, eventsServiceRef, TestEventsService
    • deprecated: EventBroker, EventPublisher, EventSubscriber, DefaultEventBroker, EventsBackend, most parts of EventsExtensionPoint (alpha), TestEventBroker, TestEventPublisher, TestEventSubscriber

    Add the eventsServiceRef as dependency to your backend plugins or backend plugin modules.

    Details:

    The previous implementation using the EventsExtensionPoint was added in the early stages of the new backend system and does not respect the plugin isolation. This made it not compatible anymore with the new backend system.

    Additionally, the previous interfaces had some room for simplification, supporting less exposure of internal concerns as well.

    Hereby, this change adds a new EventsService interface as replacement for the now deprecated EventBroker. The new interface does not require any EventPublisher or EventSubscriber interfaces anymore. Instead, it is expected that the EventsService gets passed into publishers and subscribers, and used internally. There is no need to expose anything of that at their own interfaces.

    Most parts of EventsExtensionPoint (alpha) are deprecated as well and were not usable (by other plugins or their modules) anyway.

    The DefaultEventBroker implementation is deprecated and wraps the new DefaultEventsService implementation. Optionally, an instance can be passed as argument to allow mixed setups to operate alongside.

  • Updated dependencies

Minor Changes

  • 132d672: BREAKING CHANGE: Migrate AwsSqsConsumingEventPublisher and its backend module to use EventsService.

    Uses the EventsService instead of EventBroker at AwsSqsConsumingEventPublisher, dropping the use of EventPublisher including setEventBroker(..).

    Now, AwsSqsConsumingEventPublisher.fromConfig requires events: EventsService as option.

      const sqs = AwsSqsConsumingEventPublisher.fromConfig({
        config: env.config,
    +   events: env.events,
        logger: env.logger,
        scheduler: env.scheduler,
      });
    + await Promise.all(sqs.map(publisher => publisher.start()));
    
      // e.g. at packages/backend/src/plugins/events.ts
    - await new EventsBackend(env.logger)
    -   .setEventBroker(env.eventBroker)
    -   .addPublishers(sqs)
    -   .start();
    
      // or for other kinds of setups
    - await Promise.all(sqs.map(publisher => publisher.setEventBroker(eventBroker)));

    eventsModuleAwsSqsConsumingEventPublisher uses the eventsServiceRef as dependency, instead of eventsExtensionPoint.

Patch Changes

Minor Changes

  • eff3ca9: BREAKING CHANGE: Migrate EventRouter implementations from EventBroker to EventsService.

    EventRouter uses the new EventsService instead of the EventBroker now, causing a breaking change to its signature.

    All of its extensions and implementations got adjusted accordingly. (SubTopicEventRouter, AzureDevOpsEventRouter, BitbucketCloudEventRouter, GerritEventRouter, GithubEventRouter, GitlabEventRouter)

    Required adjustments were made to all backend modules for the new backend system, now also making use of the eventsServiceRef instead of the eventsExtensionPoint.

    Migration:

    Example for implementations of SubTopicEventRouter:

      import {
        EventParams,
    +   EventsService,
        SubTopicEventRouter,
      } from '@backstage/plugin-events-node';
    
      export class GithubEventRouter extends SubTopicEventRouter {
    -   constructor() {
    -     super('github');
    +   constructor(options: { events: EventsService }) {
    +     super({
    +       events: options.events,
    +       topic: 'github',
    +     });
        }
    
    +   protected getSubscriberId(): string {
    +     return 'GithubEventRouter';
    +   }
    +
        // ...
      }

    Example for a direct extension of EventRouter:

      class MyEventRouter extends EventRouter {
    -   constructor(/* ... */) {
    +   constructor(options: {
    +     events: EventsService;
    +     // ...
    +   }) {
    -     super();
          // ...
    +     super({
    +       events: options.events,
    +       topics: topics,
    +     });
        }
    +
    +   protected getSubscriberId(): string {
    +     return 'MyEventRouter';
    +   }
    -
    -   supportsEventTopics(): string[] {
    -     return this.topics;
    -   }
      }

Patch Changes

Minor Changes

  • eff3ca9: BREAKING CHANGE: Migrate EventRouter implementations from EventBroker to EventsService.

    EventRouter uses the new EventsService instead of the EventBroker now, causing a breaking change to its signature.

    All of its extensions and implementations got adjusted accordingly. (SubTopicEventRouter, AzureDevOpsEventRouter, BitbucketCloudEventRouter, GerritEventRouter, GithubEventRouter, GitlabEventRouter)

    Required adjustments were made to all backend modules for the new backend system, now also making use of the eventsServiceRef instead of the eventsExtensionPoint.

    Migration:

    Example for implementations of SubTopicEventRouter:

      import {
        EventParams,
    +   EventsService,
        SubTopicEventRouter,
      } from '@backstage/plugin-events-node';
    
      export class GithubEventRouter extends SubTopicEventRouter {
    -   constructor() {
    -     super('github');
    +   constructor(options: { events: EventsService }) {
    +     super({
    +       events: options.events,
    +       topic: 'github',
    +     });
        }
    
    +   protected getSubscriberId(): string {
    +     return 'GithubEventRouter';
    +   }
    +
        // ...
      }

    Example for a direct extension of EventRouter:

      class MyEventRouter extends EventRouter {
    -   constructor(/* ... */) {
    +   constructor(options: {
    +     events: EventsService;
    +     // ...
    +   }) {
    -     super();
          // ...
    +     super({
    +       events: options.events,
    +       topics: topics,
    +     });
        }
    +
    +   protected getSubscriberId(): string {
    +     return 'MyEventRouter';
    +   }
    -
    -   supportsEventTopics(): string[] {
    -     return this.topics;
    -   }
      }

Patch Changes

Minor Changes

  • eff3ca9: BREAKING CHANGE: Migrate EventRouter implementations from EventBroker to EventsService.

    EventRouter uses the new EventsService instead of the EventBroker now, causing a breaking change to its signature.

    All of its extensions and implementations got adjusted accordingly. (SubTopicEventRouter, AzureDevOpsEventRouter, BitbucketCloudEventRouter, GerritEventRouter, GithubEventRouter, GitlabEventRouter)

    Required adjustments were made to all backend modules for the new backend system, now also making use of the eventsServiceRef instead of the eventsExtensionPoint.

    Migration:

    Example for implementations of SubTopicEventRouter:

      import {
        EventParams,
    +   EventsService,
        SubTopicEventRouter,
      } from '@backstage/plugin-events-node';
    
      export class GithubEventRouter extends SubTopicEventRouter {
    -   constructor() {
    -     super('github');
    +   constructor(options: { events: EventsService }) {
    +     super({
    +       events: options.events,
    +       topic: 'github',
    +     });
        }
    
    +   protected getSubscriberId(): string {
    +     return 'GithubEventRouter';
    +   }
    +
        // ...
      }

    Example for a direct extension of EventRouter:

      class MyEventRouter extends EventRouter {
    -   constructor(/* ... */) {
    +   constructor(options: {
    +     events: EventsService;
    +     // ...
    +   }) {
    -     super();
          // ...
    +     super({
    +       events: options.events,
    +       topics: topics,
    +     });
        }
    +
    +   protected getSubscriberId(): string {
    +     return 'MyEventRouter';
    +   }
    -
    -   supportsEventTopics(): string[] {
    -     return this.topics;
    -   }
      }

Patch Changes

Minor Changes

  • eff3ca9: BREAKING CHANGE: Migrate EventRouter implementations from EventBroker to EventsService.

    EventRouter uses the new EventsService instead of the EventBroker now, causing a breaking change to its signature.

    All of its extensions and implementations got adjusted accordingly. (SubTopicEventRouter, AzureDevOpsEventRouter, BitbucketCloudEventRouter, GerritEventRouter, GithubEventRouter, GitlabEventRouter)

    Required adjustments were made to all backend modules for the new backend system, now also making use of the eventsServiceRef instead of the eventsExtensionPoint.

    Migration:

    Example for implementations of SubTopicEventRouter:

      import {
        EventParams,
    +   EventsService,
        SubTopicEventRouter,
      } from '@backstage/plugin-events-node';
    
      export class GithubEventRouter extends SubTopicEventRouter {
    -   constructor() {
    -     super('github');
    +   constructor(options: { events: EventsService }) {
    +     super({
    +       events: options.events,
    +       topic: 'github',
    +     });
        }
    
    +   protected getSubscriberId(): string {
    +     return 'GithubEventRouter';
    +   }
    +
        // ...
      }

    Example for a direct extension of EventRouter:

      class MyEventRouter extends EventRouter {
    -   constructor(/* ... */) {
    +   constructor(options: {
    +     events: EventsService;
    +     // ...
    +   }) {
    -     super();
          // ...
    +     super({
    +       events: options.events,
    +       topics: topics,
    +     });
        }
    +
    +   protected getSubscriberId(): string {
    +     return 'MyEventRouter';
    +   }
    -
    -   supportsEventTopics(): string[] {
    -     return this.topics;
    -   }
      }

Patch Changes

Minor Changes

  • eff3ca9: BREAKING CHANGE: Migrate EventRouter implementations from EventBroker to EventsService.

    EventRouter uses the new EventsService instead of the EventBroker now, causing a breaking change to its signature.

    All of its extensions and implementations got adjusted accordingly. (SubTopicEventRouter, AzureDevOpsEventRouter, BitbucketCloudEventRouter, GerritEventRouter, GithubEventRouter, GitlabEventRouter)

    Required adjustments were made to all backend modules for the new backend system, now also making use of the eventsServiceRef instead of the eventsExtensionPoint.

    Migration:

    Example for implementations of SubTopicEventRouter:

      import {
        EventParams,
    +   EventsService,
        SubTopicEventRouter,
      } from '@backstage/plugin-events-node';
    
      export class GithubEventRouter extends SubTopicEventRouter {
    -   constructor() {
    -     super('github');
    +   constructor(options: { events: EventsService }) {
    +     super({
    +       events: options.events,
    +       topic: 'github',
    +     });
        }
    
    +   protected getSubscriberId(): string {
    +     return 'GithubEventRouter';
    +   }
    +
        // ...
      }

    Example for a direct extension of EventRouter:

      class MyEventRouter extends EventRouter {
    -   constructor(/* ... */) {
    +   constructor(options: {
    +     events: EventsService;
    +     // ...
    +   }) {
    -     super();
          // ...
    +     super({
    +       events: options.events,
    +       topics: topics,
    +     });
        }
    +
    +   protected getSubscriberId(): string {
    +     return 'MyEventRouter';
    +   }
    -
    -   supportsEventTopics(): string[] {
    -     return this.topics;
    -   }
      }

Patch Changes

Minor Changes

  • eff3ca9: BREAKING CHANGE: Migrate EventRouter implementations from EventBroker to EventsService.

    EventRouter uses the new EventsService instead of the EventBroker now, causing a breaking change to its signature.

    All of its extensions and implementations got adjusted accordingly. (SubTopicEventRouter, AzureDevOpsEventRouter, BitbucketCloudEventRouter, GerritEventRouter, GithubEventRouter, GitlabEventRouter)

    Required adjustments were made to all backend modules for the new backend system, now also making use of the eventsServiceRef instead of the eventsExtensionPoint.

    Migration:

    Example for implementations of SubTopicEventRouter:

      import {
        EventParams,
    +   EventsService,
        SubTopicEventRouter,
      } from '@backstage/plugin-events-node';
    
      export class GithubEventRouter extends SubTopicEventRouter {
    -   constructor() {
    -     super('github');
    +   constructor(options: { events: EventsService }) {
    +     super({
    +       events: options.events,
    +       topic: 'github',
    +     });
        }
    
    +   protected getSubscriberId(): string {
    +     return 'GithubEventRouter';
    +   }
    +
        // ...
      }

    Example for a direct extension of EventRouter:

      class MyEventRouter extends EventRouter {
    -   constructor(/* ... */) {
    +   constructor(options: {
    +     events: EventsService;
    +     // ...
    +   }) {
    -     super();
          // ...
    +     super({
    +       events: options.events,
    +       topics: topics,
    +     });
        }
    +
    +   protected getSubscriberId(): string {
    +     return 'MyEventRouter';
    +   }
    -
    -   supportsEventTopics(): string[] {
    -     return this.topics;
    -   }
      }

Patch Changes

  • 56969b6: Add new EventsService as well as eventsServiceRef for the new backend system.

    Summary:

    • new: EventsService, eventsServiceRef, TestEventsService
    • deprecated: EventBroker, EventPublisher, EventSubscriber, DefaultEventBroker, EventsBackend, most parts of EventsExtensionPoint (alpha), TestEventBroker, TestEventPublisher, TestEventSubscriber

    Add the eventsServiceRef as dependency to your backend plugins or backend plugin modules.

    Details:

    The previous implementation using the EventsExtensionPoint was added in the early stages of the new backend system and does not respect the plugin isolation. This made it not compatible anymore with the new backend system.

    Additionally, the previous interfaces had some room for simplification, supporting less exposure of internal concerns as well.

    Hereby, this change adds a new EventsService interface as replacement for the now deprecated EventBroker. The new interface does not require any EventPublisher or EventSubscriber interfaces anymore. Instead, it is expected that the EventsService gets passed into publishers and subscribers, and used internally. There is no need to expose anything of that at their own interfaces.

    Most parts of EventsExtensionPoint (alpha) are deprecated as well and were not usable (by other plugins or their modules) anyway.

    The DefaultEventBroker implementation is deprecated and wraps the new DefaultEventsService implementation. Optionally, an instance can be passed as argument to allow mixed setups to operate alongside.

  • Updated dependencies

Minor Changes

  • 55191cc: BREAKING: Both createRouter and DefaultJenkinsInfoProvider.fromConfig now require the discovery service to be forwarded from the plugin environment. This is part of the migration to support new auth services.

    The JenkinsInfoProvider interface has been updated to receive credentials of the type BackstageCredentials rather than a token.

Patch Changes

Minor Changes

  • e1e540c: BREAKING: The KubernetesBuilder.createBuilder method now requires the discovery service to be forwarded from the plugin environment. This is part of the migration to support new auth services.

Patch Changes

Minor Changes

  • 758f2a4: The Notifications frontend has been redesigned towards list view with condensed row details. The 'done' attribute has been removed to keep the Notifications aligned with the idea of a messaging system instead of a task manager.

Patch Changes

Minor Changes

  • 758f2a4: The Notifications frontend has been redesigned towards list view with condensed row details. The 'done' attribute has been removed to keep the Notifications aligned with the idea of a messaging system instead of a task manager.

Patch Changes

Minor Changes

  • 84af361: Migrated to using the new auth services.

Patch Changes

Minor Changes

  • c6b132e: Introducing checkpoints for scaffolder task action idempotency

Patch Changes

Minor Changes

  • f44589d: Introduced createMockActionContext to unify the way of creating scaffolder mock context.

    It will help to maintain tests in a long run during structural changes of action context.

Patch Changes

Minor Changes

  • d621468: BREAKING: The FactRetrieverContext type now contains an additional auth field.

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 4a3d434: Added the new auth, httpAuth, and userInfo services that were created as part of BEP-0003 to the coreServices.

    At the same time, the httpRouter service gained a new addAuthPolicy method that lets your plugin declare exemptions to the default auth policy - for example if you want to allow unauthenticated or cookie-based access to some subset of your feature routes.

    If you have migrated to the new backend system, please see the Auth Service Migration tutorial for more information on how to move toward using these services.

  • 0502d82: Updated the PermissionsService methods to accept BackstageCredentials through options.

  • Updated dependencies

Patch Changes

Patch Changes

  • 4a3d434: Added support for the new auth and httpAuth services that were created as part of BEP-0003. These services will be present by default in test apps, and you can access mocked versions of their features under mockServices.auth and mockServices.httpAuth if you want to inspect or replace their behaviors.

    There is also a new mockCredentials that you can use for acquiring mocks of the various types of credentials that are used in the new system.

  • 9802004: Added mockServices.userInfo, which now also automatically is made available in test backends.

  • fd61d39: Updated dependency testcontainers to ^10.0.0.

  • ff40ada: Updated dependency mysql2 to ^3.0.0.

  • 0fb419b: Updated dependency uuid to ^9.0.0. Updated dependency @types/uuid to ^9.0.0.

  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • ff33ee2: Removed hardcoded font-family on select input
  • ff7e126: Support i18n for core components
  • 7854120: Create a component abstraction to consume system icons.
  • ce73c3b: Removed the inline color from select icon to allow it to be colored via a theme
  • a8f7904: SignInPage's 'guest' provider now supports the @backstage/plugin-auth-backend-module-guest-provider package to generate tokens. It will continue to use the old frontend-only auth as a fallback.
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 2636075: Fixed an issue that was causing ResponseError not to report the HTTP status from the provided response.
  • Updated dependencies

Patch Changes

  • 999224f: Bump dependency minimatch to v9

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 6f4d2a0: Exported defaultTypography to make adjusting these values in a custom theme easier

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 2af5354: Bump dependency jose to v5
  • e77d7a9: Internal refactor to avoid deprecated method.
  • b1b012d: Fix issue with providerInfo not being set properly for some proxy providers, by making providerInfo an explicit optional return from authenticate
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • b4fc6e3: Deprecated the getBearerTokenFromAuthorizationHeader function, which is being replaced by the new HttpAuthService.
  • 2af5354: Bump dependency jose to v5
  • 0fb419b: Updated dependency uuid to ^9.0.0. Updated dependency @types/uuid to ^9.0.0.
  • b1b012d: Fix issue with providerInfo not being set properly for some proxy providers, by making providerInfo an explicit optional return from authenticate
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

@backstage/plugin-catalog-backend-module-incremental-ingestion@0.4.17-next.0

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

@backstage/plugin-catalog-backend-module-scaffolder-entity-model@0.1.10-next.0

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 56969b6: Add new EventsService as well as eventsServiceRef for the new backend system.

    Summary:

    • new: EventsService, eventsServiceRef, TestEventsService
    • deprecated: EventBroker, EventPublisher, EventSubscriber, DefaultEventBroker, EventsBackend, most parts of EventsExtensionPoint (alpha), TestEventBroker, TestEventPublisher, TestEventSubscriber

    Add the eventsServiceRef as dependency to your backend plugins or backend plugin modules.

    Details:

    The previous implementation using the EventsExtensionPoint was added in the early stages of the new backend system and does not respect the plugin isolation. This made it not compatible anymore with the new backend system.

    Additionally, the previous interfaces had some room for simplification, supporting less exposure of internal concerns as well.

    Hereby, this change adds a new EventsService interface as replacement for the now deprecated EventBroker. The new interface does not require any EventPublisher or EventSubscriber interfaces anymore. Instead, it is expected that the EventsService gets passed into publishers and subscribers, and used internally. There is no need to expose anything of that at their own interfaces.

    Most parts of EventsExtensionPoint (alpha) are deprecated as well and were not usable (by other plugins or their modules) anyway.

    The DefaultEventBroker implementation is deprecated and wraps the new DefaultEventsService implementation. Optionally, an instance can be passed as argument to allow mixed setups to operate alongside.

  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 0cecb09: Updated dependency @rjsf/utils to 5.17.1. Updated dependency @rjsf/core to 5.17.1. Updated dependency @rjsf/material-ui to 5.17.1. Updated dependency @rjsf/validator-ajv8 to 5.17.1.
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 758f2a4: The Notifications frontend has been redesigned towards list view with condensed row details. The 'done' attribute has been removed to keep the Notifications aligned with the idea of a messaging system instead of a task manager.

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 0502d82: The token option of the PermissionEvaluator methods is now deprecated. The options that only apply to backend implementations have been moved to PermissionsService from @backstage/backend-plugin-api instead.
  • 0fb419b: Updated dependency uuid to ^9.0.0. Updated dependency @types/uuid to ^9.0.0.
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

@backstage/plugin-scaffolder-backend-module-confluence-to-markdown@0.2.14-next.0

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

@backstage/plugin-search-backend-module-stack-overflow-collator@0.1.6-next.0

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 744c0cb: Deprecate QueryTranslator, QueryRequestOptions and SearchEngine in favor of the types exported from @backstage/plugin-search-backend-node.
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • Updated dependencies
    • @backstage/plugin-search-backend-module-stack-overflow-collator@0.1.6-next.0

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes