-
Notifications
You must be signed in to change notification settings - Fork 393
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
Ra/upgrade core v3 to v4 #5001
Ra/upgrade core v3 to v4 #5001
Conversation
packages/salesforcedx-sobjects-faux-generator/test/unit/sObjectMockData.ts
Show resolved
Hide resolved
packages/salesforcedx-utils-vscode/test/unit/helpers/traceFlagsRemover.test.ts
Show resolved
Hide resolved
...alesforcedx-vscode-apex-replay-debugger/test/vscode-integration/commands/quickLaunch.test.ts
Show resolved
Hide resolved
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.
LGTM. Only thing I suggest is making sure we have a WI in the backlog to ensure we get back to getting the number packaged version of core/templates back to 1 (reducing the size of the vsix files)
This upgrade has increased our vsixes by 6.5MB I will create a WI to keep track of versions of salesforce/templates and heroku/core-functions dependencies. |
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.
Since build and tests are passing, ✅
Nice work on this Ritam!! 🏆
What does this PR do?
What issues does this PR fix or reference?
@W-13577566@
Functionality Before
Extensions were using salesforce/core version 3
Functionality After
Extensions are using salesforce/core version 4