docs/releases/v1.2.0-next.0-changelog.md
6673babab9: Gerrit UrlReader: Implemented readTree
1b4e1e2306: Split bitbucket integration into bitbucketCloud and bitbucketServer
(backwards compatible).
In order to migrate to the new integration configs,
move your configs from integrations.bitbucket
to integrations.bitbucketCloud or integrations.bitbucketServer.
Migration example:
Before:
integrations:
bitbucket:
- host: bitbucket.org
username: bitbucket_user
appPassword: app-password
- host: bitbucket-server.company.com
token: my-token
After:
integrations:
bitbucketCloud:
- username: bitbucket_user
appPassword: app-password
bitbucketServer:
- host: bitbucket-server.company.com
token: my-token
566407bf8a: Gerrit Integration: Added the getGerritProjectsApiUrl function
1b4e1e2306: Split bitbucket integration into bitbucketCloud and bitbucketServer
(backwards compatible).
In order to migrate to the new integration configs,
move your configs from integrations.bitbucket
to integrations.bitbucketCloud or integrations.bitbucketServer.
Migration example:
Before:
integrations:
bitbucket:
- host: bitbucket.org
username: bitbucket_user
appPassword: app-password
- host: bitbucket-server.company.com
token: my-token
After:
integrations:
bitbucketCloud:
- username: bitbucket_user
appPassword: app-password
bitbucketServer:
- host: bitbucket-server.company.com
token: my-token
NotFoundComponent to EntityLayout which can be used to include a custom component when an entity is not found in the catalogplugin-catalog-backend-module-gerrit pluginfs-extra to 10.1.0.9818112d12: Update the github:publish action to allow passing required status check
contexts before merging to the main branch.
8d5a2238a9: Split publish:bitbucket into publish:bitbucketCloud and publish:bitbucketServer.
In order to migrate from the deprecated action, you need to replace the use of action
publish:bitbucket in your templates with the use of either publish:bitbucketCloud
or publish:bitbucketServer - depending on which destination SCM provider you use.
Additionally, these actions will not utilize integrations.bitbucket anymore,
but integrations.bitbucketCloud or integrations.bitbucketServer respectively.
You may or may not have migrated to these already.
As described in a previous changeset, using these two replacement integrations configs
will not compromise use cases which still rely on integrations.bitbucket as this was
set up in a backwards compatible way.
Additionally, please mind that the option enableLFS is only available (and always was)
for Bitbucket Server use cases and therefore, is not even part of the schema for
publish:bitbucketCloud anymore.
fs-extra to 10.1.0.5f4dbd2b52: A package for contributed TechDocs addons.
In this release it will introduce the ReportIssue addon, which lets you select text and open a GitHub/Gitlab issue.
createTechDocsAddonExtension to better reflect the fact that passing children to Addon components is not a valid use-case.cloneUrl string to config.fs-extra to 10.1.0.jose 4.6.0scope field. If unset, or having the
value 'global', the old behavior with cross-worker locking is retained. If
having the value 'local', there is no coordination across workers and the
behavior is more like setInterval. This can be used to replace usages of
runPeriodically helpers.create-github-app command.fs-extra to 10.1.0.commander to version 9.1.0create-github-app command to throw an error if the organization argument is a user or a non existing organization.commander to version 9.1.0fs-extra to 10.1.0.3983940a21: Optimized the command order in packages/backend/Dockerfile as well as added the --no-install-recommends to the apt-get install and tweaked the installed packages.
To apply this change to an existing app, update your packages/backend/Dockerfile to match the documented Dockerfile at https://backstage.io/docs/deployment/docker#host-build.
28bbf5aff6: Added some instruction comments to the generated config files, to clarify the
usage of backend.baseUrl and backend.listen.host. Importantly, it also per
default now listens on all IPv4 interfaces, to make it easier to take the step
over to production. If you want to do the same, update your
app-config.production.yaml as follows:
backend:
listen:
port: 7007
+ host: 0.0.0.0
Also, updated the builtin backend Dockerfile to honor the
app-config.production.yaml file. If you want to do the same, change
packages/backend/Dockerfile as follows:
-COPY packages/backend/dist/bundle.tar.gz app-config.yaml ./
+COPY packages/backend/dist/bundle.tar.gz app-config*.yaml ./
RUN tar xzf bundle.tar.gz && rm bundle.tar.gz
-CMD ["node", "packages/backend", "--config", "app-config.yaml"]
+CMD ["node", "packages/backend", "--config", "app-config.yaml", "--config", "app-config.production.yaml"]
If you look carefully, this adds a glob match on app-config files. For those
that try out the build flows locally, you also want to make sure that the docker
daemon does NOT pick up any local/private config files that might contain
secrets. You should therefore also update your local .dockerignore file at the
same time:
+*.local.yaml
cfc0f19699: Updated dependency fs-extra to 10.1.0.
344ea56acc: Bump commander to version 9.1.0
806427545f: Added a link to the ${GITHUB_TOKEN} to document how to generate a token
commander to version 9.1.0Routes element to wrap the Route elements of the test app wrapping.mountedRoutes implementation are now hidden during rendering.fs-extra to 10.1.0.cfc0f19699: Updated dependency fs-extra to 10.1.0.
787ae0d541: Add more common predefined sign-in resolvers to auth providers.
Add the existing resolver to more providers (already available at google):
providers.microsoft.resolvers.emailLocalPartMatchingUserEntityName()providers.okta.resolvers.emailLocalPartMatchingUserEntityName()Add a new resolver for simple email-to-email matching:
providers.google.resolvers.emailMatchingUserEntityProfileEmail()providers.microsoft.resolvers.emailMatchingUserEntityProfileEmail()providers.okta.resolvers.emailMatchingUserEntityProfileEmail()9ec4e0613e: Update to jose 4.6.0
Updated dependencies
jose 4.6.0knex when checking returned rowsfs-extra to 10.1.0.PermissionEvaluator instance check that would cause unexpected "invalid union" errors.bffec1c96a: Fix S3 object URL creation at AwsS3EntityProvider by
Updated dependencies
8d9f673106: Add annotation microsoft.com/email when using the defaultUserTransformer.
This will allow users of the Microsoft auth provider to utilize the predefined SignIn resolver instead of maintaining their own.
// backend/plugins/auth.ts
// [...]
export default async function createPlugin(
env: PluginEnvironment,
): Promise<Router> {
return await createRouter({
// [...]
providerFactories: {
microsoft: providers.microsoft.create({
signIn: {
resolver:
providers.microsoft.resolvers.emailMatchingUserEntityAnnotation(),
},
}),
},
});
}
Updated dependencies
PermissionEvaluator instance check that would cause unexpected "invalid union" errors.fs-extra to 10.1.0.FetchApi and related fetchApiRef which implement fetch. in order to included the Authorization Token to New Relic Dashboard Plugin, so that frontend can send an authenticated proxy call to backendfs-extra to 10.1.0.fs-extra to 10.1.0.HomePageSearchBar requiring SearchContextPermissionEvaluator instance check that would cause unexpected "invalid union" errors.useSearchContextCheck hook to check if the search context is available@backstage/core-app-api.@backstage/core-app-api.fs-extra to 10.1.0.fs-extra to 10.1.0.createTechDocsAddonExtension to better reflect the fact that passing children to Addon components is not a valid use-case.