Are you an LLM? You can read better optimized documentation at /docs/basics/changelog/releases/2026-06-10.md for this page in Markdown format
June 10, 2026
- Web: 1.6.11
- CLI: 3.7.20
- Cloud: 2.13.15
New features
- Web: More sandbox options when creating an environment — the "create environment" dialog now lets you clone the sandbox from another sandbox environment, instead of always from the production environment. Additionally, this dialog now lets you select an Apex class to run after the sandbox is activated and, for full sandboxes, choose how much object history to copy and whether to copy Chatter data. These options were previously only available in the CLI.
Improvements
- Web: Creating a new user account now requires email address verification for improved security. Existing users will also be asked to confirm their email address on their next sign-in.
- Web: Usability and accessibility of forms have been improved. Submit buttons on forms now remain clickable even while the form is still incomplete or invalid, making it easier to discover what needs to be corrected.
- XML-based merge now automatically resolves conflicts where the same element was added or modified identically on both sides of a merge.
- XML-based merge now aligns multiple same-named elements by their identifying content instead of only by position. This dramatically reduces conflicts when entries are inserted, deleted or reordered in large metadata files such as permission sets and profiles — a merge that previously produced hundreds of small conflicts can now produce only a handful or none.
Fixes
- Fixes an issue where
Date/Timefields in exported JSON files could not be round-tripped back into a subsequent import operation. JSON files can now be used to reliably round-trip Salesforce data, includingDate/Timefields. - Fixes an issue where XML-based merge could ignore some cases of significant whitespace-only changes.
- Fixes an issue where a merge could fail when XML-based merge was enabled and a metadata file could not be parsed as XML (for example because it was malformed or used an unsupported character encoding). Such files now automatically fall back to Git's text-based merge instead of failing the merge, and the path of any file that could not be parsed as XML is reported in the worker log.