@coveo/atomic 3.32.1-pre.7d360dc04c → 3.32.1-pre.85a5ccfeec

package/dist/esm/atomic-insight-interface.entry.js

@@ -1,15 +1,15 @@
 import { r as registerInstance, s as setNonce, h, H as Host, g as getElement } from './index-3f35faca.js';
 import { m as markParentAsReady } from './init-queue-fbe942c3.js';
 import { buildResultsPerPage, loadFieldActions, buildInsightEngine } from '@coveo/headless/insight';
-import { g as getNextAnalyticsConfig, a as augmentWithExternalMiddleware, b as augmentAnalyticsWithAtomicVersion, C as CommonAtomicInterfaceHelper, i as instance } from './analytics-config-e7c72c88.js';
+import { g as getNextAnalyticsConfig, a as augmentWithExternalMiddleware, b as augmentAnalyticsWithAtomicVersion, C as CommonAtomicInterfaceHelper, i as instance } from './analytics-config-77cf380f.js';
 import { A as ArrayProp } from './props-utils-76e19fa7.js';
 import { D as DEFAULT_MOBILE_BREAKPOINT } from './replace-breakpoint-213367f8.js';
 import { u as unsetLoadingFlag, s as setLoadingFlag, r as registerFacet, g as getFacetElements, w as waitUntilAppLoaded, a as createBaseStore } from './store-e14e2958.js';
 import { m as makeDesktopQuery } from './insight-layout-776b87f2.js';
 import './dayjs.min-d04628c6.js';
 import './_commonjsHelpers-1789f0cf.js';
-import './purify-c7ebd240.js';
 import '@coveo/headless';
+import './purify-c7ebd240.js';
 import '@coveo/bueno';
 import './utils-7ac76ba7.js';
 import './dom-utils-f6086cd3.js';

package/dist/esm/atomic-recs-interface.entry.js

@@ -1,13 +1,13 @@
 import { r as registerInstance, s as setNonce, h, g as getElement } from './index-3f35faca.js';
 import { m as markParentAsReady } from './init-queue-fbe942c3.js';
 import { loadRecommendationActions, loadSearchConfigurationActions, EcommerceDefaultFieldsToInclude, loadFieldActions, buildRecommendationEngine } from '@coveo/headless/recommendation';
-import { g as getNextAnalyticsConfig, c as augmentAnalyticsConfigWithDocument, d as augmentAnalyticsConfigWithAtomicVersion, a as augmentWithExternalMiddleware, b as augmentAnalyticsWithAtomicVersion, C as CommonAtomicInterfaceHelper, i as instance, m as mismatchedInterfaceAndEnginePropError } from './analytics-config-e7c72c88.js';
+import { g as getNextAnalyticsConfig, c as augmentAnalyticsConfigWithDocument, d as augmentAnalyticsConfigWithAtomicVersion, a as augmentWithExternalMiddleware, b as augmentAnalyticsWithAtomicVersion, C as CommonAtomicInterfaceHelper, i as instance, m as mismatchedInterfaceAndEnginePropError } from './analytics-config-77cf380f.js';
 import { A as ArrayProp } from './props-utils-76e19fa7.js';
 import { u as unsetLoadingFlag, s as setLoadingFlag, a as createBaseStore } from './store-e14e2958.js';
 import './dayjs.min-d04628c6.js';
 import './_commonjsHelpers-1789f0cf.js';
-import './purify-c7ebd240.js';
 import '@coveo/headless';
+import './purify-c7ebd240.js';
 import '@coveo/bueno';
 import './utils-7ac76ba7.js';
 

package/dist/esm/atomic-search-interface.entry.js

@@ -1,7 +1,7 @@
 import { r as registerInstance, s as setNonce, h, g as getElement } from './index-3f35faca.js';
 import { m as markParentAsReady } from './init-queue-fbe942c3.js';
 import { loadSearchConfigurationActions, loadQueryActions, EcommerceDefaultFieldsToInclude, loadFieldActions, buildSearchEngine, buildUrlManager, buildSearchStatus } from '@coveo/headless';
-import { g as getNextAnalyticsConfig, d as augmentAnalyticsConfigWithAtomicVersion, c as augmentAnalyticsConfigWithDocument, a as augmentWithExternalMiddleware, b as augmentAnalyticsWithAtomicVersion, C as CommonAtomicInterfaceHelper, i as instance, m as mismatchedInterfaceAndEnginePropError } from './analytics-config-e7c72c88.js';
+import { g as getNextAnalyticsConfig, d as augmentAnalyticsConfigWithAtomicVersion, c as augmentAnalyticsConfigWithDocument, a as augmentWithExternalMiddleware, b as augmentAnalyticsWithAtomicVersion, C as CommonAtomicInterfaceHelper, i as instance, m as mismatchedInterfaceAndEnginePropError } from './analytics-config-77cf380f.js';
 import { a as StorageItems, S as SafeStorage } from './local-storage-utils-410269e6.js';
 import { A as ArrayProp } from './props-utils-76e19fa7.js';
 import { m as makeDesktopQuery, n as noResultsSelector, e as errorSelector, f as firstSearchExecutedSelector } from './search-layout-1e3bd9fd.js';

package/dist/esm/atomic-sort-expression.entry.js

@@ -50,7 +50,7 @@ const AtomicSortExpression = class {
         const dropdownComponent = 'atomic-sort-dropdown';
         if (!this.host.closest(dropdownComponent)) {
             const error = new Error(`The "${this.host.nodeName.toLowerCase()}" component has to be used inside an ${dropdownComponent} element.`);
-            return (h("atomic-component-error", { key: '4ed1b69f9f7e7f0de9db4d3de45a23202df3a9db', element: this.host, error: error }));
+            return (h("atomic-component-error", { key: '745dd01b0ba0c5b66e60ef9b8c8d66b46658f356', element: this.host, error: error }));
         }
     }
     get host() { return getElement(this); }

package/dist/esm/atomic-sort-expression.entry.js.map

@@ -1 +1 @@
-{"file":"atomic-sort-expression.entry.js","mappings":";;;;;;;;;;;;;;;;;MAUa,oBAAoB;;;;;;;;;;;;QA8CxB,iBAAY,GAAsB,IAAI,CAAC;;;;;;;;;;QAavC,iBAAY,GAAsB,IAAI,CAAC;;;4BAbL,IAAI;4BAaJ,IAAI;;IAEtC,MAAM;QACX,IAAI,IAAI,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,IAAI,IAAI,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,EAAE;YAChE,OAAO,CAAC,IAAI,CACV,qHAAqH,CACtH,CAAC;SACH;QAED,MAAM,iBAAiB,GAAG,sBAAsB,CAAC;QAEjD,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,OAAO,CAAC,iBAAiB,CAAC,EAAE;YACzC,MAAM,KAAK,GAAG,IAAI,KAAK,CACrB,QAAQ,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,WAAW,EAAE,wCAAwC,iBAAiB,WAAW,CAC7G,CAAC;YACF,QACE,+EACE,OAAO,EAAE,IAAI,CAAC,IAAI,EAClB,KAAK,EAAE,KAAK,GACY,EAC1B;SACH;KACF;;;AAnCM;IAFN,SAAS,EAAE;0DAEkC;AAavC;IAFN,SAAS,EAAE;0DAEkC;;;;","names":[],"sources":["src/components/search/atomic-sort-expression/atomic-sort-expression.tsx"],"sourcesContent":["import {Component, Prop, Element, h} from '@stencil/core';\nimport {ArrayProp} from '../../../utils/props-utils';\n\n/**\n * The `atomic-sort-expression` component defines a sort expression. This component must be inside an `atomic-sort-dropdown` component.\n */\n@Component({\n  tag: 'atomic-sort-expression',\n  shadow: false,\n})\nexport class AtomicSortExpression {\n  @Element() public host!: HTMLElement;\n\n  /**\n   * The non-localized label to display for this expression.\n   */\n  @Prop({reflect: true}) public label!: string;\n\n  /**\n   * One or more sort criteria that the end user can select or toggle between.\n   *\n   * The available sort criteria are:\n   *\n   * * `relevancy`\n   * * `date ascending`/`date descending`\n   * * `qre`\n   * * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (`criteria=\"size ascending\"`).\n   *\n   * You can specify multiple sort criteria to be used in the same request by separating them with a comma (`criteria=\"size ascending, date ascending\"`).\n   * \n   * .Combining Sort Criteria\n   * [%collapsible]\n   * ====\n   * You can specify a list of comma-separated sort criteria which will be applied sequentially. For example, if there's a tie on the 1st criterion, the API uses the 2nd criterion to break the tie. However, this only works when combining:\n   * * a relevancy criterion followed by one or more field or date criteria.\n   * * a qre criterion followed by one or more field or date criteria.\n   * * two or more field criteria (`<FIELD>` descending, `<FIELD>` descending).\n   * * a single date criterion and one or more field criteria in any order (`<FIELD>` descending, date ascending).\n   * Examples:\n   * * `relevancy`, `<FIELD> descending`\n   * * `qre`, `<FIELD> ascending`\n   * * `date descending`, `<FIELD> descending`, `<FIELD> ascending`\n   * ====\n   */\n  @Prop({reflect: true}) public expression!: string;\n  /**\n   * The tabs on which the sort expression can be displayed. This property should not be used at the same time as `tabs-excluded`.\n   *\n   * Set this property as a stringified JSON array, e.g.,\n   * ```html\n   *  <atomic-sort-expression tabs-included='[\"tabIDA\", \"tabIDB\"]'></atomic-sort-expression snippet>\n   * ```\n   * If you don't set this property, the sort expression can be displayed on any tab. Otherwise, the sort expression can only be displayed on the specified tabs.\n   */\n  @ArrayProp()\n  @Prop({reflect: true, mutable: true})\n  public tabsIncluded: string[] | string = '[]';\n\n  /**\n   * The tabs on which the sort expression must not be displayed. This property should not be used at the same time as `tabs-included`.\n   *\n   * Set this property as a stringified JSON array, e.g.,\n   * ```html\n   *  <atomic-sort-expression tabs-excluded='[\"tabIDA\", \"tabIDB\"]'></atomic-sort-expression>\n   * ```\n   * If you don't set this property, the sort expression can be displayed on any tab. Otherwise, the sort expression won't be displayed on any of the specified tabs.\n   */\n  @ArrayProp()\n  @Prop({reflect: true, mutable: true})\n  public tabsExcluded: string[] | string = '[]';\n\n  public render() {\n    if (this.tabsIncluded.length > 0 && this.tabsExcluded.length > 0) {\n      console.warn(\n        'Values for both \"tabs-included\" and \"tabs-excluded\" have been provided. This is could lead to unexpected behaviors.'\n      );\n    }\n\n    const dropdownComponent = 'atomic-sort-dropdown';\n\n    if (!this.host.closest(dropdownComponent)) {\n      const error = new Error(\n        `The \"${this.host.nodeName.toLowerCase()}\" component has to be used inside an ${dropdownComponent} element.`\n      );\n      return (\n        <atomic-component-error\n          element={this.host}\n          error={error}\n        ></atomic-component-error>\n      );\n    }\n  }\n}\n"],"version":3}
+{"file":"atomic-sort-expression.entry.js","mappings":";;;;;;;;;;;;;;;;;MAUa,oBAAoB;;;;;;;;;;;;QAgCxB,iBAAY,GAAsB,IAAI,CAAC;;;;;;;;;;QAavC,iBAAY,GAAsB,IAAI,CAAC;;;4BAbL,IAAI;4BAaJ,IAAI;;IAEtC,MAAM;QACX,IAAI,IAAI,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,IAAI,IAAI,CAAC,YAAY,CAAC,MAAM,GAAG,CAAC,EAAE;YAChE,OAAO,CAAC,IAAI,CACV,qHAAqH,CACtH,CAAC;SACH;QAED,MAAM,iBAAiB,GAAG,sBAAsB,CAAC;QAEjD,IAAI,CAAC,IAAI,CAAC,IAAI,CAAC,OAAO,CAAC,iBAAiB,CAAC,EAAE;YACzC,MAAM,KAAK,GAAG,IAAI,KAAK,CACrB,QAAQ,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,WAAW,EAAE,wCAAwC,iBAAiB,WAAW,CAC7G,CAAC;YACF,QACE,+EACE,OAAO,EAAE,IAAI,CAAC,IAAI,EAClB,KAAK,EAAE,KAAK,GACY,EAC1B;SACH;KACF;;;AAnCM;IAFN,SAAS,EAAE;0DAEkC;AAavC;IAFN,SAAS,EAAE;0DAEkC;;;;","names":[],"sources":["src/components/search/atomic-sort-expression/atomic-sort-expression.tsx"],"sourcesContent":["import {Component, Prop, Element, h} from '@stencil/core';\nimport {ArrayProp} from '../../../utils/props-utils';\n\n/**\n * The `atomic-sort-expression` component defines a sort expression. This component must be inside an `atomic-sort-dropdown` component.\n */\n@Component({\n  tag: 'atomic-sort-expression',\n  shadow: false,\n})\nexport class AtomicSortExpression {\n  @Element() public host!: HTMLElement;\n\n  /**\n   * The non-localized label to display for this expression.\n   */\n  @Prop({reflect: true}) public label!: string;\n\n  /**\n   * One or more sort criteria that the end user can select or toggle between.\n   *\n   * The available sort criteria are:\n   *\n   * * `relevancy`\n   * * `date ascending`/`date descending`\n   * * `qre`\n   * * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (e.g., `criteria=\"size ascending\"`).\n   *\n   * You can specify multiple sort criteria to be used in the same request by separating them with a comma (e.g., `criteria=\"size ascending, date ascending\"`).\n   */\n  @Prop({reflect: true}) public expression!: string;\n  /**\n   * The tabs on which the sort expression can be displayed. This property should not be used at the same time as `tabs-excluded`.\n   *\n   * Set this property as a stringified JSON array, e.g.,\n   * ```html\n   *  <atomic-sort-expression tabs-included='[\"tabIDA\", \"tabIDB\"]'></atomic-sort-expression snippet>\n   * ```\n   * If you don't set this property, the sort expression can be displayed on any tab. Otherwise, the sort expression can only be displayed on the specified tabs.\n   */\n  @ArrayProp()\n  @Prop({reflect: true, mutable: true})\n  public tabsIncluded: string[] | string = '[]';\n\n  /**\n   * The tabs on which the sort expression must not be displayed. This property should not be used at the same time as `tabs-included`.\n   *\n   * Set this property as a stringified JSON array, e.g.,\n   * ```html\n   *  <atomic-sort-expression tabs-excluded='[\"tabIDA\", \"tabIDB\"]'></atomic-sort-expression>\n   * ```\n   * If you don't set this property, the sort expression can be displayed on any tab. Otherwise, the sort expression won't be displayed on any of the specified tabs.\n   */\n  @ArrayProp()\n  @Prop({reflect: true, mutable: true})\n  public tabsExcluded: string[] | string = '[]';\n\n  public render() {\n    if (this.tabsIncluded.length > 0 && this.tabsExcluded.length > 0) {\n      console.warn(\n        'Values for both \"tabs-included\" and \"tabs-excluded\" have been provided. This is could lead to unexpected behaviors.'\n      );\n    }\n\n    const dropdownComponent = 'atomic-sort-dropdown';\n\n    if (!this.host.closest(dropdownComponent)) {\n      const error = new Error(\n        `The \"${this.host.nodeName.toLowerCase()}\" component has to be used inside an ${dropdownComponent} element.`\n      );\n      return (\n        <atomic-component-error\n          element={this.host}\n          error={error}\n        ></atomic-component-error>\n      );\n    }\n  }\n}\n"],"version":3}

package/dist/esm/version.js

@@ -1,2 +1,2 @@
-export const headlessVersion = '3.28.1-pre.7d360dc04c';
-export const atomicVersion = '3.32.1-pre.7d360dc04c';
+export const headlessVersion = '3.28.1-pre.85a5ccfeec';
+export const atomicVersion = '3.32.1-pre.85a5ccfeec';

package/dist/types/components/common/interface/interface-controller.d.ts

@@ -21,7 +21,7 @@ export declare class InterfaceController<EngineType extends AnyEngineType> imple
     private host;
     private i18nPromise;
     private hangingComponentsInitialization;
-    constructor(host: LitElement & BaseAtomicInterface<EngineType>, globalVariableName: string);
+    constructor(host: LitElement & BaseAtomicInterface<EngineType>, globalVariableName: string, headlessVersion: string);
     hostConnected(): void;
     hostDisconnected(): void;
     onComponentInitializing(event: InitializeEvent): void;

package/dist/types/components/search/atomic-sort-expression/atomic-sort-expression.d.ts

@@ -15,23 +15,9 @@ export declare class AtomicSortExpression {
      * * `relevancy`
      * * `date ascending`/`date descending`
      * * `qre`
-     * * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (`criteria="size ascending"`).
+     * * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (e.g., `criteria="size ascending"`).
      *
-     * You can specify multiple sort criteria to be used in the same request by separating them with a comma (`criteria="size ascending, date ascending"`).
-     *
-     * .Combining Sort Criteria
-     * [%collapsible]
-     * ====
-     * You can specify a list of comma-separated sort criteria which will be applied sequentially. For example, if there's a tie on the 1st criterion, the API uses the 2nd criterion to break the tie. However, this only works when combining:
-     * * a relevancy criterion followed by one or more field or date criteria.
-     * * a qre criterion followed by one or more field or date criteria.
-     * * two or more field criteria (`<FIELD>` descending, `<FIELD>` descending).
-     * * a single date criterion and one or more field criteria in any order (`<FIELD>` descending, date ascending).
-     * Examples:
-     * * `relevancy`, `<FIELD> descending`
-     * * `qre`, `<FIELD> ascending`
-     * * `date descending`, `<FIELD> descending`, `<FIELD> ascending`
-     * ====
+     * You can specify multiple sort criteria to be used in the same request by separating them with a comma (e.g., `criteria="size ascending, date ascending"`).
      */
     expression: string;
     /**

package/dist/types/components.d.ts

@@ -2731,7 +2731,7 @@ export namespace Components {
      */
     interface AtomicSortExpression {
         /**
-          * One or more sort criteria that the end user can select or toggle between.  The available sort criteria are:  * `relevancy` * `date ascending`/`date descending` * `qre` * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (`criteria="size ascending"`).  You can specify multiple sort criteria to be used in the same request by separating them with a comma (`criteria="size ascending, date ascending"`).  .Combining Sort Criteria [%collapsible] ==== You can specify a list of comma-separated sort criteria which will be applied sequentially. For example, if there's a tie on the 1st criterion, the API uses the 2nd criterion to break the tie. However, this only works when combining: * a relevancy criterion followed by one or more field or date criteria. * a qre criterion followed by one or more field or date criteria. * two or more field criteria (`<FIELD>` descending, `<FIELD>` descending). * a single date criterion and one or more field criteria in any order (`<FIELD>` descending, date ascending). Examples: * `relevancy`, `<FIELD> descending` * `qre`, `<FIELD> ascending` * `date descending`, `<FIELD> descending`, `<FIELD> ascending` ====
+          * One or more sort criteria that the end user can select or toggle between.  The available sort criteria are:  * `relevancy` * `date ascending`/`date descending` * `qre` * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (e.g., `criteria="size ascending"`).  You can specify multiple sort criteria to be used in the same request by separating them with a comma (e.g., `criteria="size ascending, date ascending"`).
          */
         "expression": string;
         /**
@@ -7289,7 +7289,7 @@ declare namespace LocalJSX {
      */
     interface AtomicSortExpression {
         /**
-          * One or more sort criteria that the end user can select or toggle between.  The available sort criteria are:  * `relevancy` * `date ascending`/`date descending` * `qre` * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (`criteria="size ascending"`).  You can specify multiple sort criteria to be used in the same request by separating them with a comma (`criteria="size ascending, date ascending"`).  .Combining Sort Criteria [%collapsible] ==== You can specify a list of comma-separated sort criteria which will be applied sequentially. For example, if there's a tie on the 1st criterion, the API uses the 2nd criterion to break the tie. However, this only works when combining: * a relevancy criterion followed by one or more field or date criteria. * a qre criterion followed by one or more field or date criteria. * two or more field criteria (`<FIELD>` descending, `<FIELD>` descending). * a single date criterion and one or more field criteria in any order (`<FIELD>` descending, date ascending). Examples: * `relevancy`, `<FIELD> descending` * `qre`, `<FIELD> ascending` * `date descending`, `<FIELD> descending`, `<FIELD> ascending` ====
+          * One or more sort criteria that the end user can select or toggle between.  The available sort criteria are:  * `relevancy` * `date ascending`/`date descending` * `qre` * `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (e.g., `criteria="size ascending"`).  You can specify multiple sort criteria to be used in the same request by separating them with a comma (e.g., `criteria="size ascending, date ascending"`).
          */
         "expression": string;
         /**

package/dist/types/global/environment.d.ts

@@ -1,4 +1,4 @@
-export interface AtomicEnvironment {
+interface AtomicEnvironment {
     version: string;
     headlessVersion: string;
 }
@@ -7,5 +7,7 @@ declare global {
         [anyGlobalVariable: string]: AtomicEnvironment;
     }
 }
-export declare function getAtomicEnvironment(): AtomicEnvironment;
-export declare function setCoveoGlobal(globalVariableName: string): void;
+export declare function getAtomicEnvironment(headlessVersion: string): AtomicEnvironment;
+export declare function getAtomicVersion(): string;
+export declare function setCoveoGlobal(globalVariableName: string, headlessVersion: string): void;
+export {};

package/docs/atomic-docs.json

@@ -1,5 +1,5 @@
 {
-  "timestamp": "2025-08-08T16:35:25",
+  "timestamp": "2025-08-11T13:09:20",
   "compiler": {
     "name": "@stencil/core",
     "version": "4.20.0",
@@ -14300,7 +14300,7 @@
           "mutable": false,
           "attr": "expression",
           "reflectToAttr": true,
-          "docs": "One or more sort criteria that the end user can select or toggle between.\n\nThe available sort criteria are:\n\n* `relevancy`\n* `date ascending`/`date descending`\n* `qre`\n* `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (`criteria=\"size ascending\"`).\n\nYou can specify multiple sort criteria to be used in the same request by separating them with a comma (`criteria=\"size ascending, date ascending\"`).\n\n.Combining Sort Criteria\n[%collapsible]\n====\nYou can specify a list of comma-separated sort criteria which will be applied sequentially. For example, if there's a tie on the 1st criterion, the API uses the 2nd criterion to break the tie. However, this only works when combining:\n* a relevancy criterion followed by one or more field or date criteria.\n* a qre criterion followed by one or more field or date criteria.\n* two or more field criteria (`<FIELD>` descending, `<FIELD>` descending).\n* a single date criterion and one or more field criteria in any order (`<FIELD>` descending, date ascending).\nExamples:\n* `relevancy`, `<FIELD> descending`\n* `qre`, `<FIELD> ascending`\n* `date descending`, `<FIELD> descending`, `<FIELD> ascending`\n====",
+          "docs": "One or more sort criteria that the end user can select or toggle between.\n\nThe available sort criteria are:\n\n* `relevancy`\n* `date ascending`/`date descending`\n* `qre`\n* `<FIELD> ascending`/`<FIELD> descending`, where you replace `<FIELD>` with the name of a sortable field in your index (e.g., `criteria=\"size ascending\"`).\n\nYou can specify multiple sort criteria to be used in the same request by separating them with a comma (e.g., `criteria=\"size ascending, date ascending\"`).",
           "docsTags": [],
           "values": [
             {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@coveo/atomic",
   "type": "module",
-  "version": "3.32.1-pre.7d360dc04c",
+  "version": "3.32.1-pre.85a5ccfeec",
   "description": "A web-component library for building modern UIs interfacing with the Coveo platform",
   "homepage": "https://docs.coveo.com/en/atomic/latest/",
   "repository": {
@@ -82,7 +82,7 @@
   },
   "dependencies": {
     "@coveo/bueno": "1.1.0",
-    "@coveo/headless": "3.28.1-pre.7d360dc04c",
+    "@coveo/headless": "3.28.1-pre.85a5ccfeec",
     "@lit/context": "1.1.6",
     "@popperjs/core": "2.11.8",
     "@salesforce-ux/design-system": "2.27.2",
@@ -169,7 +169,7 @@
   },
   "peerDependencies": {
     "@coveo/bueno": "1.1.0",
-    "@coveo/headless": "3.28.1-pre.7d360dc04c",
+    "@coveo/headless": "3.28.1-pre.85a5ccfeec",
     "typescript": ">=5.0.0"
   },
   "peerDependenciesMeta": {