Overview - @builder.io/sdks

@builder.io/sdks

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
ENG-11765_add_fetchTotalCount_to_getAll
2d736240 add fetchTotalCount param to getAll
1 day ago by Aishwarya ...
Failed
main
14dcf32b chore: bump version to 0.0.17 (#4329) ## Description Bumping up the version of `@builder.io/plugin-sfcc-commerce-api` plugin to 0.017 _Screenshot_ <img width="1278" height="548" alt="Screenshot 2026-03-02 at 2 33 38 PM" src="https://github.com/user-attachments/assets/aa2bd0d9-7bba-4630-9395-c79bddb90523" />  --- > [!NOTE] > **Low Risk** > Low risk: this is a pure version bump in `package.json`/`package-lock.json` with no code or dependency changes. > > **Overview** > Bumps `@builder.io/plugin-sfcc-commerce-api` from `0.0.16` to `0.0.17`, updating both `package.json` and `package-lock.json` accordingly. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit e68a23f884b68f8731d458f8000e116b4bd2b89e. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> 
10 days ago by Aishwarya ...
Succeeded
ENG-11447_sfcc_version_upgrade
92dad931 chore: bump version to 0.0.17
10 days ago by Aishwarya ...
Succeeded
main
7f704db6 fix[sfcc]: ENG-11447 surface specific auth errors and trim Einstein settings (#4306) ## Description When Salesforce rejects authentication (e.g. "redirect_uri doesn't match the registered redirects"), the specific error message from Salesforce was available in the server response but was being discarded in `validateConfig()`, which always threw the same generic string regardless of the actual failure reason. **Changes:** - `validateConfig()` now reads `response.errors[0].title` and appends the specific Salesforce reason to the error message shown to the user. - A second check is also added to catch a previously silent failure case where the server returns a { message } shaped response (e.g. when plugin settings are not found in Firestore). This was previously falling through without throwing any error. - Added `.trim()` when reading `einsteinId` and `einsteinSiteId` from settings, consistent with the existing pattern in the headless plugin. **JIRA Ticket:** https://builder-io.atlassian.net/browse/ENG-11447 **Testing:** https://www.notion.so/builderio/Testing-SFCC-Plugin-3173d7274be5802bb5fdd27ddd35ad86  --- > [!NOTE] > **Low Risk** > Low risk: limited to config validation and settings parsing, with no changes to core commerce read/search flows. Main risk is rejecting configs that previously passed due to stricter response handling. > > **Overview** > Improves Salesforce Commerce plugin config validation by treating both `errors[]` and unexpected `{ message }` responses as authentication failures, and logging the Salesforce-provided failure detail to aid debugging. > > Also trims whitespace from `einsteinId` and `einsteinSiteId` before deciding whether to enable Einstein recommenders, reducing failures caused by accidental spaces. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a395b32bf7c57adf32f6aaf67ca053614af5d493. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> 
10 days ago by Aishwarya ...
Succeeded
main
ecf0648e fix[sfcc]: ENG-11447 surface specific auth errors and trim Einstein settings (#4306) ## Description When Salesforce rejects authentication (e.g. "redirect_uri doesn't match the registered redirects"), the specific error message from Salesforce was available in the server response but was being discarded in `validateConfig()`, which always threw the same generic string regardless of the actual failure reason. **Changes:** - `validateConfig()` now reads `response.errors[0].title` and appends the specific Salesforce reason to the error message shown to the user. - A second check is also added to catch a previously silent failure case where the server returns a { message } shaped response (e.g. when plugin settings are not found in Firestore). This was previously falling through without throwing any error. - Added `.trim()` when reading `einsteinId` and `einsteinSiteId` from settings, consistent with the existing pattern in the headless plugin. **JIRA Ticket:** https://builder-io.atlassian.net/browse/ENG-11447 **Testing:** https://www.notion.so/builderio/Testing-SFCC-Plugin-3173d7274be5802bb5fdd27ddd35ad86  --- > [!NOTE] > **Low Risk** > Low risk: limited to config validation and settings parsing, with no changes to core commerce read/search flows. Main risk is rejecting configs that previously passed due to stricter response handling. > > **Overview** > Improves Salesforce Commerce plugin config validation by treating both `errors[]` and unexpected `{ message }` responses as authentication failures, and logging the Salesforce-provided failure detail to aid debugging. > > Also trims whitespace from `einsteinId` and `einsteinSiteId` before deciding whether to enable Einstein recommenders, reducing failures caused by accidental spaces. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a395b32bf7c57adf32f6aaf67ca053614af5d493. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> 
10 days ago by Aishwarya ...
Failed
ENG-11447_sfcc_version_upgrade
92dad931 chore: bump version to 0.0.17
10 days ago by Aishwarya ...
Failed
main
ecf0648e fix[sfcc]: ENG-11447 surface specific auth errors and trim Einstein settings (#4306) ## Description When Salesforce rejects authentication (e.g. "redirect_uri doesn't match the registered redirects"), the specific error message from Salesforce was available in the server response but was being discarded in `validateConfig()`, which always threw the same generic string regardless of the actual failure reason. **Changes:** - `validateConfig()` now reads `response.errors[0].title` and appends the specific Salesforce reason to the error message shown to the user. - A second check is also added to catch a previously silent failure case where the server returns a { message } shaped response (e.g. when plugin settings are not found in Firestore). This was previously falling through without throwing any error. - Added `.trim()` when reading `einsteinId` and `einsteinSiteId` from settings, consistent with the existing pattern in the headless plugin. **JIRA Ticket:** https://builder-io.atlassian.net/browse/ENG-11447 **Testing:** https://www.notion.so/builderio/Testing-SFCC-Plugin-3173d7274be5802bb5fdd27ddd35ad86  --- > [!NOTE] > **Low Risk** > Low risk: limited to config validation and settings parsing, with no changes to core commerce read/search flows. Main risk is rejecting configs that previously passed due to stricter response handling. > > **Overview** > Improves Salesforce Commerce plugin config validation by treating both `errors[]` and unexpected `{ message }` responses as authentication failures, and logging the Salesforce-provided failure detail to aid debugging. > > Also trims whitespace from `einsteinId` and `einsteinSiteId` before deciding whether to enable Einstein recommenders, reducing failures caused by accidental spaces. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit a395b32bf7c57adf32f6aaf67ca053614af5d493. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> 
10 days ago by Aishwarya ...
Succeeded
ENG-11447_sfcc_error_handling
d958952f code cleanup
10 days ago by Aishwarya ...