@salesforce/ui-bundle-template-app-react-sample-b2x 12.4.1 → 12.4.3

package/dist/CHANGELOG.md

@@ -3,6 +3,23 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+## [12.4.3](https://github.com/salesforce-experience-platform-emu/webapps/compare/v12.4.2...v12.4.3) (2026-09-03)
+
+**Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project
+
+
+
+
+
+## [12.4.2](https://github.com/salesforce-experience-platform-emu/webapps/compare/v12.4.1...v12.4.2) (2026-09-02)
+
+
+### Bug Fixes
+
+* **ui-bundle:** use UI API GraphQL instead of Chatter for current-user lookup ([#951](https://github.com/salesforce-experience-platform-emu/webapps/issues/951)) ([47c28c1](https://github.com/salesforce-experience-platform-emu/webapps/commit/47c28c10a0b838eacef6c4a3e45e3a4fe587d20a))
+
+
+
 ## [12.4.1](https://github.com/salesforce-experience-platform-emu/webapps/compare/v12.4.0...v12.4.1) (2026-09-02)
 
 **Note:** Version bump only for package @salesforce/ui-bundle-template-base-sfdx-project

package/dist/README.md

@@ -330,6 +330,8 @@ cd -
 
 > **Prerequisite:** The org must be authenticated and metadata must already be deployed before running these commands, as the schema is generated from the org's live metadata.
 
+> **Guest and Portal GraphQL API Access requires an org preference** Starting with org release 264, unauthenticated (guest) sessions can only call the GraphQL API — the endpoint this app's data layer uses — if the **Enable GraphQL API for Guest Users** org preference is enabled. It is off by default. This is a security-sensitive, org-wide setting, so enable it through **Setup > Security > API Access Controls > Enable GraphQL API for Guest Users**. Enable it before configuring the guest user profile in [Step 4](#step-4-configure-the-guest-user-profile). Without it, guest GraphQL calls fail with `403 GUEST_INSUFFICIENT_ACCESS`. This applies to any b2b/b2c (external) app whose site allows guest browsing — not just this sample.
+
 ### 7. Rebuild the UI Bundle
 
 Step 6 updates the generated GraphQL types in the UI Bundle source. Rebuild the app to compile those changes into the bundle before deploying:
@@ -504,6 +506,8 @@ Open the guest user profile (linked from the site's Preferences page, as describ
 
 > **Security note:** Enabling API access for the guest profile is required for the UI Bundle to make GraphQL API calls on behalf of unauthenticated users. Ensure that object-level and field-level permissions are restrictive (as listed below) to avoid exposing sensitive data.
 
+> **Org preference (orgs on API v264+):** Profile-level "API Enabled" is not sufficient on its own. On orgs at API version 264 or later, guest sessions also need the org-wide **`GraphQLApiOrgPrefForGuestUsers`** preference enabled (**Setup > Security > API Access Controls > Enable GraphQL API for Guest Users**), or GraphQL calls from the guest user return `403 GUEST_INSUFFICIENT_ACCESS`. See the note in [Step 6](#6-generate-graphql-types).
+
 **Custom Object Permissions:**
 
 Guest users can only browse available properties and listings. All other objects are restricted.

package/dist/force-app/main/default/uiBundles/propertyrentalapp/package.json

@@ -19,8 +19,8 @@
     "graphql:schema": "node scripts/get-graphql-schema.mjs"
   },
   "dependencies": {
-    "@salesforce/platform-sdk": "^12.4.1",
-    "@salesforce/ui-bundle": "^12.4.1",
+    "@salesforce/platform-sdk": "^12.4.3",
+    "@salesforce/ui-bundle": "^12.4.3",
     "@tailwindcss/vite": "^4.1.17",
     "class-variance-authority": "^0.7.1",
     "clsx": "^2.1.1",
@@ -51,8 +51,8 @@
     "@graphql-eslint/eslint-plugin": "^4.1.0",
     "@graphql-tools/utils": "^11.0.0",
     "@playwright/test": "^1.49.0",
-    "@salesforce/graphiti": "^12.4.1",
-    "@salesforce/vite-plugin-ui-bundle": "^12.4.1",
+    "@salesforce/graphiti": "^12.4.3",
+    "@salesforce/vite-plugin-ui-bundle": "^12.4.3",
     "@testing-library/jest-dom": "^6.6.3",
     "@testing-library/react": "^16.1.0",
     "@testing-library/user-event": "^14.5.2",

package/dist/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/ui-bundle-template-base-sfdx-project",
-  "version": "12.4.1",
+  "version": "12.4.3",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/ui-bundle-template-base-sfdx-project",
-      "version": "12.4.1",
+      "version": "12.4.3",
       "license": "SEE LICENSE IN LICENSE.txt",
       "dependencies": {
         "fast-xml-parser": "^5.9.3",

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/ui-bundle-template-base-sfdx-project",
-  "version": "12.4.1",
+  "version": "12.4.3",
   "description": "Base SFDX project template",
   "license": "SEE LICENSE IN LICENSE.txt",
   "publishConfig": {

package/dist/scripts/org-setup-config-schema.mjs

@@ -72,8 +72,8 @@ export const ConfigSchema = z
         // Required because React (Site Container) sites hide SSO config in Admin UI.
         authProviderNames: z.array(z.string().min(1)).min(1),
         // Permission set to assign to community users created via SSO.
-        // Required because getCurrentUser() calls /chatter/users/me which needs
-        // API access (PermissionsApiEnabled) that the community profile lacks.
+        // Required because getCurrentUser() calls UI API GraphQL (uiapi.currentUser)
+        // which needs API access (PermissionsApiEnabled) that the community profile lacks.
         // Typically the app's "*_Guest_User_Api_Access" permset.
         communityUserPermset: z.string().min(1).optional(),
       })

package/dist/scripts/org-setup.mjs

@@ -546,7 +546,7 @@ function loadSelfRegConfig(config) {
  * - communityMemberProfile: profile added to NetworkMemberGroup (required for access)
  * - authProviderNames: DeveloperNames of AuthProvider (OAuth) or SamlSsoConfig (SAML) records to link to site
  * - communityUserPermset: permset assigned to community users so getCurrentUser()
- *   works (requires PermissionsApiEnabled for /chatter/users/me via /sf/api/)
+ *   works (requires PermissionsApiEnabled for UI API GraphQL via /sf/api/)
  *
  * Returns null if no "socialLogin" section exists in config (the step is hidden).
  */
@@ -937,7 +937,7 @@ function addCommunityMemberProfile(profileName, siteName, targetOrg) {
  * Assign a permission set to all existing community users with a given profile.
  *
  * After SSO login, community users need the app's API-enabled permset so that
- * getCurrentUser() (which calls /chatter/users/me via the /sf/api/ proxy) works.
+ * getCurrentUser() (which calls UI API GraphQL via the /sf/api/ proxy) works.
  * Without PermissionsApiEnabled the proxy returns API_DISABLED_FOR_ORG and the
  * React app treats the user as unauthenticated.
  *
@@ -2309,7 +2309,7 @@ async function main() {
       addCommunityMemberProfile(socialLoginConfig.communityMemberProfile, siteName, targetOrg);
 
       // Sub-step 4 (optional): Assign API-enabled permset to community users.
-      // Without this, getCurrentUser() fails because /chatter/users/me requires
+      // Without this, getCurrentUser() fails because UI API GraphQL requires
       // PermissionsApiEnabled which the standard community profile lacks.
       if (socialLoginConfig.communityUserPermset) {
         console.log(`  [4/${totalSubSteps}] Assigning API permset to community users...`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/ui-bundle-template-app-react-sample-b2x",
-  "version": "12.4.1",
+  "version": "12.4.3",
   "description": "Salesforce sample property rental React app",
   "license": "SEE LICENSE IN LICENSE.txt",
   "author": "",