Skip to content

release-2025-01-13

Latest
Compare
Choose a tag to compare
@github-actions github-actions released this 13 Jan 10:32
647dbf8

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@roadiehq/[email protected]

Major Changes

  • 6e4add9: BREAKING: Needs SCM auth API to be configured in the application.

    Migrate to use SCM auth instead of direct GitHub to allow possibility to work with multiple GitHub integrations at once.

    This will work automatically if ScmAuth.createDefaultApiFactory() is used when APIs registered. If not, you need to register an implementation of scmAuthApiRef as documented in: https://backstage.io/docs/auth/#custom-scmauthapi-implementation.

@roadiehq/[email protected]

Major Changes

  • 6e4add9: BREAKING: Needs SCM auth API to be configured in the application.

    Migrate to use SCM auth instead of direct GitHub to allow possibility to work with multiple GitHub integrations at once.

    This will work automatically if ScmAuth.createDefaultApiFactory() is used when APIs registered. If not, you need to register an implementation of scmAuthApiRef as documented in: https://backstage.io/docs/auth/#custom-scmauthapi-implementation.

@roadiehq/[email protected]

Major Changes

  • 6e4add9: BREAKING: Needs SCM auth API to be configured in the application.

    Migrate to use SCM auth instead of direct GitHub to allow possibility to work with multiple GitHub integrations at once.

    This will work automatically if ScmAuth.createDefaultApiFactory() is used when APIs registered. If not, you need to register an implementation of scmAuthApiRef as documented in: https://backstage.io/docs/auth/#custom-scmauthapi-implementation.

[email protected]

Patch Changes