Add support for shopper/admin attributes, bundle min/max, catalog rule validation and pricebook segmentation

[field123]

Tracking issue for bringing the legacy SDK in line with recent additions to the upstream PIM (pim.yaml) and shopper Catalog View (catalog_view.yaml) OpenAPI specs.

In scope

From pim.yaml (admin / PXM)

• shopper_attributes / admin_attributes on PcmProductBase (already on hierarchies and nodes)
• Per-option min / max on ProductComponentOption
• columns.include parameter on ExportProducts (POST /pcm/products/export)

From catalog_view.yaml (shopper / catalog)

• Validate method on CatalogsRulesEndpoint (POST /catalogs/rules/validate) with match_type of filter | similarity | conflict | resolve_for_shopper
• pricebook_ids operator on RuleFilter and pricebook_ids on RuleBase.attributes
• available_prices, alternative_prices, available_pricebook_ids on ProductResponse.attributes (plus alternative_prices on component_products meta)
• ReleaseIndexingCompleteData type ({ data: { status: 'succeeded' | 'failed' } })

Out of scope (potential follow-up)

• Threading the EP-Pricebook-IDs-Of-Available-Prices-To-Show request header through Catalog / Catalogs.Products methods. The request factory already supports additionalHeaders, so this is a small follow-up if consumers need it — but it touches every product-facing method, so worth a separate PR.

References

• Upstream regen of the generated SDKs: chore(sdks): regenerate pxm and shopper SDKs from updated specs composable-frontend#523

[github-actions]

🎉 This issue has been resolved in version 33.6.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀