sfdx-git-delta 5.3.0 → 5.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +2 -0
- package/README.md +4 -8
- package/lib/metadata/v55.json +1347 -0
- package/oclif.manifest.json +1 -1
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
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.
|
|
4
4
|
|
|
5
|
+
### [5.3.1](https://github.com/scolladon/sfdx-git-delta/compare/v5.3.0...v5.3.1) (2022-08-04)
|
|
6
|
+
|
|
5
7
|
## [5.3.0](https://github.com/scolladon/sfdx-git-delta/compare/v5.2.0...v5.3.0) (2022-06-13)
|
|
6
8
|
|
|
7
9
|
|
package/README.md
CHANGED
|
@@ -151,7 +151,7 @@ OPTIONS
|
|
|
151
151
|
-W, --ignore-whitespace ignore git diff whitespace (space,
|
|
152
152
|
tab, eol) changes
|
|
153
153
|
|
|
154
|
-
-a, --api-version=api-version [default:
|
|
154
|
+
-a, --api-version=api-version [default: 55] salesforce API version
|
|
155
155
|
|
|
156
156
|
-d, --generate-delta generate delta files in [--output]
|
|
157
157
|
folder
|
|
@@ -183,7 +183,7 @@ OPTIONS
|
|
|
183
183
|
this command invocation
|
|
184
184
|
```
|
|
185
185
|
|
|
186
|
-
_See code: [src/commands/sgd/source/delta.ts](https://github.com/scolladon/sfdx-git-delta/blob/v5.3.
|
|
186
|
+
_See code: [src/commands/sgd/source/delta.ts](https://github.com/scolladon/sfdx-git-delta/blob/v5.3.1/src/commands/sgd/source/delta.ts)_
|
|
187
187
|
<!-- commandsstop -->
|
|
188
188
|
|
|
189
189
|
### Windows users
|
|
@@ -192,8 +192,8 @@ If you run SGD on a Windows system, use double quotes [to prevent the terminal t
|
|
|
192
192
|
|
|
193
193
|
### CI/CD specificity
|
|
194
194
|
|
|
195
|
-
In CI/CD pipelines, branches are not checked out locally when the repository is cloned so you must specify the remote prefix.
|
|
196
|
-
If you do not specify the remote in CI context, the git pointer check will raise an error as the branch is not created locally.
|
|
195
|
+
In CI/CD pipelines, branches are not checked out locally when the repository is cloned, so you must specify the remote prefix.
|
|
196
|
+
If you do not specify the remote in CI context, the git pointer check will raise an error (as the branch is not created locally).
|
|
197
197
|
This applies to both `--from` and `--to` parameters as they both accept git pointers.
|
|
198
198
|
|
|
199
199
|
Exemple comparing `HEAD` with a `development` branch when the CI clone the repository with `origin` set as reference to the remote:
|
|
@@ -285,10 +285,6 @@ The simplest option to deploy the incremental changes is to use `force:source:de
|
|
|
285
285
|
sfdx force:source:deploy -x package/package.xml --postdestructivechanges destructiveChanges/destructiveChanges.xml
|
|
286
286
|
```
|
|
287
287
|
|
|
288
|
-
```sh
|
|
289
|
-
sfdx force:source:deploy -x package/package.xml --postdestructivechanges destructiveChanges/destructiveChanges.xml
|
|
290
|
-
```
|
|
291
|
-
|
|
292
288
|
And voilà! 🥳
|
|
293
289
|
|
|
294
290
|
However, keep in mind thate the above command will fail if the destructive change was supposed to be executed before the deployment (i.e. as `--predestructivechanges`), or if a warning occurs during deployment. Make sure to protect your CI/CD pipeline from those scenarios, so that it don't get stuck by a failed destructive change.
|