Skip to content

Releases: backstage/backstage

v0.45.0

02 Sep 12:23
174a8b5

Choose a tag to compare

@backstage/core-components@0.4.0

Minor Changes

  • 3ed78fc: Changed the titleComponent prop on ContentHeader to accept ReactNode instead of a React ComponentType. Usages of this prop should be converted from passing a component to passing in the rendered element:

    -<ContentHeader titleComponent={MyComponent}>
    +<ContentHeader titleComponent={<MyComponent />}>

Patch Changes

  • e0a6aea: Bumped react-hook-form to ^7.12.2

@backstage/search-common@0.2.0

Minor Changes

  • a13f21c: Implement optional pageCursor based paging in search.

    To use paging in your app, add a <SearchResultPager /> to your
    SearchPage.tsx.

@backstage/techdocs-common@0.10.0

Minor Changes

  • 8b0f6f8: Set the correct edit_uri or repo_url for documentation pages that are hosted on GitHub and GitLab.

    The constructor of the TechDocsGenerator changed.
    Prefer the use of TechdocsGenerator.fromConfig(…) instead:

    - const techdocsGenerator = new TechdocsGenerator({
    + const techdocsGenerator = TechdocsGenerator.fromConfig(config, {
        logger,
        containerRunner,
    -   config,
      });

Patch Changes

  • 30ed662: Adding in-context search to TechDocs Reader component. Using existing search-backend to query for indexed search results scoped into a specific entity's techdocs. Needs TechDocsCollator enabled on the backend to work.

    Adding extra information to indexed tech docs documents for search.

  • 3624616: "Local" (out-of-the-box) publisher explicitly follows lower-case entity triplet
    logic.

  • 67ba7e0: Only write the updated mkdocs.yml file if the content was updated.

    This keeps local files unchanged if the dir annotation is used in combination with the file location.

  • 8eab6be: Force using posix path for cloud storage

  • Updated dependencies

    • @backstage/integration@0.6.3
    • @backstage/search-common@0.2.0
    • @backstage/catalog-model@0.9.1
    • @backstage/backend-common@0.9.1

@backstage/plugin-search-backend-module-pg@0.2.0

Minor Changes

  • a13f21c: Implement optional pageCursor based paging in search.

    To use paging in your app, add a <SearchResultPager /> to your
    SearchPage.tsx.

Patch Changes

  • Updated dependencies
    • @backstage/search-common@0.2.0
    • @backstage/plugin-search-backend-node@0.4.2
    • @backstage/backend-common@0.9.1

@backstage/backend-common@0.9.1

Patch Changes

  • 714a2a9: Export type that are needed to implement a new UrlReader
  • Updated dependencies
    • @backstage/integration@0.6.3

@backstage/catalog-model@0.9.1

Patch Changes

  • 13dc373: Add an optional metadata.title field to all entity kinds.

    This used to be available on only the Template kind, and we have decided that the metadata block should be the same for all kinds. A title can be useful especially in large and complex catalogs where users have a tough time navigating or discerning among the entities.

    It also carries some risk. You do not want to end up giving a title that collides with an actual name, which at best leads to confusion and at worst could be a liability. We do not perform any collision detection in the catalog. If you want to disallow this facility you may want to add a small processor that makes sure it's not set.

    At the time of writing this message, only the scaffolder actually makes use of this field for display purposes.

@backstage/cli@0.7.10

Patch Changes

  • 5e803ed: Added support for importing font files. Imports in CSS via url() are supported for the final frontend bundle, but not for packages that are built for publishing. Module imports of fonts files from TypeScript are supported everywhere.
  • b5118ff: Updated dependencies

@backstage/codemods@0.1.12

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.4.0
    • @backstage/core-app-api@0.1.11

@backstage/core-app-api@0.1.11

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.4.0

@backstage/create-app@0.3.39

Patch Changes

  • 2592463: Minor tweaks to the create-app template to match earlier documented changes

@backstage/dev-utils@0.2.8

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1
    • @backstage/core-app-api@0.1.11
    • @backstage/integration-react@0.1.8

@backstage/integration@0.6.3

Patch Changes

  • 5dca42b: Update to properly handle Azure DevOps Server download URL

@backstage/integration-react@0.1.8

Patch Changes

  • Updated dependencies
    • @backstage/integration@0.6.3
    • @backstage/core-components@0.4.0

@backstage/plugin-allure@0.1.1

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-api-docs@0.6.7

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/plugin-catalog@0.6.14
    • @backstage/catalog-model@0.9.1

@backstage/plugin-auth-backend@0.3.24

Patch Changes

  • 2a105f4: Add a warning log message that passport-saml will require a cert config parameter imminently.

    We intend to upgrade this package soon, past the point where we will start to strictly require the auth.saml.cert configuration parameter to be present. To avoid issues starting your auth backend, please

  • 31892ee: typo fix tenentId in Azure auth provider docs

  • e9b1e2a: Added signIn and authHandler resolver for oAuth2 provider

  • ca45b16: Export GitHub to allow use with Identity resolver

  • Updated dependencies

    • @backstage/catalog-model@0.9.1
    • @backstage/backend-common@0.9.1

@backstage/plugin-badges@0.2.8

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-bitrise@0.1.11

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-catalog@0.6.14

Patch Changes

  • 10db3ce: Update the AboutCard to properly support non-standard entity types and rework the defaults for the build-in kinds.

    This change also uses useElementFilter(...) instead of React.children.count(...) in AboutField to properly recognize whether children are available.

  • 7e5f14d: This change hides pagination counter of search tables and group members list when results fit in one page

  • 3ed78fc: Added the ability to switch entity kind on the catalog index page. This is a non-breaking change, but if you created a custom CatalogPage and wish to use this feature, make the modifications shown on #6895.

  • aaa1dd1: Use a Link for the edit button on the AboutCard instead of doing window.open(...)

  • Updated dependencies

    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/integration@0.6.3
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1
    • @backstage/integration-react@0.1.8

@backstage/plugin-catalog-backend@0.13.6

Patch Changes

  • 4d62dc1: GitHub discovery processor passes over repositories that do not have a default branch
  • 977b1df: Adds optional namespacing for users in the GitHub Multi Org Plugin
  • Updated dependencies
    • @backstage/integration@0.6.3
    • @backstage/search-common@0.2.0
    • @backstage/plugin-search-backend-node@0.4.2
    • @backstage/catalog-model@0.9.1
    • @backstage/backend-common@0.9.1

@backstage/plugin-catalog-import@0.5.20

Patch Changes

  • e0a6aea: Bumped react-hook-form to ^7.12.2
  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/integration@0.6.3
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1
    • @backstage/integration-react@0.1.8

@backstage/plugin-catalog-react@0.4.5

Patch Changes

  • 3ed78fc: Added a useEntityKinds hook to load a unique list of entity kinds from the catalog.
    Fixed a bug in EntityTypePicker where the component did not hide when no types were available in returned entities.
  • Updated dependencies
    • @backstage/integration@0.6.3
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1
    • @backstage/core-app-api@0.1.11

@backstage/plugin-circleci@0.2.22

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-cloudbuild@0.2.22

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-code-coverage@0.1.10

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-config-schema@0.1.6

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.4.0

@backstage/plugin-cost-insights@0.11.5

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.4.0

@backstage/plugin-explore@0.3.15

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.5
    • @backstage/core-components@0.4.0
    • @backstage/catalog-model@0.9.1

@backstage/plugin-firehydrant@0.1.2

Patch Ch...

Read more

v0.44.1

31 Aug 18:00
9b2c625

Choose a tag to compare

Hey, I just made a Pull Request!

Just created a new plugin for Allure reports as suggested in #6528
Screenshot 2021-08-23 at 6 32 47 PM
Screenshot 2021-08-23 at 6 31 52 PM

✔️ Checklist

  • A changeset describing the change and affected packages. (more info)
  • Added or updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)
  • All your commits have a Signed-off-by line in the message. (more info)

v0.44.0

26 Aug 12:31
e436edb

Choose a tag to compare

@backstage/backend-common@0.9.0

Minor Changes

  • a365f1f: The ZipArchiveResponse class now accepts an optional stripFirstDirectory parameter. Note that its default value is false, which leads to a breaking change in behaviour to previous versions of the class. If you use this class explicitly and want to retain the old behaviour, add a true parameter value to its constructor.

Patch Changes

  • Updated dependencies
    • @backstage/integration@0.6.2
    • @backstage/config@0.1.8

@backstage/techdocs-common@0.9.0

Minor Changes

  • 58452cd: OpenStack Swift Client changed with Trendyol's OpenStack Swift SDK.

    Migration from old OpenStack Swift Configuration

    Let's assume we have the old OpenStack Swift configuration here.

    techdocs:
      publisher:
        type: 'openStackSwift'
        openStackSwift:
          containerName: 'name-of-techdocs-storage-bucket'
          credentials:
            username: ${OPENSTACK_SWIFT_STORAGE_USERNAME}
            password: ${OPENSTACK_SWIFT_STORAGE_PASSWORD}
          authUrl: ${OPENSTACK_SWIFT_STORAGE_AUTH_URL}
          keystoneAuthVersion: ${OPENSTACK_SWIFT_STORAGE_AUTH_VERSION}
          domainId: ${OPENSTACK_SWIFT_STORAGE_DOMAIN_ID}
          domainName: ${OPENSTACK_SWIFT_STORAGE_DOMAIN_NAME}
          region: ${OPENSTACK_SWIFT_STORAGE_REGION}
    Step 1: Change the credential keys

    Since the new SDK uses Application Credentials to authenticate OpenStack, we
    need to change the keys credentials.username to credentials.id,
    credentials.password to credentials.secret and use Application Credential ID
    and secret here. For more detail about credentials look
    here.

    Step 2: Remove the unused keys

    Since the new SDK doesn't use the old way authentication, we don't need the keys
    openStackSwift.keystoneAuthVersion, openStackSwift.domainId,
    openStackSwift.domainName and openStackSwift.region. So you can remove them.

    Step 3: Add Swift URL

    The new SDK needs the OpenStack Swift connection URL for connecting the Swift.
    So you need to add a new key called openStackSwift.swiftUrl and give the
    OpenStack Swift url here. Example url should look like that:
    https://example.com:6780/swift/v1

    That's it!

    Your new configuration should look like that!

    techdocs:
      publisher:
        type: 'openStackSwift'
        openStackSwift:
          containerName: 'name-of-techdocs-storage-bucket'
          credentials:
            id: ${OPENSTACK_SWIFT_STORAGE_APPLICATION_CREDENTIALS_ID}
            secret: ${OPENSTACK_SWIFT_STORAGE_APPLICATION_CREDENTIALS_SECRET}
          authUrl: ${OPENSTACK_SWIFT_STORAGE_AUTH_URL}
          swiftUrl: ${OPENSTACK_SWIFT_STORAGE_SWIFT_URL}
  • c772d9a: TechDocs sites can now be accessed using paths containing entity triplets of
    any case (e.g. /docs/namespace/KIND/name or /docs/namespace/kind/name).

    If you do not use an external storage provider for serving TechDocs, this is a
    transparent change and no action is required from you.

    If you do use an external storage provider for serving TechDocs (one of* GCS,
    AWS S3, or Azure Blob Storage), you must run a migration command against your
    storage provider before updating.

    A migration guide is available here.

    • (*) We're seeking help from the community to bring OpenStack Swift support
      to feature parity with the above.

Patch Changes

  • Updated dependencies
    • @backstage/backend-common@0.9.0
    • @backstage/integration@0.6.2
    • @backstage/config@0.1.8

@backstage/plugin-techdocs@0.11.0

Minor Changes

  • c772d9a: TechDocs sites can now be accessed using paths containing entity triplets of
    any case (e.g. /docs/namespace/KIND/name or /docs/namespace/kind/name).

    If you do not use an external storage provider for serving TechDocs, this is a
    transparent change and no action is required from you.

    If you do use an external storage provider for serving TechDocs (one of* GCS,
    AWS S3, or Azure Blob Storage), you must run a migration command against your
    storage provider before updating.

    A migration guide is available here.

    • (*) We're seeking help from the community to bring OpenStack Swift support
      to feature parity with the above.
  • 787bc08: The TechDocs plugin has completed the migration to the Composability API. In
    order to update to this version, please ensure you've made all necessary
    changes to your App.tsx file as outlined in the create-app changelog.

Patch Changes

  • 90c68a2: Fix Techdocs feedback icon link for GitHub URLs
  • Updated dependencies
    • @backstage/plugin-catalog@0.6.13
    • @backstage/plugin-catalog-react@0.4.4
    • @backstage/core-components@0.3.3
    • @backstage/integration@0.6.2
    • @backstage/config@0.1.8

@backstage/plugin-techdocs-backend@0.10.0

Minor Changes

  • 58452cd: OpenStack Swift Client changed with Trendyol's OpenStack Swift SDK.

    Migration from old OpenStack Swift Configuration

    Let's assume we have the old OpenStack Swift configuration here.

    techdocs:
      publisher:
        type: 'openStackSwift'
        openStackSwift:
          containerName: 'name-of-techdocs-storage-bucket'
          credentials:
            username: ${OPENSTACK_SWIFT_STORAGE_USERNAME}
            password: ${OPENSTACK_SWIFT_STORAGE_PASSWORD}
          authUrl: ${OPENSTACK_SWIFT_STORAGE_AUTH_URL}
          keystoneAuthVersion: ${OPENSTACK_SWIFT_STORAGE_AUTH_VERSION}
          domainId: ${OPENSTACK_SWIFT_STORAGE_DOMAIN_ID}
          domainName: ${OPENSTACK_SWIFT_STORAGE_DOMAIN_NAME}
          region: ${OPENSTACK_SWIFT_STORAGE_REGION}
    Step 1: Change the credential keys

    Since the new SDK uses Application Credentials to authenticate OpenStack, we
    need to change the keys credentials.username to credentials.id,
    credentials.password to credentials.secret and use Application Credential ID
    and secret here. For more detail about credentials look
    here.

    Step 2: Remove the unused keys

    Since the new SDK doesn't use the old way authentication, we don't need the keys
    openStackSwift.keystoneAuthVersion, openStackSwift.domainId,
    openStackSwift.domainName and openStackSwift.region. So you can remove them.

    Step 3: Add Swift URL

    The new SDK needs the OpenStack Swift connection URL for connecting the Swift.
    So you need to add a new key called openStackSwift.swiftUrl and give the
    OpenStack Swift url here. Example url should look like that:
    https://example.com:6780/swift/v1

    That's it!

    Your new configuration should look like that!

    techdocs:
      publisher:
        type: 'openStackSwift'
        openStackSwift:
          containerName: 'name-of-techdocs-storage-bucket'
          credentials:
            id: ${OPENSTACK_SWIFT_STORAGE_APPLICATION_CREDENTIALS_ID}
            secret: ${OPENSTACK_SWIFT_STORAGE_APPLICATION_CREDENTIALS_SECRET}
          authUrl: ${OPENSTACK_SWIFT_STORAGE_AUTH_URL}
          swiftUrl: ${OPENSTACK_SWIFT_STORAGE_SWIFT_URL}
  • c772d9a: TechDocs sites can now be accessed using paths containing entity triplets of
    any case (e.g. /docs/namespace/KIND/name or /docs/namespace/kind/name).

    If you do not use an external storage provider for serving TechDocs, this is a
    transparent change and no action is required from you.

    If you do use an external storage provider for serving TechDocs (one of* GCS,
    AWS S3, or Azure Blob Storage), you must run a migration command against your
    storage provider before updating.

    A migration guide is available here.

    • (*) We're seeking help from the community to bring OpenStack Swift support
      to feature parity with the above.

Patch Changes

  • Updated dependencies
    • @backstage/backend-common@0.9.0
    • @backstage/integration@0.6.2
    • @backstage/config@0.1.8
    • @backstage/techdocs-common@0.9.0

@backstage/backend-test-utils@0.1.6

Patch Changes

  • Updated dependencies
    • @backstage/backend-common@0.9.0
    • @backstage/config@0.1.8

@backstage/codemods@0.1.11

Patch Changes

  • Updated dependencies
    • @backstage/core-app-api@0.1.10
    • @backstage/core-components@0.3.3

@backstage/config@0.1.8

Patch Changes

  • 47113f1: Only warn once per key when trying to read visibility-filtered values

@backstage/core-app-api@0.1.10

Patch Changes

  • cfcb486: Add system icons for the built-in entity types and use them in the entity list of the catalog-import plugin.

  • 392b36f: Added support for using authenticating via GitHub Apps in addition to GitHub OAuth Apps. It used to be possible to use G...

Read more

v0.43.0

20 Aug 10:38
95f4f66

Choose a tag to compare

@backstage/plugin-auth-backend@0.3.22

Patch Changes

  • 79d24a9: Fix an issue where the default app origin was not allowed to authenticate users.

@backstage/plugin-catalog-backend@0.13.4

Patch Changes

  • 7ab5516: Properly handle Date objects being returned for timestamps in the database driver

@backstage/plugin-scaffolder-backend@0.15.1

Patch Changes

  • d622cfa: GitHub branch protection option 'Require review from Code Owners' can be enabled by adding requireCodeOwnersReview: true in context input.

@backstage/create-app@0.3.37

v0.42.0

19 Aug 13:34
2f291df

Choose a tag to compare

@backstage/plugin-catalog-backend-module-ldap@0.3.0

Minor Changes

  • 54b441a: Introduce LdapOrgEntityProvider as an alternative to LdapOrgReaderProcessor. This also changes the LdapClient interface to require a logger.

Patch Changes

  • Updated dependencies
    • @backstage/plugin-catalog-backend@0.13.3
    • @backstage/config@0.1.7

@backstage/plugin-home@0.2.0

Minor Changes

  • 2b7d345: Create the Home plugin which exports some basic functionality that's used to compose a homepage. An example of a composed homepage is added to the example app.

    This change also introduces the createCardExtension which creates a lazy loaded card that is intended to be used for homepage components.

    Adoption of this homepage requires setup similar to what can be found in the example app.

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.2
    • @backstage/theme@0.2.10

@backstage/backend-common@0.8.10

Patch Changes

  • 8543d98: Add an optional info parameter to the readTree filter option with a size property.
  • 4d90926: Read responses in UrlReader#read() as array buffer instead of as text to allow reading non-text locations such as images.
  • 9b4604b: Add support for watching configuration by implementing the subscribe method in the configuration returned by loadBackendConfig.
  • b8cb120: Add AWS S3 URL Reader
  • Updated dependencies
    • @backstage/config@0.1.7
    • @backstage/config-loader@0.6.7
    • @backstage/integration@0.6.1

@backstage/cli@0.7.9

Patch Changes

  • f3bba3d: Remove debug logging
  • 8ea1e96: Fix file path handling in diff commands on Windows.
  • 2518aab: Compensate for error formatting mismatch between Webpack 5 and react-dev-utils
  • 1ac2961: Reintroduce Node.js shims that were removed in the Webpack 5 migration.
  • 8d07a8b: Add Buffer to ProvidePlugin since this is no longer provided in webpack@5
  • fe506a0: Remove Webpack deprecation message when running build.
  • 485438a: Fix backstage-cli backend:dev argument passing
  • Updated dependencies
    • @backstage/config@0.1.7
    • @backstage/config-loader@0.6.7

@backstage/codemods@0.1.10

Patch Changes

  • Updated dependencies
    • @backstage/core-app-api@0.1.9
    • @backstage/core-components@0.3.2

@backstage/config@0.1.7

Patch Changes

  • 90f2547: Extended the Config interface to have an optional subscribe method that can be used be notified of updates to the configuration.

@backstage/config-loader@0.6.7

Patch Changes

  • 0ade9d0: Include devDependencies and optionalDependencies in the detection of Backstage packages when collecting configuration schema.
  • 9b8cec0: Add support for config file watching through a new group of watch options to loadConfig.
  • Updated dependencies
    • @backstage/config@0.1.7

@backstage/core-app-api@0.1.9

Patch Changes

  • 72a31c2: Add support for additional app origins
  • Updated dependencies
    • @backstage/config@0.1.7
    • @backstage/core-components@0.3.2
    • @backstage/theme@0.2.10

@backstage/core-components@0.3.2

Patch Changes

  • a3f3cff: Change the default hover experience for the sidebar to be not jumpy & add visual separation between sidebar & Entity Page tabs for dark mode.
  • 6b1afe8: Add a configurable palette.bursts.gradient property to the Backstage theme, to support customizing the gradients in the ItemCard header.
  • Updated dependencies
    • @backstage/config@0.1.7
    • @backstage/theme@0.2.10

@backstage/dev-utils@0.2.7

Patch Changes

  • be2cd47: Fixed busy refresh loop that happened when registering a page at /.
  • Updated dependencies
    • @backstage/core-app-api@0.1.9
    • @backstage/plugin-catalog-react@0.4.3
    • @backstage/core-components@0.3.2
    • @backstage/theme@0.2.10

@backstage/integration@0.6.1

Patch Changes

  • b8cb120: Add AWS S3 URL Reader
  • Updated dependencies
    • @backstage/config@0.1.7

@backstage/theme@0.2.10

Patch Changes

  • 6b1afe8: Add a configurable palette.bursts.gradient property to the Backstage theme, to support customizing the gradients in the ItemCard header.

@backstage/plugin-auth-backend@0.3.21

Patch Changes

  • 72a31c2: Add support for additional app origins
  • Updated dependencies
    • @backstage/backend-common@0.8.10
    • @backstage/config@0.1.7

@backstage/plugin-catalog@0.6.12

Patch Changes

  • fa1e003: Show a Not Found message when navigating to a nonexistent entity
  • 2105d60: Migrate and export UnregisterEntityDialog component from catalog-react package
  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.3
    • @backstage/core-components@0.3.2
    • @backstage/integration@0.6.1
    • @backstage/theme@0.2.10

@backstage/plugin-catalog-backend@0.13.3

Patch Changes

  • 61aa652: Avoid duplicate work by comparing previous processing rounds with the next

  • fe960ad: Updates the DefaultProcessingDatabase to accept a refresh interval function instead of a fixed refresh interval in seconds which used to default to 100s. The catalog now ships with a default refresh interval function that schedules entities for refresh every 100-150 seconds, this should
    help to smooth out bursts that occur when a lot of entities are scheduled for refresh at the same second.

    Custom RefreshIntervalFunction can be implemented and passed to the CatalogBuilder using .setInterval(fn)

  • 54b441a: Export the entity provider related types for external use.

  • 03bb05a: Enabled live reload of locations configured in catalog.locations.

  • 2766b2a: Add experimental Prometheus metrics instrumentation to the catalog

  • Updated dependencies

    • @backstage/backend-common@0.8.10
    • @backstage/config@0.1.7
    • @backstage/integration@0.6.1

@backstage/plugin-catalog-backend-module-msgraph@0.2.3

Patch Changes

  • 77cdc5a: Pass along a UserTransformer to the read step
  • be498d2: Pass along a OrganizationTransformer to the read step
  • Updated dependencies
    • @backstage/plugin-catalog-backend@0.13.3
    • @backstage/config@0.1.7

@backstage/plugin-catalog-import@0.5.18

Patch Changes

  • ced85b5: Fix importing yaml files from URLs with trailing query parameters.
  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.3
    • @backstage/core-components@0.3.2
    • @backstage/integration@0.6.1
    • @backstage/theme@0.2.10

@backstage/plugin-catalog-react@0.4.3

Patch Changes

  • 3bc0092: Clarified messaging around configured locations in the UnregisterEntityDialog.
  • 2105d60: Migrate and export UnregisterEntityDialog component from catalog-react package
  • Updated dependencies
    • @backstage/core-app-api@0.1.9
    • @backstage/core-components@0.3.2
    • @backstage/integration@0.6.1

@backstage/plugin-jenkins@0.5.4

Patch Changes

  • d7d1f6f: Make isJenkinsAvailable recognise both the old and the new Jenkins annotation.
  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.3
    • @backstage/core-components@0.3.2
    • @backstage/theme@0.2.10

@backstage/plugin-jenkins-backend@0.1.3

Patch Changes

  • efbb82d: Extract JenkinsConfig to make writing a custom JenkinsInfoProvider easier.
  • Updated dependencies
    • @backstage/backend-common@0.8.10
    • @backstage/config@0.1.7

@backstage/plugin-scaffolder@0.11.1

Patch Changes

  • 5bab4fe: Previously when supplying custom scaffolder field extensions, it was necessary to also include the default ones if they were needed. Since the field extensions are keyed by name, there's no harm in leaving the default ones in place when adding custom ones - if templates don't refer to them they will be ignored, and if custom ones are introduced with the same name, the custom ones will take priority over the default ones.

    Users configuring custom field extensions can remove the default ones from the scaffolder route after this change, and they'll still be available:

        <Route path="/create" element={<ScaffolderPage />}>
          <ScaffolderFieldExtensions>
    -        <EntityPickerFieldExtension />
    -        <EntityNamePickerFieldExtension />
    -        <RepoUrlPickerFieldExtension />
    -        <OwnerPickerFieldExtension />
            <LowerCaseValuePickerFieldExtension />
          </ScaffolderFieldExtensions>
        </Route>
  • 24d0e1e: Set id in <TextValuePicker>.

  • Updated dependencies

    • @backstage/plugin-catalog-react@0.4.3
    • @backstage/config@0.1.7
    • @backstage/core-components@0.3.2
    • @backstage/integration@0.6.1
    • @backstage/theme@0.2.10

@backstage/plugin-search-backend@0.2.4

Patch Changes

  • 64baede: Improve search query logging message
  • Updated dependencies
    • @backstage/backend-common@0.8.10

@backstage/plugin-search-backend-module-pg@0.1.2

Patch Changes

  • ee99798: Correct version requirements on postgres from 11 to 12. Postgres 12 is required
    due the use of generated columns.
  • Updated dependencies
    • @backstage/backend-common@0.8.10

@backstage/plugin-sentry@0.3.19

Patch Changes

  • 0e7595d: Do not show [No Type] when issue metadata includes title instead of type
  • d8e4afc: Render the statsFor property in sentry issues table
  • Updated dependencies
    • @backstage/plugin-catalog-react@0.4.3
    • @backstage/core-components@0.3.2
    • @backstage/theme@0.2.10

@backstage/plugin-todo-backend@0.1.10

Patch Changes

  • 0b34dc7: Ignore images and files that are larger than 200KB.
  • Updated dependencies
    • @backstage/backend-common@0.8.10
    • @backstage/config@0.1.7
    • @backstage/integra...
Read more

v0.41.0

12 Aug 09:58
90439d5

Choose a tag to compare

@backstage/integration@0.6.0

Minor Changes

  • ce19580: getGitHubFileFetchUrl and getGitHubRequestOptions now require a credentials argument. This is needed to address an issue where the raw route was chosen by the UrlReader when using GitHub Apps based auth.

    Deprecated the getGitHubRequestOptions function, which is no longer used internally.

Patch Changes

  • 8bedb75: Update Luxon dependency to 2.x
  • 68af4d5: Adds an allow list of GitHub installations
  • 5fd31c2: Remove repo restriction from GitHub credentials provider

@backstage/plugin-scaffolder@0.11.0

Minor Changes

  • e30646a: Add Bitbucket workspace and project fields to RepoUrlPicker to support Bitbucket cloud and server

Patch Changes

  • 8bedb75: Update Luxon dependency to 2.x

  • 7894421: Added UI Schema support for array items for example, support EntityPicker within an array field

  • fa84fe4: - Adds a new field EntityNamePicker that can be used in scaffolder templates to accept and validate an entity name. This field is registered by default, and can be used in templates by setting the ui:field property to EntityNamePicker. If you've customized your scaffolder field extensions, you can include this one by adding it when registering the scaffolder route:

    import {
      ScaffolderFieldExtensions,
    +   EntityNamePickerFieldExtension,
    } from '@backstage/plugin-scaffolder';
    
      <Route path="/create" element={<ScaffolderPage />}>
        <ScaffolderFieldExtensions>
          {/* ...custom field extensions... */}
    
    +       <EntityNamePickerFieldExtension />
        </ScaffolderFieldExtensions>
      </Route>;
    • Adds a new generic field TextValuePicker to be used when writing custom field extensions that use a standard UI with custom validation. An example of doing this can be found in packages/app/src/components/scaffolder/customScaffolderExtensions.tsx.
  • 56c7739: Switched @types/react dependency to request * rather than a specific version.

  • Updated dependencies

    • @backstage/integration@0.6.0
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6
    • @backstage/plugin-catalog-react@0.4.2
    • @backstage/integration-react@0.1.7

@backstage/plugin-scaffolder-backend@0.15.0

Minor Changes

  • e30646a: Add Bitbucket workspace and project fields to RepoUrlPicker to support Bitbucket cloud and server

Patch Changes

  • 8bedb75: Update Luxon dependency to 2.x
  • Updated dependencies
    • @backstage/integration@0.6.0
    • @backstage/backend-common@0.8.9
    • @backstage/plugin-scaffolder-backend-module-cookiecutter@0.1.1

@backstage/plugin-sonarqube@0.2.0

Minor Changes

  • 8db48b9: Use IdentityApi to provide Auth Token for SonarQubeClient Api calls

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6
    • @backstage/plugin-catalog-react@0.4.2

@backstage/backend-common@0.8.9

Patch Changes

  • f7ce7c5: Use a more informative error message when URL reading isn't allowed due to no reader matching the target URL.
  • ce19580: Pass on credentials to the integrations package, so that it can properly pick the API route when using GitHub apps based auth
  • Updated dependencies
    • @backstage/integration@0.6.0

@backstage/backend-test-utils@0.1.5

Patch Changes

  • 5240457: Make sure that the unique databases names generated by TestDatabases.create()
    don't collide.
  • Updated dependencies
    • @backstage/backend-common@0.8.9
    • @backstage/cli@0.7.8

@backstage/cli@0.7.8

Patch Changes

  • c4ef918: Migrate to using webpack@5 🎉

@backstage/codemods@0.1.9

Patch Changes

  • Updated dependencies
    • @backstage/core-app-api@0.1.8
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6

@backstage/core-app-api@0.1.8

Patch Changes

  • 3626576: Add support for serving the app with a base path other than /, which is enabled by including the path in app.baseUrl.
  • 56c7739: Switched @types/react dependency to request * rather than a specific version.
  • Updated dependencies
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6

@backstage/core-components@0.3.1

Patch Changes

  • 56c7739: Switched @types/react dependency to request * rather than a specific version.
  • 55a5dbd: Fix for SidebarItem matching the active route too broadly.
  • Updated dependencies
    • @backstage/core-plugin-api@0.1.6

@backstage/core-plugin-api@0.1.6

Patch Changes

  • 56c7739: Switched @types/react dependency to request * rather than a specific version.

@backstage/create-app@0.3.35

Patch Changes

  • 362ea5a: Updated the index page redirect to work with apps served on a different base path than /.

    To apply this change to an existing app, remove the / prefix from the target route in the Navigate element in packages/app/src/App.tsx:

    -<Navigate key="/" to="/catalog" />
    +<Navigate key="/" to="catalog" />
  • 80582cb: Use new composable TechDocsIndexPage and DefaultTechDocsHome

    Make the following changes to your App.tsx to migrate existing apps:

    -    <Route path="/docs" element={<TechdocsPage />} />
    +    <Route path="/docs" element={<TechDocsIndexPage />}>
    +      <DefaultTechDocsHome />
    +    </Route>
    +    <Route
    +      path="/docs/:namespace/:kind/:name/*"
    +      element={<TechDocsReaderPage />}
    +    />
  • c4ef918: Migrate to using webpack@5 🎉

  • 56c7739: Add a complete prettier setup to the created project. Prettier used to only be added as a dependency to create apps, but there wasn't a complete setup included that makes it easy to run prettier. That has now changed, and the new prettier:check command can be used to check the formatting of the files in your created project.

    To apply this change to an existing app, a couple of changes need to be made.

    Create a .prettierignore file at the root of your repository with the following contents:

    dist
    dist-types
    coverage
    .vscode
    

    Next update the root package.json by bumping the prettier version and adding the new prettier:check command:

       "scripts": {
         ...
    +    "prettier:check": "prettier --check .",
         ...
       },
       ...
       "dependencies": {
         ...
    -    "prettier": "^1.19.1"
    +    "prettier": "^2.3.2"
       }

    Finally run yarn prettier --write . on your project to update the existing formatting.

  • 9f8f8dd: Removed the / prefix in the catalog SidebarItem element, as it is no longer needed.

    To apply this change to an existing app, remove the / prefix from the catalog and any other sidebar items in packages/app/src/components/Root/Root.ts:

    -<SidebarItem icon={HomeIcon} to="/catalog" text="Home" />
    +<SidebarItem icon={HomeIcon} to="catalog" text="Home" />
  • 56c7739: Switched @types/react-dom dependency to of the app package to request * rather than a specific version.

    To apply this change to an existing app, change the following in packages/app/package.json:

    -    "@types/react-dom": "^16.9.8",
    +    "@types/react-dom": "*",

@backstage/dev-utils@0.2.6

Patch Changes

  • 56c7739: Switched @types/react dependency to request * rather than a specific version.
  • Updated dependencies
    • @backstage/core-app-api@0.1.8
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6
    • @backstage/test-utils@0.1.17
    • @backstage/plugin-catalog-react@0.4.2
    • @backstage/integration-react@0.1.7

@backstage/integration-react@0.1.7

Patch Changes

  • Updated dependencies
    • @backstage/integration@0.6.0
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6

@backstage/techdocs-common@0.8.1

Patch Changes

  • bc405be: Stale TechDocs content (files that had previously been published but which have
    since been removed) is now removed from storage at publish-time. This is now
    supported by the following publishers:

    • Google GCS
    • AWS S3
    • Azure Blob Storage

    You may need to apply a greater level of permissions (e.g. the ability to
    delete objects in your storage provider) to any credentials/accounts used by
    the TechDocs CLI or TechDocs backend in order for this change to take effect.

    For more details, see #6132.

  • Updated dependencies

    • @backstage/integration@0.6.0
    • @backstage/backend-common@0.8.9

@backstage/test-utils@0.1.17

Patch Changes

  • 56c7739: Switched @types/react dependency to request * rather than a specific version.
  • Updated dependencies
    • @backstage/core-app-api@0.1.8
    • @backstage/core-plugin-api@0.1.6
    • @backstage/test-utils-core@0.1.2

@backstage/test-utils-core@0.1.2

Patch Changes

  • 56c7739: Switched @types/react dependency to request * rather than a specific version.

@backstage/plugin-api-docs@0.6.6

Patch Changes

  • 56c7739: Switched @types/react dependency to request * rather than a specific version.
  • 0383314: Support deep linking in OpenAPI definitions.
  • Updated dependencies
    • @backstage/core-components@0.3.1
    • @backstage/core-plugin-api@0.1.6
    • @backstage/plugin-catalog@0.6.11
    • @backstage/plugin-catalog-react@0.4.2

@backstage/plugin-auth-backend@0.3.20

Patch Changes

  • 29f7cff: Added resolveCatalogMembership utility to query the catalog for additional authentication claims within sig...
Read more

v0.40.1

11 Aug 14:45
4bada5c

Choose a tag to compare

Release FireHydrant Plugin

This is the first version of the FireHydrant plugin, available at @backstage/plugin-firehydrant. It pulls service incidents data from FireHydrant, such as current active incidents and incident analytics for a given service, as well as quick links to create and view all of your organization's incidents.

The plugin includes the components for rendering and an API client which calls FireHydrant through the proxy.

Screen Shot 2021-07-28 at 2 24 23 PM

v0.40.0

05 Aug 13:35
0cbbc97

Choose a tag to compare

@backstage/core-components@0.3.0

Minor Changes

  • 7bf0062: Remove unused props from InfoCard prop type

Patch Changes

  • c4d8ff9: Switched frontend identity code to use token instead of the deprecated idToken field
  • 7b8aa8d: Move the CreateComponentButton from the catalog plugin to the core-components & rename it to CreateButton to be reused inside the api-docs plugin & scaffolder plugin, but also future plugins. Additionally, improve responsiveness of CreateButton & SupportButton by shrinking them to IconButtons on smaller screens.
  • 260c053: Fix All Material UI Warnings
  • Updated dependencies
    • @backstage/config@0.1.6
    • @backstage/core-plugin-api@0.1.5

@backstage/techdocs-common@0.8.0

Minor Changes

  • 48ea3d2: TechDocs has dropped all support for the long-ago deprecated git-based common
    prepares as well as all corresponding values in backstage.io/techdocs-ref
    annotations.

    Entities whose backstage.io/techdocs-ref annotation values still begin with
    github:, gitlab:, bitbucket:, or azure/api: will no longer be generated
    by TechDocs. Be sure to update these values so that they align with their
    expected format and your usage of TechDocs.

    For details, see this explainer on TechDocs ref annotation values.

Patch Changes

  • Updated dependencies
    • @backstage/backend-common@0.8.8
    • @backstage/config@0.1.6
    • @backstage/integration@0.5.9

@backstage/backend-common@0.8.8

Patch Changes

  • 6aa7c3d: bump node-tar version to the latest
  • Updated dependencies
    • @backstage/config@0.1.6
    • @backstage/integration@0.5.9
    • @backstage/config-loader@0.6.6

@backstage/cli@0.7.7

Patch Changes

  • 6aa7c3d: bump node-tar version to the latest
  • e9d3983: Keep track of filtered configuration values when running frontend in development mode.
  • Updated dependencies
    • @backstage/config@0.1.6
    • @backstage/config-loader@0.6.6

@backstage/codemods@0.1.8

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/core-app-api@0.1.7

@backstage/config@0.1.6

Patch Changes

  • e9d3983: Add warning when trying to access configuration values that have been filtered out by visibility.

@backstage/config-loader@0.6.6

Patch Changes

  • e9d3983: Add option to populate the filteredKeys property when processing configuration with a schema.
  • Updated dependencies
    • @backstage/config@0.1.6

@backstage/core-app-api@0.1.7

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/config@0.1.6
    • @backstage/core-plugin-api@0.1.5

@backstage/core-plugin-api@0.1.5

Patch Changes

  • c4d8ff9: Switched frontend identity code to use token instead of the deprecated idToken field
  • Updated dependencies
    • @backstage/config@0.1.6

@backstage/create-app@0.3.34

Patch Changes

@backstage/dev-utils@0.2.5

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/core-app-api@0.1.7
    • @backstage/integration-react@0.1.6
    • @backstage/plugin-catalog-react@0.4.1

@backstage/integration@0.5.9

Patch Changes

  • 3c50ff5: Fixed bug for comparing Organization name in GithubCredentialsProvider
  • Updated dependencies
    • @backstage/config@0.1.6

@backstage/integration-react@0.1.6

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/config@0.1.6
    • @backstage/core-plugin-api@0.1.5
    • @backstage/integration@0.5.9

@backstage/search-common@0.1.3

Patch Changes

  • d9c13d5: Implements configuration and indexing functionality for ElasticSearch search engine. Adds indexing, searching and default translator for ElasticSearch and modifies default backend example-app to use ES if it is configured.

    Example configurations:

    AWS

    Using AWS hosted ElasticSearch the only configuration options needed is the URL to the ElasticSearch service. The implementation assumes
    that environment variables for AWS access key id and secret access key are defined in accordance to the default AWS credential chain..

    search:
      elasticsearch:
        provider: aws
        node: https://my-backstage-search-asdfqwerty.eu-west-1.es.amazonaws.com

    Elastic.co

    Elastic Cloud hosted ElasticSearch uses a Cloud ID to determine the instance of hosted ElasticSearch to connect to. Additionally, username and password needs to be provided either directly or using environment variables like defined in Backstage documentation.

    search:
      elasticsearch:
        provider: elastic
        cloudId: backstage-elastic:asdfqwertyasdfqwertyasdfqwertyasdfqwerty==
        auth:
          username: elastic
          password: changeme

    Others

    Other ElasticSearch instances can be connected to by using standard ElasticSearch authentication methods and exposed URL, provided that the cluster supports that. The configuration options needed are the URL to the node and authentication information. Authentication can be handled by either providing username/password or and API key or a bearer token. In case both username/password combination and one of the tokens are provided, token takes precedence. For more information how to create an API key, see Elastic documentation on API keys and how to create a bearer token, see Elastic documentation on tokens.

    Configuration examples

    With username and password
    search:
      elasticsearch:
        node: http://localhost:9200
        auth:
          username: elastic
          password: changeme
    With bearer token
    search:
      elasticsearch:
        node: http://localhost:9200
        auth:
          bearer: token
    With API key
    search:
      elasticsearch:
        node: http://localhost:9200
        auth:
          apiKey: base64EncodedKey
  • Updated dependencies

    • @backstage/config@0.1.6

@backstage/plugin-api-docs@0.6.5

Patch Changes

  • 7b8aa8d: Move the CreateComponentButton from the catalog plugin to the core-components & rename it to CreateButton to be reused inside the api-docs plugin & scaffolder plugin, but also future plugins. Additionally, improve responsiveness of CreateButton & SupportButton by shrinking them to IconButtons on smaller screens.
  • Updated dependencies
    • @backstage/plugin-catalog@0.6.10
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/plugin-catalog-react@0.4.1

@backstage/plugin-badges@0.2.7

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/plugin-catalog-react@0.4.1

@backstage/plugin-bitrise@0.1.9

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/plugin-catalog-react@0.4.1

@backstage/plugin-catalog@0.6.10

Patch Changes

  • cf4635f: Fix bug with re-rendering the EntityRoutes when the entity changes but the route does not
  • 7b8aa8d: Move the CreateComponentButton from the catalog plugin to the core-components & rename it to CreateButton to be reused inside the api-docs plugin & scaffolder plugin, but also future plugins. Additionally, improve responsiveness of CreateButton & SupportButton by shrinking them to IconButtons on smaller screens.
  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/integration@0.5.9
    • @backstage/integration-react@0.1.6
    • @backstage/plugin-catalog-react@0.4.1

@backstage/plugin-catalog-import@0.5.16

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/integration@0.5.9
    • @backstage/integration-react@0.1.6
    • @backstage/plugin-catalog-react@0.4.1

@backstage/plugin-catalog-react@0.4.1

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/integration@0.5.9
    • @backstage/core-app-api@0.1.7

@backstage/plugin-circleci@0.2.21

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.3.0
    • @backstage/core-plugin-api@0.1.5
    • @backstage/plugin-catalog-react@0.4.1

@backstage/plugin-cloudbuild@0.2.21

#...

Read more

v0.39.1

03 Aug 17:58
4f3c36b

Choose a tag to compare

Released a new backend module package for use with the search backend plugin to enable search via ElasticSearch, @backstage/plugin-search-backend-module-elasticsearch

v0.39.0

29 Jul 11:44
c49b012

Choose a tag to compare

@backstage/core-components@0.2.0

Minor Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes

Patch Changes

  • 19d9995: Improve accessibility of core & catalog components by adjusting them with non-breaking changes.

  • 224e544: Added an EntityProcessingErrorsPanel component to show any errors that occurred when refreshing an entity from its source location.

    If upgrading, this should be added to your EntityPage in your Backstage application:

    // packages/app/src/components/catalog/EntityPage.tsx
    
    const overviewContent = (
    ...
              <EntityOrphanWarning />
            </Grid>
           </EntitySwitch.Case>
        </EntitySwitch>
    +   <EntitySwitch>
    +     <EntitySwitch.Case if={hasCatalogProcessingErrors}>
    +       <Grid item xs={12}>
    +         <EntityProcessingErrorsPanel />
    +       </Grid>
    +     </EntitySwitch.Case>
    +   </EntitySwitch>
    

    Additionally, WarningPanel now changes color based on the provided severity.

  • Updated dependencies

    • @backstage/core-plugin-api@0.1.4
    • @backstage/theme@0.2.9

@backstage/plugin-catalog-react@0.4.0

Minor Changes

  • c5cb558: Introduce the useEntityOwnership hook, which implements the full new ownership model.

    This also means a breaking change to the interface of UserListFilter. It no longer
    accepts a user entity as input, but rather a function that checks ownership of an
    entity. This function is taken from the above mentioned hook output. So if you are
    instantiating the filter yourself, you will change from something like

    const { entity } = useOwnUser();
    const filter = new UserListFilter('owned', user, ...);

    to

    const { isOwnedEntity } = useEntityOwnership();
    const filter = new UserListFilter('owned', isOwnedEntity, ...);

Patch Changes

  • 19d9995: Improve accessibility of core & catalog components by adjusting them with non-breaking changes.
  • 11c370a: Export CATALOG_FILTER_EXISTS symbol
  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes
  • 043a423: Fix EntityListProvider to not update url if unmounted
  • Updated dependencies
    • @backstage/core-components@0.2.0
    • @backstage/core-app-api@0.1.6
    • @backstage/core-plugin-api@0.1.4
    • @backstage/catalog-client@0.3.18

@backstage/plugin-xcmetrics@0.2.0

Minor Changes

  • 616e10e: New data in form of trend lines, status timeline and other is added to the dashboard of XCMetrics to give a better understanding of how the build system is behaving.

Patch Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes
  • Updated dependencies
    • @backstage/core-components@0.2.0
    • @backstage/core-plugin-api@0.1.4
    • @backstage/theme@0.2.9

@backstage/catalog-client@0.3.18

Patch Changes

  • 11c370a: Support filtering entities via property existence

@backstage/cli@0.7.6

Patch Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes

@backstage/codemods@0.1.7

Patch Changes

  • Updated dependencies
    • @backstage/core-components@0.2.0
    • @backstage/core-app-api@0.1.6
    • @backstage/core-plugin-api@0.1.4

@backstage/core-app-api@0.1.6

Patch Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes
  • Updated dependencies
    • @backstage/core-components@0.2.0
    • @backstage/core-plugin-api@0.1.4
    • @backstage/theme@0.2.9

@backstage/core-plugin-api@0.1.4

Patch Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes
  • Updated dependencies
    • @backstage/theme@0.2.9

@backstage/create-app@0.3.33

Patch Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.

    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes
  • d50c9e7: Update the software-templates to point to main branch instead of master

  • 224e544: Added an EntityProcessingErrorsPanel component to show any errors that occurred when refreshing an entity from its source location.

    If upgrading, this should be added to your EntityPage in your Backstage application:

    // packages/app/src/components/catalog/EntityPage.tsx
    
    const overviewContent = (
    ...
              <EntityOrphanWarning />
            </Grid>
           </EntitySwitch.Case>
        </EntitySwitch>
    +   <EntitySwitch>
    +     <EntitySwitch.Case if={hasCatalogProcessingErrors}>
    +       <Grid item xs={12}>
    +         <EntityProcessingErrorsPanel />
    +       </Grid>
    +     </EntitySwitch.Case>
    +   </EntitySwitch>
    

    Additionally, WarningPanel now changes color based on the provided severity.

@backstage/dev-utils@0.2.4

Patch Changes

  • 9d40fcb: - Bumping material-ui/core version to at least 4.12.2 as they made some breaking changes in later versions which broke Pagination of the Table.
    • Switching out material-table to @material-table/core for support for the later versions of material-ui/core
    • This causes a minor API change to @backstage/core-components as the interface for Table re-exports the prop from the underlying Table components.
    • onChangeRowsPerPage has been renamed to onRowsPerPageChange
    • onChangePage has been renamed to onPageChange
    • Migration guide is here: https://material-table-core.com/docs/breaking-changes
  • Updated dependencies
    • @backstage/core-components@0.2.0
    • @backstage/plugin-catalog-react@0.4.0
    • @backstage/core-app-api@0.1.6
    • @backstage/core-plugin-api@0.1.4
    • @backstage/integration-react@0.1.5
    • @backstage/test-utils@0.1.16
    • @bac...
Read more