Release v6.5.0 for ECOM v26.8 (@W-23614477@)

[joeluong-sfcc]

Summary

• Update all APIs to the ECOM v26.8 pinned versions per the api-manager release/26.8 pom.
• Includes the previously-unreleased Bug Fixes now shipping under v6.5.0: the CDN Zones spec generation fix (unblocking zones-oas v1.3.0) and the auto-publish-on-merge fix.

API Versions

API Name	API Version
assignments	1.0.38
slas-admin	1.18.0
shopper-login	1.50.0
campaigns	1.0.40
catalogs	1.0.46
cors-preferences	1.1.0
coupons	1.0.43
customers	1.1.3
gift-certificates	1.0.42
orders	1.5.2
preferences	1.2.2
products	1.2.0
promotions	1.0.36
shopper-availability	1.3.0
shopper-baskets	1.11.0
shopper-baskets	2.11.1
shopper-configurations	1.3.0
shopper-consents	1.1.4
shopper-context	1.1.3
shopper-customers	1.8.0
shopper-experience	1.6.0
shopper-gift-certificates	1.2.0
shopper-orders	1.17.1
shopper-products	1.11.1
shopper-promotions	1.3.0
shopper-search	1.10.0
shopper-seo	1.2.0
shopper-stores	1.3.0
source-code-groups	1.0.40
cdn-api-process-apis	1.3.0

Test plan

• npm run updateApis succeeded — apis/ matches api-versions.txt (30 folders), all 11 bumped exchange.json versions verified, no *-internal.yaml leaked, diff report shows 0 endpoint removals.
• npm run build (clean + renderTemplates + compile) produced clean output; only the pre-existing auth-oas form-parameter generator warnings.
• npm test passed: lint, depcheck, 53 unit tests, 21 release-workflow tests — all green.
• npm run doc regenerated the CHANGELOG v6.5.0 API Versions table and the typedoc HTML under docs/; docs/CHANGELOG.md matches root byte-for-byte.
• Spot-checked the zones (cdn-api-process-apis 1.3.0) and shopper-orders (1.17.1) generated output to confirm the new endpoints surfaced.

Ticket

W-23614477

[vcua-mobify]

LGTM

Small nit from claude about a changelog entry but its non-blocking:

Non-blocking observations

zones-oas type renames (heads-up, not a blocker). The large zones churn (+1527/−808) is mostly re-tagging and additive Turnstile types, but two generated types changed name/disappeared: ApiStandardsErrorResponse → ErrorResponse, and a capitalized OrganizationId type was dropped (lowercase param retained). For strict TS consumers importing those exact type names from the CDN Zones module, that's technically a breaking rename. It's upstream-spec-driven and lands in an API that was previously blocked from generating (the whole point of the CDN Zones fix shipping here), so the practical blast radius is near-zero — but worth being aware of, and it's arguably worth a one-line note in the changelog's Bug Fixes if you want to be thorough.