Skip to content

Latest commit

 

History

History
2127 lines (1590 loc) · 62.5 KB

v1.7.0-next.2-changelog.md

File metadata and controls

2127 lines (1590 loc) · 62.5 KB

Release v1.7.0-next.2

Minor Changes

  • 8554533546: BREAKING The bazaar-backend createRouter now requires that the identityApi is passed to the router.

    These changes are required to packages/backend/src/plugins/bazaar.ts

    The user entity ref is now added to the members table and is taken from the requesting user using the identityApi.

    import { PluginEnvironment } from '../types';
    import { createRouter } from '@backstage/plugin-bazaar-backend';
    import { Router } from 'express';
    
    export default async function createPlugin(
      env: PluginEnvironment,
    ): Promise<Router> {
      return await createRouter({
        logger: env.logger,
        config: env.config,
        database: env.database,
    +   identity: env.identity,
      });
    }

Patch Changes

Minor Changes

  • b2e6cb6acf: Added a new method addLocationAnalyzers to the CatalogBuilder. With this you can add location analyzers to your catalog. These analyzers will be used by the /analyze-location endpoint to decide if the provided URL contains any catalog-info.yaml files already or not.

    Moved the following types from this package to @backstage/plugin-catalog-backend.

    • AnalyzeLocationResponse
    • AnalyzeLocationRequest
    • AnalyzeLocationExistingEntity
    • AnalyzeLocationGenerateEntity
    • AnalyzeLocationEntityField
  • eb25f7e12d: The exported permission rules and the API of createCatalogConditionalDecision have changed to reflect the breaking changes made to the PermissionRule type. Note that all involved types are exported from @backstage/plugin-catalog-backend/alpha

Patch Changes

Minor Changes

  • b2e6cb6acf: Breaking Moved the code search for the existing catalog-info.yaml files to the backend from the frontend. It means it will use the configured GitHub integration's credentials.

    Add the following to your CatalogBuilder to have the repo URL ingestion working again.

    // catalog.ts
    import { GitHubLocationAnalyzer } from '@backstage/plugin-catalog-backend-module-github';
    ...
      builder.addLocationAnalyzers(
        new GitHubLocationAnalyzer({
          discovery: env.discovery,
          config: env.config,
        }),
      );
    ...

Patch Changes

Minor Changes

  • 404366c853: Deprecated the LocationSpec type. It got moved from this package to the @backstage/plugin-catalog-common so make sure imports are updated.

Patch Changes

Minor Changes

  • 46b4a72cee: BREAKING: When defining permission rules, it's now necessary to provide a ZodSchema that specifies the parameters the rule expects. This has been added to help better describe the parameters in the response of the metadata endpoint and to validate the parameters before a rule is executed.

    To help with this, we have also made a change to the API of permission rules. Before, the permission rules toQuery and apply signature expected parameters to be separate arguments, like so...

    createPermissionRule({
      apply: (resource, foo, bar) => true,
      toQuery: (foo, bar) => {},
    });

    The API has now changed to expect the parameters as a single object

    createPermissionRule({
      paramSchema: z.object({
        foo: z.string().describe('Foo value to match'),
        bar: z.string().describe('Bar value to match'),
      }),
      apply: (resource, { foo, bar }) => true,
      toQuery: ({ foo, bar }) => {},
    });

    One final change made is to limit the possible values for a parameter to primitives and arrays of primitives.

Patch Changes

Minor Changes

  • 46b4a72cee: BREAKING: When defining permission rules, it's now necessary to provide a ZodSchema that specifies the parameters the rule expects. This has been added to help better describe the parameters in the response of the metadata endpoint and to validate the parameters before a rule is executed.

    To help with this, we have also made a change to the API of permission rules. Before, the permission rules toQuery and apply signature expected parameters to be separate arguments, like so...

    createPermissionRule({
      apply: (resource, foo, bar) => true,
      toQuery: (foo, bar) => {},
    });

    The API has now changed to expect the parameters as a single object

    createPermissionRule({
      paramSchema: z.object({
        foo: z.string().describe('Foo value to match'),
        bar: z.string().describe('Bar value to match'),
      }),
      apply: (resource, { foo, bar }) => true,
      toQuery: ({ foo, bar }) => {},
    });

    One final change made is to limit the possible values for a parameter to primitives and arrays of primitives.

Patch Changes

Minor Changes

  • eb25f7e12d: BREAKING The exported permission rules have changed to reflect the breaking changes made to the PermissionRule type.

    For example, the playlistConditions.isOwner API has changed from:

    playlistConditions.isOwner(['user:default/me', 'group:default/owner']);

    to:

    playlistConditions.isOwner({
      owners: ['user:default/me', 'group:default/owner'],
    });

Patch Changes

Minor Changes

  • 17ff77154c: Update the github:publish action to allow passing whether pull requests must be up to date with the default branch before merging.
  • a8e9848479: Added optional sourcePath parameter to publish:gitlab:merge-request action, targetPath is now optional and falls back to current workspace path.

Patch Changes

Minor Changes

  • 7ced1b4076: Add optional catalogClient argument to createRoute parameters

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

  • 01dff06be4: Leverage cache mounts in Dockerfile during yarn install ... and apt-get ... commands to speed up repeated builds.
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 2d3a5f09ab: Use response.json rather than response.send where appropriate, as outlined in SECURITY.md
  • 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

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 823acaa88b: Moved the following types from @backstage/plugin-catalog-backend to this package.

    • AnalyzeLocationResponse
    • AnalyzeLocationRequest
    • AnalyzeLocationExistingEntity
    • AnalyzeLocationGenerateEntity
    • AnalyzeLocationEntityField
  • 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

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

  • 2d3a5f09ab: Use response.json rather than response.send where appropriate, as outlined in SECURITY.md
  • Updated dependencies

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

  • 2d3a5f09ab: Use response.json rather than response.send where appropriate, as outlined in SECURITY.md
  • 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

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