sf-decomposer 5.3.9 → 5.3.11

package/CHANGELOG.md

@@ -5,6 +5,21 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [5.3.11](https://github.com/mcarvin8/sf-decomposer/compare/v5.3.10...v5.3.11) (2025-02-24)
+
+
+### Bug Fixes
+
+* **deps:** bump @salesforce/source-deploy-retrieve ([bbd3ec4](https://github.com/mcarvin8/sf-decomposer/commit/bbd3ec4a807ef9277aec4e8e22b58c4e4820be61))
+* **deps:** bump the xml-disassemblers group across 1 directory with 3 updates ([8b9966f](https://github.com/mcarvin8/sf-decomposer/commit/8b9966f071666c56f19851eb4962ccc1424b0ba0))
+
+## [5.3.10](https://github.com/mcarvin8/sf-decomposer/compare/v5.3.9...v5.3.10) (2025-02-16)
+
+
+### Bug Fixes
+
+* **deps:** bump @salesforce/source-deploy-retrieve ([38a9946](https://github.com/mcarvin8/sf-decomposer/commit/38a9946f306cac16537fd19d95fadb8fe00e25bb))
+
 ## [5.3.9](https://github.com/mcarvin8/sf-decomposer/compare/v5.3.8...v5.3.9) (2025-02-10)
 
 

package/README.md

@@ -7,18 +7,19 @@
   <summary>Table of Contents</summary>
 
 - [Install](#install)
-- [Why Use This Plugin?](#why-use-this-plugin)
+- [Why SF Decomposer](#why-sf-decomposer)
 - [Commands](#commands)
   - [`sf decomposer decompose`](#sf-decomposer-decompose)
   - [`sf decomposer recompose`](#sf-decomposer-recompose)
+- [Decompose Structure](#decompose-structure)
 - [Supported Metadata](#supported-metadata)
   - [Metadata Exceptions](#metadata-exceptions)
 - [Debugging](#debugging)
-- [Ignore Files when Decomposing](#ignore-files-when-decomposing)
 - [Hooks](#hooks)
 - [Ignore Files](#ignore-files)
-  - [`.forceignore` updates](#.forceignore-updates)
-  - [`.gitignore` updates](#.gitignore-updates)
+  - [`.forceignore`](#.forceignore)
+  - [`.sfdecomposerignore`](#.sfdecomposerignore)
+  - [`.gitignore`](#.gitignore)
 - [Contributing](#contributing)
 - [Issues](#issues)
 - [License](#license)
@@ -26,28 +27,21 @@
 
 A Salesforce CLI plugin to break down large metadata files into smaller, more manageable files for version control and then recreate deployment-compatible files.
 
-**DISCLAIMERS:**
-
-- You must update the `.forceignore` to have the Salesforce CLI ignore the decomposed files created by this plugin. See [Ignore Files](#ignore-files).
-- It is recommended that you extensively test this plugin in a sandbox environment on the metadata types for which you wish to use this tool.
-- Do not change your production/QA pipelines until you have tested this and are happy with the results.
-- Ensure your deployment pipelines are stable before implementing this plugin.
-
 ## Install
 
 ```bash
 sf plugins install sf-decomposer@x.y.z
 ```
 
-## Why Use this Plugin?
+## Why SF Decomposer
 
-Why should you consider using this Salesforce CLI Plugin over Salesforce's decomposition?
+Why should you consider using `sf-decomposer` over Salesforce's decomposition?
 
-- Salesforce's decomposition betas are evaluated for each metadata type before they are considered. My plugin supports the vast majority of Salesforce metadata types available from the Metadata API.
-- Salesforce's decomposition is all or nothing for each metadata type. Meaning, if you want to decompose workflows, all of your workflows will need to be decomposed to work with Salesforce's approach. My plugin allows you to selectively decompose for each metadata type.
-  - See [Ignore Files when Decomposing](#ignore-files-when-decomposing)
-- Some metadata types may only be partially decomposed by Salesforce such as permission sets based on what designs are picked. My plugin will allow for total decomposition. So if a user wants to fully decompose permission sets, they can use this plugin.
-- When this plugin recomposes the decomposed files, it will sort the elements consistently compared to native Salesforce files.
+- Salesforce's decomposition betas are evaluated for each metadata type before they are considered. `sf-decomposer` supports the vast majority of Salesforce metadata types available from the Metadata API.
+- Salesforce's decomposition is all or nothing for each metadata type. Meaning, if you want to decompose workflows, all of your workflows will need to be decomposed to work with Salesforce's approach. `sf-decomposer` allows you to selectively decompose for each metadata type.
+  - See [.sfdecomposerignore](#.sfdecomposerignore)
+- Some metadata types may only be partially decomposed by Salesforce such as permission sets based on what designs are picked. `sf-decomposer` will allow for total decomposition. So if a user wants to fully decompose permission sets, they can use this plugin.
+- When `sf-decomposer` recomposes the decomposed files, it will sort the elements consistently compared to native Salesforce files.
 
 ## Commands
 
@@ -60,40 +54,25 @@ The `sf-decomposer` supports 2 commands:
 
 Decomposes the original metadata files in all local package directories into smaller files for version control. 
 
-When the files are decomposed, it will:
-- decompose leaf elements (i.e. `<userLicense>Salesforce</userLicense>`) in the same file. The leaf file-name will match the original file-name, just in a decomposed directory.
-- decompose nested elements into their own files.
-  - If unique ID elements are found, the decomposed files will be named using them.
-  - Otherwise, the decomposed files will be named with the SHA-256 hash of the element contents.
-  - See [Contributing](#contributing) for more information on unique ID elements.
-
-<img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-perm-set.png">
-<p><em>Decomposed Permission Sets named using unique ID elements</em></p>
-
-<br>
-
-<img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-labels.png" alt="Description"> 
-<p><em>Decomposed Custom Labels named using unique ID elements</em></p>
-
-<br>
-
-<img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-apps-hashes.png">
-<p><em>Decomposed Application named using SHA-256 hashes of elements</em></p>
-
-<br>
-
 ```
 USAGE
   $ sf decomposer decompose -m <value> -f <value> -i <value> [--prepurge --postpurge --debug --json]
 
 FLAGS
-  -m, --metadata-type=<value>             The metadata suffix to process, such as 'flow', 'labels', etc. You can provide this flag multiple times.
-  -f, --format=<value>                    [default: 'xml'] The file type for the decomposed files. Must match what format you provide for recompose.
-  -i, --ignore-package-directory=<value>  Package directories to ignore. Should be as they appear in the "sfdx-project.json" file.
+  -m, --metadata-type=<value>             The metadata suffix to process, such as 'flow', 'labels', etc. 
                                           Can be declared multiple times.
-  --prepurge                              [default: false] If provided, purge directories of pre-existing decomposed files.
-  --postpurge                             [default: false] If provided, purge the original files after decomposing them.
-  --debug                                 [default: false] If provided, log debugging results to a text file (disassemble.log).
+  -f, --format=<value>                    The file type for the decomposed files. 
+                                          Must match what format you provide for recompose.
+                                          [default: 'xml']
+  -i, --ignore-package-directory=<value>  Package directory to ignore.
+                                          Should be as they appear in the "sfdx-project.json".
+                                          Can be declared multiple times.
+  --prepurge                              Purgd directories of pre-existing decomposed files.
+                                          [default: false] 
+  --postpurge                             Purge the original files after decomposing them.
+                                          [default: false] 
+  --debug                                 Log debugging results to a text file (disassemble.log).
+                                          [default: false] 
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -127,12 +106,18 @@ USAGE
   $ sf decomposer recompose -m <value> -f <value> -i <value> [--postpurge --debug --json]
 
 FLAGS
-  -m, --metadata-type=<value>               The metadata suffix to process, such as 'flow', 'labels', etc. You can provide this flag multiple times.
-  -f, --format=<value>                      [default: 'xml'] The file format for the decomposed files.
-  -i, --ignore-package-directory=<value>    Package directories to ignore. Should be as they appear in the "sfdx-project.json" file.
+  -m, --metadata-type=<value>               The metadata suffix to process, such as 'flow', 'labels', etc. 
+                                            Can be declared multiple times.
+  -f, --format=<value>                      The file format for the decomposed files.
+                                            Must match what format you provide for decompose.
+                                            [default: 'xml']
+  -i, --ignore-package-directory=<value>    Package directory to ignore. 
+                                            Should be as they appear in the "sfdx-project.json".
                                             Can be declared multiple times.
-  --postpurge                               [default: false] If provided, purge the decomposed files after recomposing them.
-  --debug                                   [default: false] If provided, log debugging results to a text file (disassemble.log).
+  --postpurge                               Purge the decomposed files after recomposing them.
+                                            [default: false]
+  --debug                                   Log debugging results to a text file (disassemble.log).
+                                            [default: false]
 
 GLOBAL FLAGS
   --json  Format output as json.
@@ -157,6 +142,29 @@ EXAMPLES
 
 ```
 
+## Decompose Structure
+
+When the original metadata files are decomposed, this structure is followed for all metadata types except for custom labels:
+
+- Leaf elements (i.e. `<userLicense>Salesforce</userLicense>`) will be decomposed in the same file in the root of the decomposed directory. The leaf file-name will match the original file-name.
+- Nested elements will be decomposed into their own files under sub-directories by the element type, i.e. custom permissions in a permission set will have their own decomposed file under a custom permissions sub-folder. 
+  - If unique ID elements are found, the decomposed nested files will be named using them.
+  - Otherwise, the decomposed nested files will be named with the SHA-256 hash of the element contents.
+  - See [Contributing](#contributing) for more information on unique ID elements.
+
+<img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-perm-set.png">
+<p><em>Decomposed Permission Sets named using unique ID elements</em></p>
+
+<br>
+
+<img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-apps-hashes.png">
+<p><em>Decomposed Application named using SHA-256 hashes of elements</em></p>
+
+When custom labels are decomposed, each custom label will have its own file in the original labels directory.
+
+<img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-labels.png" alt="Description"> 
+<p><em>Decomposed Custom Labels</em></p>
+
 ## Supported Metadata
 
 All metadata types imported from this plugin's version of `@salesforce/source-deploy-retrieve` (SDR) toolkit are supported except for certain types.
@@ -196,13 +204,13 @@ Here are some examples:
 
 ## Debugging
 
-The plugin searches the current working directory for the `sfdx-project.json`, and if it's not found in the current working directory, it will search upwards for it until it hits your root drive. If the `sfdx-project.json` file isn't found, the plugin will fail with:
+`sf-decomposer` searches the current working directory for the `sfdx-project.json`, and if it's not found in the current working directory, it will search upwards for it until it hits your root drive. If the `sfdx-project.json` file isn't found, the plugin will fail with:
 
 ```
 Error (1): sfdx-project.json not found in any parent directory.
 ```
 
-The xml-disassembler package will log errors, and optionally debugging statements, to a log file, `disassemble.log`. This log will be created in the working directory and will be created when running this plugin at all times. If there were no errors, this log will be empty. By default, the log will only contain errors. This plugin will print the errors as warnings in the command terminal to allow all other files to be processed. These warnings when decomposing or recomposing will look like:
+The `xml-disassembler` package will log errors, and optionally debugging statements, to a log file, `disassemble.log`. This log will be created in the working directory and will be created when running this plugin at all times. If there were no errors, this log will be empty. By default, the log will only contain errors. This plugin will print the errors as warnings in the command terminal to allow all other files to be processed. These warnings when decomposing or recomposing will look like:
 
 ```
 Warning: C:\Users\matth\Documents\sf-decomposer\test\baselines\flows\Get_Info\actionCalls\Get_Info.actionCalls-meta.xml was unabled to be parsed and will not be processed. Confirm formatting and try again.
@@ -216,21 +224,9 @@ To add additional debugging statements to the log file, provide the `--debug` fl
 
 Recommend adding the `disassemble.log` to your `.gitignore` file if you are using this in a git-based repo.
 
-## Ignore Files when Decomposing
-
-If you wish, you can create an ignore file in the root of your repository named `.sfdecomposerignore` to ignore specific XMLs when running the decompose command. The ignore file should follow [.gitignore spec 2.22.1](https://git-scm.com/docs/gitignore).
-
-When the decompose command is ran with the `--debug` flag and it processes a file that matches an entry in `.sfdecomposerignore`, a warning will be printed to the `disassemble.log`:
-
-```
-[2024-05-22T09:32:12.078] [WARN] default - File ignored by .sfdecomposerignore: C:\Users\matth\Documents\sf-decomposer\test\baselines\bots\Assessment_Bot\v1.botVersion-meta.xml
-```
-
-The ignore file is not read by the recompose command.
-
 ## Hooks
 
-**NOTE:** In order to avoid errors during the retrieval, you must configure your `.forceignore` file to have the Salesforce CLI ignore the decomposed files. See [Ignore Files](#ignore-files) section.
+> **NOTE:** In order to avoid errors during the retrieval, you must configure your `.forceignore` file to have the Salesforce CLI ignore the decomposed files. See [Ignore Files](#ignore-files) section.
 
 A post-retrieve hook (for the decompose command) and a pre-run hook (for the recompose command) have been configured if you elect to use them. The post-retrieve hook will automatically decompose the desired metadata types after every Salesforce CLI retrieval (`sf project retrieve start` command). The pre-run hook will automatically recompose the desired metadata types before every Salesforce CLI deployment/validation (`sf project deploy start` and `sf project deploy validate` commands).
 
@@ -246,15 +242,27 @@ If the `.sfdecomposer.config.json` file isn't found, the hooks will be skipped.
 
 ## Ignore Files
 
-### `.forceignore` updates
+### `.forceignore`
 
 The Salesforce CLI **must** ignore the decomposed files and allow the recomposed files.
 
 You can use the sample [.forceignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.forceignore) provided. Update the decomposed file extensions based on what format you're using (`.xml`, `.json`, or `.yaml`).
 
-### `.gitignore` updates
+### `.sfdecomposerignore`
+
+If you wish, you can create a `.sfdecomposerignore` file in the root of your repository to ignore specific XMLs when running the decompose command. The `.sfdecomposerignore` file should follow [.gitignore spec 2.22.1](https://git-scm.com/docs/gitignore).
+
+When the decompose command is ran with the `--debug` flag and it processes a file that matches an entry in `.sfdecomposerignore`, a warning will be printed to the `disassemble.log`:
+
+```
+[2024-05-22T09:32:12.078] [WARN] default - File ignored by .sfdecomposerignore: C:\Users\matth\Documents\sf-decomposer\test\baselines\bots\Assessment_Bot\v1.botVersion-meta.xml
+```
+
+`.sfdecomposerignore` is not read by the recompose command.
+
+### `.gitignore`
 
-Optionally, Git (or whatever version control system you are using) can ignore the recomposed files so you don't stage those in your repositories. You can also ignore the log created by the disassembler package.
+Optionally, Git (or whatever version control system you are using) can ignore the recomposed files so you don't stage those in your repositories. You can also have git ignore the `disassemble.log` created by the `xml-disassembler` package.
 
 You can use the sample [.gitignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.gitignore) provided.
 
@@ -264,7 +272,7 @@ Contributions are welcome! See [Contributing](https://github.com/mcarvin8/sf-dec
 
 ## Issues
 
-If you encounter any issues, please create an issue in the repository's [issue tracker](https://github.com/mcarvin8/sf-decomposer/issues). Please also create issues for feature enhancements or to support newer metadata types added to the [SDR toolkit](https://github.com/forcedotcom/source-deploy-retrieve).
+If you encounter any bugs or would like to request features, please create an [issue](https://github.com/mcarvin8/sf-decomposer/issues).
 
 ## License
 

package/messages/decomposer.decompose.md

@@ -16,19 +16,19 @@ You should run this after you retrieve metadata from an org.
 
 # flags.metadata-type.summary
 
-The metadata suffix to process, such as 'flow', 'labels', etc. You can provide this flag multiple times to process multiple metadata types with a single command.
+The metadata suffix to process, such as 'flow', 'labels', etc.
 
 # flags.prepurge.summary
 
-If provided, purge directories of pre-existing decomposed files.
+Purge directories of pre-existing decomposed files.
 
 # flags.postpurge.summary
 
-If provided, purge the original files after decomposing them.
+Purge the original files after decomposing them.
 
 # flags.debug.summary
 
-If provided, debug to a log file.
+Debug to a log file.
 
 # flags.format.summary
 

package/messages/decomposer.recompose.md

@@ -16,15 +16,15 @@ You should run this before you deploy decomposed metadata to an org.
 
 # flags.metadata-type.summary
 
-The metadata suffix to process, such as 'flow', 'labels', etc. You can provide this flag multiple times to process multiple metadata types with a single command.
+The metadata suffix to process, such as 'flow', 'labels', etc.
 
 # flags.postpurge.summary
 
-If provided, purge the decomposed files after recomposing them.
+Purge the decomposed files after recomposing them.
 
 # flags.debug.summary
 
-If provided, debug to a log file.
+Debug to a log file.
 
 # flags.format.summary
 

package/oclif.lock

@@ -1596,10 +1596,10 @@
     string-width "^7.2.0"
     terminal-link "^3.0.0"
 
-"@salesforce/source-deploy-retrieve@^12.14.6":
-  version "12.14.6"
-  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.14.6.tgz#19fee9916619cac38d4b703de3ad9eba10343143"
-  integrity sha512-7a9tzVmRhuja1w05zhW/UpoViA5xYXJGsZlSjAqOPHH5n4e2/q9Q+XeOb2kfusOr34oEHoU+YFcsZXWc9hu0SA==
+"@salesforce/source-deploy-retrieve@^12.15.1":
+  version "12.15.1"
+  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.15.1.tgz#72e86cf950a7abf0b5f2d1b1b4db88260d41b426"
+  integrity sha512-wJRdTYMv8W/W4Y5ml7V2uW9/drS34My0y4CB9I+eaR1pls9a6QorAa5NgFYoi5Re+UuiojOcIUNGuKKvsA4Wbg==
   dependencies:
     "@salesforce/core" "^8.8.2"
     "@salesforce/kit" "^3.2.3"
@@ -4112,6 +4112,13 @@ fast-xml-parser@^4.5.1:
   dependencies:
     strnum "^1.0.5"
 
+fast-xml-parser@^5.0.6:
+  version "5.0.6"
+  resolved "https://registry.yarnpkg.com/fast-xml-parser/-/fast-xml-parser-5.0.6.tgz#3531c630ea334bd67b91f236117fbf439a19b21f"
+  integrity sha512-5zIl0jWsewL5LdneswG6aJXx1YH1FXQ02UVIe/CZI3wXhI3SqP62bjcIYRNOgU43/MnN1t/MCpH6UoOtBrDNug==
+  dependencies:
+    strnum "^2.0.4"
+
 fastest-levenshtein@^1.0.7:
   version "1.0.16"
   resolved "https://registry.npmjs.org/fastest-levenshtein/-/fastest-levenshtein-1.0.16.tgz"
@@ -7223,6 +7230,11 @@ strnum@^1.0.5:
   resolved "https://registry.npmjs.org/strnum/-/strnum-1.0.5.tgz"
   integrity sha512-J8bbNyKKXl5qYcR36TIO8W3mVGVHrmmxsd5PAItGkmyzwJvybiw2IVq5nqd0i4LSNSkB/sx9VHllbfFdr9k1JA==
 
+strnum@^2.0.4:
+  version "2.0.4"
+  resolved "https://registry.yarnpkg.com/strnum/-/strnum-2.0.4.tgz#7b2ace8a55d8c92a41c2d339ddb1bc306f337820"
+  integrity sha512-qrXhLMohxtEPKMlajtNaOp5zvAQUo6L3fNcdiJKzWH98kGfklqGwmxhFjM7DzxsuoVM7rJeiYr+lEcu4Jlu9UQ==
+
 supports-color@^5.3.0:
   version "5.5.0"
   resolved "https://registry.npmjs.org/supports-color/-/supports-color-5.5.0.tgz"
@@ -7791,12 +7803,12 @@ write-file-atomic@^3.0.0:
     signal-exit "^3.0.2"
     typedarray-to-buffer "^3.1.5"
 
-xml-disassembler@^1.3.11:
-  version "1.3.11"
-  resolved "https://registry.yarnpkg.com/xml-disassembler/-/xml-disassembler-1.3.11.tgz#427ea0ef5ab679dce3ff931136834c821dd1e374"
-  integrity sha512-SK20Co9nxwnQIDh7qlSX9lPsp4Zho+ysMXulsUmDhEAYLe57WHaBfi0DcdgTrB9cWBgjrM8TtipK7FZ81rzCag==
+xml-disassembler@^1.3.12:
+  version "1.3.12"
+  resolved "https://registry.yarnpkg.com/xml-disassembler/-/xml-disassembler-1.3.12.tgz#f3fa2ea6573e815c20e6ca2e7a758dfe68a7b807"
+  integrity sha512-P/aApcGRfq568GHwNBQDqdsKq686rwX03ZusyDugbokxd7CDPB5AXBP79bdrJWdKV4k6l/dHBfRwMzJ/kgcNbg==
   dependencies:
-    fast-xml-parser "^4.5.1"
+    fast-xml-parser "^5.0.6"
     ignore "^5.3.1"
     log4js "^6.9.1"
     tslib "^2.6.2"
@@ -7809,21 +7821,21 @@ xml2js@^0.6.2:
     sax ">=0.6.0"
     xmlbuilder "~11.0.0"
 
-xml2json-disassembler@^1.1.11:
-  version "1.1.11"
-  resolved "https://registry.yarnpkg.com/xml2json-disassembler/-/xml2json-disassembler-1.1.11.tgz#3500612985d0139021bf960031b4cfbde719dc2a"
-  integrity sha512-SeiOFYNo5+T0wLNBWuQaePYo7P+LDIBGK8ZfbWolkWtK5o3isoR+955oDdnc/M3edpVElUi2hHq338PgG56ing==
+xml2json-disassembler@^1.1.12:
+  version "1.1.12"
+  resolved "https://registry.yarnpkg.com/xml2json-disassembler/-/xml2json-disassembler-1.1.12.tgz#b7feba01bd575f9d68e1fc0341ab0b3f5d09b4fc"
+  integrity sha512-YQJd7XPdq8pxLZK++Ld6GGOowQalZsarg3UXh2GA4RwM6yPL4vpKPW6kFE3aa9llsHDgpBVZH3TYoirtfAWvUA==
   dependencies:
     tslib "^2.6.2"
-    xml-disassembler "^1.3.11"
+    xml-disassembler "^1.3.12"
 
-xml2yaml-disassembler@^1.1.11:
-  version "1.1.11"
-  resolved "https://registry.yarnpkg.com/xml2yaml-disassembler/-/xml2yaml-disassembler-1.1.11.tgz#cd3f2a1394fed8df41d62184eecefb112d129f62"
-  integrity sha512-gvEYlHVn0nqiP0P0iGZrtL4RlTg1jFCvP+QHSWSTDhsdCQP66B5qgaiKgjkPLrwq1aMsEQf0C4Wxxc1ogNwlnw==
+xml2yaml-disassembler@^1.1.12:
+  version "1.1.12"
+  resolved "https://registry.yarnpkg.com/xml2yaml-disassembler/-/xml2yaml-disassembler-1.1.12.tgz#3f933b33a4f6a30b19e43277890be7914fa6b096"
+  integrity sha512-BpTbiJsECMWxDme/ZwkVsDkDQuGXb14YswViajIWkNOMnzH6/8ITUqLMUsL0GGajufhM9a3+xNiZF0k/9Kzk5A==
   dependencies:
     tslib "^2.6.2"
-    xml-disassembler "^1.3.11"
+    xml-disassembler "^1.3.12"
     yaml "^2.7.0"
 
 xmlbuilder@~11.0.0:

package/oclif.manifest.json

@@ -29,7 +29,7 @@
           "char": "m",
           "name": "metadata-type",
           "required": true,
-          "summary": "The metadata suffix to process, such as 'flow', 'labels', etc. You can provide this flag multiple times to process multiple metadata types with a single command.",
+          "summary": "The metadata suffix to process, such as 'flow', 'labels', etc.",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
@@ -37,21 +37,21 @@
         "prepurge": {
           "name": "prepurge",
           "required": false,
-          "summary": "If provided, purge directories of pre-existing decomposed files.",
+          "summary": "Purge directories of pre-existing decomposed files.",
           "allowNo": false,
           "type": "boolean"
         },
         "postpurge": {
           "name": "postpurge",
           "required": false,
-          "summary": "If provided, purge the original files after decomposing them.",
+          "summary": "Purge the original files after decomposing them.",
           "allowNo": false,
           "type": "boolean"
         },
         "debug": {
           "name": "debug",
           "required": false,
-          "summary": "If provided, debug to a log file.",
+          "summary": "Debug to a log file.",
           "allowNo": false,
           "type": "boolean"
         },
@@ -131,7 +131,7 @@
           "char": "m",
           "name": "metadata-type",
           "required": true,
-          "summary": "The metadata suffix to process, such as 'flow', 'labels', etc. You can provide this flag multiple times to process multiple metadata types with a single command.",
+          "summary": "The metadata suffix to process, such as 'flow', 'labels', etc.",
           "hasDynamicHelp": false,
           "multiple": true,
           "type": "option"
@@ -139,14 +139,14 @@
         "postpurge": {
           "name": "postpurge",
           "required": false,
-          "summary": "If provided, purge the decomposed files after recomposing them.",
+          "summary": "Purge the decomposed files after recomposing them.",
           "allowNo": false,
           "type": "boolean"
         },
         "debug": {
           "name": "debug",
           "required": false,
-          "summary": "If provided, debug to a log file.",
+          "summary": "Debug to a log file.",
           "allowNo": false,
           "type": "boolean"
         },
@@ -198,5 +198,5 @@
       ]
     }
   },
-  "version": "5.3.9"
+  "version": "5.3.11"
 }

package/package.json

@@ -1,16 +1,16 @@
 {
   "name": "sf-decomposer",
-  "description": "Decomposes Salesforce metadata into more manageable files.",
-  "version": "5.3.9",
+  "description": "Break down large Salesforce metadata files into smaller, more manageable files for version control and then recreate deployment-compatible files.",
+  "version": "5.3.11",
   "dependencies": {
     "@oclif/core": "^4",
     "@salesforce/core": "^8.2.1",
     "@salesforce/sf-plugins-core": "^11.2.1",
-    "@salesforce/source-deploy-retrieve": "^12.14.6",
+    "@salesforce/source-deploy-retrieve": "^12.15.1",
     "fs-extra": "^11.2.0",
-    "xml-disassembler": "^1.3.11",
-    "xml2json-disassembler": "^1.1.11",
-    "xml2yaml-disassembler": "^1.1.11"
+    "xml-disassembler": "^1.3.12",
+    "xml2json-disassembler": "^1.1.12",
+    "xml2yaml-disassembler": "^1.1.12"
   },
   "devDependencies": {
     "@commitlint/cli": "^18.6.1",