chore(deps): bump @salesforce/agents to 2.0.6 - #479
Conversation
520045f to
0e73073
Compare
|
Thanks for the contribution! Unfortunately we can't verify the commit author(s): Nico Pappagianis <n***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, refresh the status of this Pull Request. |
1 similar comment
|
Thanks for the contribution! Unfortunately we can't verify the commit author(s): Nico Pappagianis <n***@s***.com>. One possible solution is to add that email to your GitHub account. Alternatively you can change your commits to another email and force push the change. After getting your commits associated with your GitHub account, refresh the status of this Pull Request. |
c50f16a to
797dbaa
Compare
What
Bumps
@salesforce/agentsfrom^2.0.5to^2.0.6(package.json+yarn.lock).Why
@salesforce/agents@2.0.6ships the fix forsf agent publish authoring-bundlecrashing withTypeError: Cannot read properties of undefined (reading 'map')when the agent contains arelated_agentnode (compiled from an AgentScriptconnected_subagentblock, which has notoolsarray). This was blocking a customer from publishing an Orchestrator / multi-agent (Super Agent) via the CLI.@salesforce/agents@2.0.6is published and taggedlateston npm.Notes
yarn.lockentry was updated surgically (version, resolved, integrity).2.0.6introduces no new/changed transitive dependencies vs2.0.5, so no other lockfile entries change.