-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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.
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
chore: Upgrade jsforce
to 3.6.2 and use jsforce-node
#18363
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Graphite Automations"Add consumer team as reviewer" took an action on this PR • (12/27/24)1 reviewer was added to this PR based on Keith Williams's automation. "Add foundation team as reviewer" took an action on this PR • (12/31/24)1 reviewer was added to this PR based on Keith Williams's automation. |
E2E results are ready! |
@zomars there's no tests specifically that test the library as we mock returns. I have been developing against this branch though and haven't run into any errors. |
Seems like we have a failure related with platform |
…into upgrade-jsforce-v3
I'm currently talking with @ThyMinimalDev and @emrysal about it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's goooo
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ |
What does this PR do?
Upgrades
jsforce
version from v1.11.0 to v3.6.3Uses
jsforce-node
. A more slimmed down version ofjsforce
without the browser specific bloatFixes #XXXX (GitHub issue number)
Fixes CAL-XXXX (Linear issue number - should be visible at the bottom of the GitHub issue description)
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
Checklist