Skip to content

Commit

Permalink
RNs 2024-08-21 (#2988)
Browse files Browse the repository at this point in the history
* chore: RNs 2024-08-21

* chore: small tweaks

* chore: indentation

* Update releasenotes/README.md

Co-authored-by: Shane McLaughlin <[email protected]>

* Update releasenotes/README.md

Co-authored-by: Shane McLaughlin <[email protected]>

* chore: indentation

---------

Co-authored-by: Shane McLaughlin <[email protected]>
  • Loading branch information
iowillhoit and mshanemc committed Aug 21, 2024
1 parent 1e9f431 commit 234f3b7
Showing 1 changed file with 56 additions and 7 deletions.
63 changes: 56 additions & 7 deletions releasenotes/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,14 +25,67 @@ Additional documentation:
* [Salesforce CLI Plugin Developer Guide](https://github.com/salesforcecli/cli/wiki/Quick-Introduction-to-Developing-sf-Plugins)
* [Salesforce CLI Setup Guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm)

## 2.55.6 (August 21, 2024) [stable-rc]
## 2.56.6 (August 28, 2024) [stable-rc]

**ANNOUNCEMENT:** Be sure you read [this pinned GitHub issue](https://github.com/forcedotcom/cli/issues/2974) about the upcoming removal of these commands: `force:source:*`, `force:mdapi:*`, `force:org:create`, and `force:org:delete`.

These changes are in the Salesforce CLI release candidate. We plan to include these changes in next week's official release. This list isn't final and is subject to change.

------------

* NEW: Try the new BETA `api request rest` command to send REST calls to your org! ([plugin-api repo](https://github.com/salesforcecli/plugin-api))

- `sf api request rest sobjects/account/<ID> --method PATCH --body "{\"Name\": \"Updated\"}"`
- `sf api request rest sobjects/account/<ID> --method PATCH --body body.txt`
- `cat body.txt | sf api request rest sobjects/account --body -`
- Stream results to a file with the `--stream-to-output` flag
- Run `sf api request rest --help` to see more examples

* CHANGE: We shipped `decomposeCustomLabelsBeta`, got [feedback](https://github.com/forcedotcom/cli/issues/2840) (thank you!), and decided to change how it behaves. You can see the design proposal [here](https://github.com/forcedotcom/cli/discussions/2948). It removes an extra folder layer that other decomposition strategies needed and supports more flexible folder structures.

Now there's `decomposeCustomLabeltsBeta2`. If you haven't used it yet, you can try it via `sf project convert source-behavior --behavior decomposeCustomLabelsBeta2`. This works if your project isn't using a preset OR if you started using the original flavor of `decomposeCustomLabeltsBeta`. Please keep the feedback coming! (source-deploy-retrieve PR [#1392](https://github.com/forcedotcom/source-deploy-retrieve/pull/1392))

* FIX: Salesforce DX projects now support the GenAiFunction [metadata type](https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json) (source-deploy-retrieve PR [#1404](https://github.com/forcedotcom/source-deploy-retrieve/pull/1404), plugin-deploy-retrieve PR [#1137](https://github.com/salesforcecli/plugin-deploy-retrieve/pull/1137))

* NEW: The `apex run test` and `apex get test` commands now have a new `--concise` flag

Setting this flag for `apex run test` or `apex get test` will suppress passing test results and the code coverage table. Only failing tests and the summary table will be displayed. (plugin-apex PR [#504](https://github.com/salesforcecli/plugin-apex/pull/504), Github Issue [#243](https://github.com/forcedotcom/salesforcedx-apex/issues/243), Github Discussion [#2872](https://github.com/forcedotcom/cli/discussions/2872))

Many thanks to [Kyle Capehart](https://github.com/k-capehart) for contributing this useful new flag!

* NEW: The `sf project convert source-behavior` command will now warn if you have uncommitted work before doing project modifications. Note that this command puts components in a newly created `main/default` folder in each package directory. You might need to re-organize them into your preferred structure. (plugin-deploy-retrieve PR [#1130](https://github.com/salesforcecli/plugin-deploy-retrieve/pull/1130))

* NEW: Check out the improved human readable output on the `org create scratch` and `org resume scratch` commands! They now take advantage of the new [@oclif/multi-stage-output](https://github.com/oclif/multi-stage-output) repo. Keep your eyes out for more multi-staged output improvements in the near future. (plugin-org PR [#1120](https://github.com/salesforcecli/plugin-org/pull/1120))

* FIX: Support for 21 new metadata types (source-deploy-retrieve PR [#1398](https://github.com/forcedotcom/source-deploy-retrieve/pull/1398))
* AssessmentConfiguration
* ContextUseCaseMapping
* ContractType
* DocumentTemplate
* EmployeeDataSyncProfile
* ExternalAuthIdentityProvider
* ExternalDataTranObject
* ExternalDocStorageConfig
* GenAiPlugin
* LearningAchievementConfig
* MktDataConnection
* MktDataConnectionSrcParam
* PortalDelegablePermissionSet
* ProductAttrDisplayConfig
* ProductSpecificationRecType
* ProductSpecificationType
* RecAlrtDataSrcExpSetDef
* ReferencedDashboard
* RelatedRecordAssocCriteria
* VirtualVisitConfig
* WaveAnalyticAssetCollection



## 2.55.6 (August 21, 2024) [stable]

**ANNOUNCEMENT:** Be sure you read [this pinned GitHub issue](https://github.com/forcedotcom/cli/issues/2974) about the upcoming removal of these commands: `force:source:*`, `force:mdapi:*`, `force:org:create`, and `force:org:delete`.

* NEW: Execute a SOSL text-based search query in your org with the new `data search` command. Similar to how the `data query` command works with SOQL queries, you can specify the SOSL query at the command line with the `--query` flag or read the query from a file with the `--file` flag. This example executes the specified SOSL query in an org with alias `my-scratch`:

```bash
Expand All @@ -43,19 +96,15 @@ These changes are in the Salesforce CLI release candidate. We plan to include th

* FIX: When parsing a scratch org definition file, Salesforce CLI now removes the `$schema` property (if it exists at the top of the JSON file) to prevent getting an invalid JSON error. (sfdx-core PR [#1113](https://github.com/forcedotcom/sfdx-core/pull/1113))

Thank you, Alan Jaouen[https://github.com/alanjaouen), for noticing the problem and then contributing the fix! We love it.
Thank you, [Alan Jaouen](https://github.com/alanjaouen), for noticing the problem and then contributing the fix! We love it.

* FIX: We now wait for config files to be unlocked before we read them. This improvement fixes issues like parallel command executions that cause file reads to return empty. (GitHub issue [#2965](https://github.com/forcedotcom/cli/issues/2965), sfdx-core PR [#1116](https://github.com/forcedotcom/sfdx-core/pull/1116))

* FIX: We updated the help and output of the `--package-name` flag of `project retrieve start` to clarify that the results are for reference only and shouldn't be used in your development work. (GitHub issue [#2931](https://github.com/forcedotcom/cli/issues/2931), plugin-deploy-retrieve [#1124](https://github.com/salesforcecli/plugin-deploy-retrieve/pull/1124))

* FIX: Salesforce DX projects now support the UiFormatSpecificationSet [metadata type](https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/registry/metadataRegistry.json).

## 2.54.6 (August 14, 2024) [stable]

**ANNOUNCEMENT:** Be sure you read [this pinned GitHub issue](https://github.com/forcedotcom/cli/issues/2974) about the upcoming removal of these commands: `force:source:*`, `force:mdapi:*`, `force:org:create`, and `force:org:delete`.

-----------------
## 2.54.6 (August 14, 2024)

* NEW: Salesforce CLI now automatically regenerates the autocomplete cache after you install or uninstall a plugin to ensure that the autocomplete feature is always using the latest set of CLI command and flag names. (plugin-autocomplete PR [#753](https://github.com/oclif/plugin-autocomplete/pull/753), oclif plugin-plugins PR [#932](https://github.com/oclif/plugin-plugins/pull/932))

Expand Down

0 comments on commit 234f3b7

Please sign in to comment.