To protect custom Lightning web components, the setting Use Lightning Web Security for Lightning web components is enabled by default in new Salesforce orgs. The new Lightning Web Security architecture is replacing Lightning Locker over several releases.

Where: This change applies to new Salesforce orgs that use Lightning Experience in all editions. The Lightning Web Security setting affects Lightning web components that are used in Aura-based Experience Cloud sites. It doesn’t affect LWR-based Experience Cloud sites.

Secure Components by Default with Lightning Web Security in New Orgs (salesforce.com)

This release update has been postponed indefinitely and not enforced in its present form. Don’t enable it.

Where: This change applies to Lightning Experience in Essentials, Professional, Enterprise, Performance, Unlimited, and Developer editions. Lightning console apps are available for an extra cost to users with Salesforce Platform user licenses for certain products. Some restrictions apply. For pricing details, contact your Salesforce account executive.

When: This update has been postponed indefinitely.

Keep Working with Tab-Focused Dialogs (Release Update) (salesforce.com)

The requirement to use multi-factor authentication (MFA) when accessing Salesforce products went into effect on February 1, 2022. All users must now use MFA when they log in to Salesforce, whether they’re logging in directly or using single sign-on (SSO). To help customers satisfy this requirement, in the first half of 2023, Salesforce is automatically enabling MFA for direct logins. In the September 2023 timeframe, we’re enforcing MFA by making it a permanent part of the Salesforce login process. To avoid disruptions to your users when these milestones occur, enable MFA as soon as possible.

Where: This change applies to Lightning Experience, Salesforce Classic, and all Salesforce mobile apps in all editions.

When: As of February 1, 2022, Salesforce customers are contractually required to use MFA when accessing Salesforce products, according to the Salesforce Trust and Compliance Documentation. For a subset of customers, a release update that automatically enables MFA for all direct Salesforce logins is available in Winter ’23 and takes effect when the Spring ’23 release rolls out. For all other customers, this release update applies in a later release. For more information, see MFA To Be Auto-Enabled for Some Customers in Spring ’23 (Release Update). To monitor the MFA enforcement milestone schedule, see the MFA Enforcement Roadmap.

How: To see if you’re affected by the MFA Auto-Enablement Release Update, monitor the Release Update node in Setup.

To implement and roll out MFA on your own:

• Check out the Multi-Factor Authentication Assistant. In Lightning Experience, from Setup, in the Quick Find box, enter MFA, and then select Multi-Factor Authentication Assistant.
• Get customizable templates for rollout planning and change management by downloading the MFA Rollout Pack.
• Make sure that your implementation satisfies the terms of the MFA requirement with the MFA Requirement Checker.

Be Ready for Multi-Factor Authentication Auto-Enablement (salesforce.com)

To help support your customers in Sierra Leone, the new leone (SLE) currency is available in Salesforce.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce mobile app in all editions.

To improve the Japanese katakana translation for foreign language words, we plan to replace the current Japanese Industrial Standards (JIS) style with the 1991 Cabinet Notification Directive style in Winter ’24.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the mobile app in all editions. Product documentation gets updated to use the new style starting in Winter ’24.

Prepare for the Japanese Katakana Style Change (salesforce.com)

To improve accuracy and your users’ experience, we updated the translations for some standard object, tab, and field names for these languages: Chinese (Simplified), Finnish, French, Italian, Japanese, Korean, Portuguese (Brazil), Spanish, Spanish (Mexico), and Romanian.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the mobile app in all editions.

How: To review the changes, see Winter ’23 Translated Terminology Update and download the attached list of changes. If you want to use a different translation for tab and field labels, you can change the name.

Review Updated Label Translations (salesforce.com)

Keep up to date with renamed time zones. Apia Daylight Time (GMT+14:00) is no longer observed, and four time zones are renamed.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce app in all editions, except Database.com.

Why: The Apia Daylight Time (Pacific/Apia) is removed. The name for these time zones changed.

Review Updated Time Zones (salesforce.com)

Stay up to date with the latest locale formats from International Components for Unicode (ICU) and Oracle’s Java Development Kit (JDK). Whether you use the ICU or the JDK format, we recommend that you evaluate how the changes affect you. This release includes ICU 71.1, which uses Common Locale Data Repository (CLDR) version 41, and JDK version 11, which uses CDLR version 33.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce app in all editions, except Database.com.

How: Review the changes to date, time, name, and currency formats for the locales that you use in Salesforce and evaluate how they affect you. Then test your filters, code, and components as needed.

Prepare for Locale Format Changes (salesforce.com)

To conduct business wherever you are, adopt the International Components for Unicode (ICU) locale formats. Locales control the formats for dates, times, currencies, addresses, names, and numeric values. ICU sets the international standard for these formats. The ICU locale formats provide a consistent experience across the platform and improve integration with ICU-compliant applications across the globe. When you enable this update, the ICU locale formats replace Oracle’s Java Development Kit (JDK) locale formats in Salesforce. This update was first made available in Winter ’20.

Where: This change applies to Lightning Experience, Salesforce Classic, and all versions of the Salesforce mobile app in all editions, except Database.com.

When: Salesforce enforces this update in Spring ’24. Salesforce orgs created in Winter ’20 or later have ICU locale formats enabled by default. To get the major release upgrade date for your instance, go to Trust Status, search for your instance, and click the maintenance tab.

How: To enable this update, from Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. For Enable ICU Locale Formats, follow the testing and activation steps.

The English (Canada) locale (en_CA) requires separate activation. From Setup, in the Quick Find box, enter User Interface, and select User Interface. Then select Enable ICU formats for en_CA locale, and save your changes.

Enable ICU Locale Formats (Release Update) (salesforce.com)

Stay up to date with the latest locale formats and time zones. Prepare for a new style for Japanese katakana. And the new leone is available as a currency.

• Enable ICU Locale Formats (Release Update)
  To conduct business wherever you are, adopt the International Components for Unicode (ICU) locale formats. Locales control the formats for dates, times, currencies, addresses, names, and numeric values. ICU sets the international standard for these formats. The ICU locale formats provide a consistent experience across the platform and improve integration with ICU-compliant applications across the globe. When you enable this update, the ICU locale formats replace Oracle’s Java Development Kit (JDK) locale formats in Salesforce. This update was first made available in Winter ’20.
• Prepare for Locale Format Changes
  Stay up to date with the latest locale formats from International Components for Unicode (ICU) and Oracle’s Java Development Kit (JDK). Whether you use the ICU or the JDK format, we recommend that you evaluate how the changes affect you. This release includes ICU 71.1, which uses Common Locale Data Repository (CLDR) version 41, and JDK version 11, which uses CDLR version 33.
• Review Updated Time Zones
  Keep up to date with renamed time zones. Apia Daylight Time (GMT+14:00) is no longer observed, and four time zones are renamed.
• Review Updated Label Translations
  To improve accuracy and your users’ experience, we updated the translations for some standard object, tab, and field names for these languages: Chinese (Simplified), Finnish, French, Italian, Japanese, Korean, Portuguese (Brazil), Spanish, Spanish (Mexico), and Romanian.
• Prepare for the Japanese Katakana Style Change
  To improve the Japanese katakana translation for foreign language words, we plan to replace the current Japanese Industrial Standards (JIS) style with the 1991 Cabinet Notification Directive style in Winter ’24.
• Conduct Business with the New Leone
  To help support your customers in Sierra Leone, the new leone (SLE) currency is available in Salesforce.

Globalization (salesforce.com)