docs/releases/v1.4.0-next.1-changelog.md
96a82d9791: BREAKING: Removed the following deprecated package commands:
app:build - Use package build insteadapp:serve - Use package start insteadbackend:build - Use package build insteadbackend:bundle - Use package build insteadbackend:dev - Use package start insteadplugin:build - Use package build insteadplugin:serve - Use package start insteadbuild - Use package build insteadlint - Use package lint insteadprepack - Use package prepack insteadpostpack - Use package postpack insteadIn order to replace these you need to have migrated to using package roles.
@rollup/plugin-node-resolve to ^13.0.6run-script-webpack-plugin to ^0.1.0.6d61b44466: The ResponseError.fromResponse now accepts a more narrow response type, in order to avoid incompatibilities between different fetch implementations.
The response property of ResponseError has also been narrowed to a new ConsumedResponse type that omits all the properties for consuming the body of the response. This is not considered a breaking change as it was always an error to try to consume the body of the response.
9d4040777e: BREAKING: Removed all directly exported auth provider factories, option types, and sign-in resolvers. For example: AwsAlbProviderOptions, bitbucketUserIdSignInResolver, createGithubProvider. These are all still accessible via the providers export. For example, use providers.github.create() rather than createGithubProvider(), and providers.bitbucket.resolvers.userIdMatchingUserEntityAnnotation() rather than bitbucketUserIdSignInResolver.
BREAKING: Removed the exported AuthProviderFactoryOptions type as well as the deprecated option fields of the AuthProviderFactory callback. This includes the tokenManager, tokenIssuer, discovery, and catalogApi fields. Existing usage of these should be replaced with the new utilities in the resolverContext field. The deprecated TokenIssuer type is now also removed, since it is no longer used.
BREAKING: Removed getEntityClaims, use getDefaultOwnershipEntityRefs instead.
DEPRECATION: Deprecated AtlassianAuthProvider as it was unintentionally exported.
67503d159e: Add basic OpenAPI \$ref support.
For more information see here.
c5af773757: BREAKING: In order to remain interoperable with all currently supported
deployments of Elasticsearch, this package will now conditionally use either
the @elastic/elasticsearch or @opensearch-project/opensearch client when
communicating with your deployed cluster.
If you do not rely on types exported from this package, or if you do not make
use of the createElasticSearchClientOptions or newClient methods on the
ElasticSearchSearchEngine class, then upgrading to this version should not
require any further action on your part. Everything will continue to work as it
always has.
If you do rely on either of the above methods or any underlying types, some
changes may be needed to your custom code. A type guard is now exported by this
package (isOpenSearchCompatible(options)), which you may use to help clarify
which client options are compatible with which client constructors.
If you are using this package with the search.elasticsearch.provider set to
aws, and you are making use of the newClient method in particular, you may
wish to start using the @opensearch-project/opensearch client in your custom
code.
config: techdocs.publisher.local.publishDirectoryconfig: techdocs.publisher.local.publishDirectorylegacyCopyReadmeMdToIndexMd in techdocs-cli generate command, and decouple it's logic from the techdocs-ref flag.SidebarSubmenuItemlegacyCopyReadmeMdToIndexMd in techdocs-cli generate command, and decouple it's logic from the techdocs-ref flag.htmlFontSize property and also sets typography design tokens for h5 and h6 in base theme.49ff472c0b: Add the possibility in the GitlabDiscoveryEntityProvider to scan the whole project instead of concrete groups. For that, use a configuration like this one, where the group parameter is omitted (not mandatory anymore):
catalog:
providers:
gitlab:
yourProviderId:
host: gitlab-host # Identifies one of the hosts set up in the integrations
branch: main # Optional. Uses `master` as default
entityFilename: catalog-info.yaml # Optional. Defaults to `catalog-info.yaml`
Updated dependencies
a46e317a75: Added support for customizing the time format used in the HeaderWorldClock component
Here's an example of how this can be used in the HomePage.tsx found in \packages\app\src\components\home to change the clock to be in the 24hr time format:
+const timeFormat: Intl.DateTimeFormatOptions = {
+ hour: '2-digit',
+ minute: '2-digit',
+ hour12: false,
+};
export const homePage = (
<Page themeId="home">
<Header title={<WelcomeTitle />} pageTitleOverride="Home">
+ <HeaderWorldClock clockConfigs={clockConfigs} customTimeFormat={timeFormat} />
</Header>
<Content>
<Grid container spacing={3}>
<Grid item xs={12}>
<HomePageSearchBar />
</Grid>
Updated dependencies
MyGroupsSidebarItem509c4092f0: To allow people to use a global search context in the search modal, the code for the search modal has been changed to only create a local search context if there is no parent context already defined.
If you want to continue using a local context even if you define a global one, you will have to wrap the modal in a new local context manually:
<SearchContextProvider>
<SearchModal toggleModal={toggleModal} />
</SearchContextProvider>
Updated dependencies