Skip to content

Releases: CrystallizeAPI/import-utilities

v1.28.0

29 Jun 11:11
e69eec7
Compare
Choose a tag to compare

Minor Changes

v1.27.0

29 Jun 10:52
8866b31
Compare
Choose a tag to compare

Minor Changes

  • 6beea90: Add Item Relation for SKUs

v1.26.0

06 Jun 16:11
5d47484
Compare
Choose a tag to compare

Minor Changes

  • 5134397: Upgrading packages and minor bugfix

v1.25.0

26 Apr 08:06
b42070c
Compare
Choose a tag to compare

Minor Changes

  • 5828857: Updated generated grapqhl schema

Patch Changes

  • 5828857: Updated dependencies to resolve vulnerabilities

v1.24.4

19 Apr 17:45
dd8d4f5
Compare
Choose a tag to compare

Patch Changes

  • 65a058c: Fixed package links in readme

v1.24.3

30 Mar 09:47
8070b46
Compare
Choose a tag to compare

Patch Changes

  • e530a8c: Added types for useItemRelationsComponent extended
    component-content.input
  • 24e5633: Added a fix for sanitization of not adding item relations components
    when found alone, in chunks and choice in items.ts for documents, products,
    and variant items.

v1.24.2

24 Mar 09:56
3ea3e52
Compare
Choose a tag to compare

Patch Changes

  • 81563ab: Fixed an issue where product variant component data would not be
    exported for all languages.

v1.24.1

21 Mar 14:10
81f273b
Compare
Choose a tag to compare

Patch Changes

  • dbe4a4c: Fix error when boolean content is null in a chunk

v1.24.0

13 Mar 12:31
b28b442
Compare
Choose a tag to compare

Minor Changes

  • 2bc9e95: includeDescendantsOfUnpublishedFolders option for items is
    introduced to give you the possibility to include published items that are
    located under an published folders for bootstrapper.createSpec().

    This is only useful if you're targeting the published version of items.
    Example:

    const spec = await bootstrapper.createSpec({
        ...
        items: {
          version: 'published',
          includeDescendantsOfUnpublishedFolders: true,
        }
      })
    

    Beware Unpublished folders will appear with an invalid shape identifier in
    the export, which makes it unsuitable for import. The real value here is if
    you combine this with another createSpec where you target the current or
    draft version of items, which together gives the correct image of the
    current item tree state.

v1.23.0

10 Mar 12:35
5fa7e86
Compare
Choose a tag to compare

Minor Changes

  • 2eecefa: Certain internals in the items area are now running in parallel for
    the spec creation. This increases the speed of spec creation of items with
    roughly 40%.

    This also introduces an internal load balancing mechanism, which is designed
    to keep the request counts below the threshold of Crystallize APIs

Patch Changes

  • 5e70780: Bump import-export-sdk and schema deps
  • 5794af7: Update @crystallize/schema to 0.0.4