feat: migrate from @salesforce/core v5 -> v6 #5332
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…rceApexTestRunCodeAction.ts
peternhale
requested changes
Jan 11, 2024
| @@ -10,9 +10,9 @@ | |||
| }, | |||
| "main": "out/src", | |||
| "dependencies": { | |||
| "@salesforce/core": "5.3.20", | |||
| "@salesforce/core": "6.4.3", | |||
There was a problem hiding this comment.
@daphne-sfdc please bump this to the most recent version of v6. I know its a moving target, but lets try to get this merged being as close to current as possible.
There was a problem hiding this comment.
Probably should visit all of the one to see if they have been bumped
…retrieve v10.2.5 -> v10.2.9
peternhale
approved these changes
Jan 11, 2024
mingxuanzhangsfdx
approved these changes
Jan 12, 2024
|
I tested it manually and it looks good. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Migrates @salesforce/core from v5.3.0 -> v6.4.7
This upgrade means we are able to support Core v6 in our other dependencies, so the following dependencies are also migrated from Core v5 -> v6 in this PR:
What issues does this PR fix or reference?
@W-14671437@
Functionality Before
Extensions monorepo uses v5 of @salesforce/core
Functionality After
Extensions monrepo uses v6 of @salesforce/core, which means we are now able to pull in new features from our shared libraries