Skip to content

sf RNs: May 20, 2026 - agent preview/publish JWT fix #3557

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jshackell-sfdc merged 3 commits into from
May 14, 2026
Merged

sf RNs: May 20, 2026 - agent preview/publish JWT fix #3557

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8089db3
Add agent preview/publish JWT fix to 2.135.7 release notes
shetzel May 14, 2026
7388c63
chore: less details in the release note
shetzel May 14, 2026
be5847a
Fix command descriptions in release notes
jshackell-sfdc May 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions releasenotes/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,8 @@ These changes are in the Salesforce CLI release candidate. We plan to include th

* FIX: We are now correctly digitally signing all downloadable Salesforce CLI packages and executables. (GitHub Issue [#3547](https://github.com/forcedotcom/cli/issues/3547))

* FIX: (Agentforce DX) The `agent preview` and `agent publish authoring-bundle` commands no longer fail with HTTP 404 errors when user permissions are correct. The fix isolates connections used when calling server APIs, preventing token clobbering during connection refreshes. (plugin-agent PR [#421](https://github.com/salesforcecli/plugin-agent/pull/421), agents PR [#278](https://github.com/forcedotcom/agents/pull/278))

## 2.134.6 (May 13, 2026) [stable]

* NEW: Successfully run Apex tests in a scratch org that send emails to users with unverified email domains by setting the `EmailAuthorizationSettings.enableSubstituteFromAddress` field to `true` in your scratch org definition file. With this scratch org feature you can work around the [new Salesforce requirement](https://help.salesforce.com/s/articleView?id=005316090&type=1) that emails sent from Salesforce must have verified email domains. Here's an example of including this setting in a scratch org definition file.
Expand Down