@teambit/harmony.content.cli-reference 2.0.1021 → 2.0.1022
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/cli-reference.docs.mdx +1 -1
- package/cli-reference.json +5 -0
- package/cli-reference.mdx +19 -18
- package/dist/cli-reference.docs.mdx +1 -1
- package/dist/cli-reference.json +5 -0
- package/dist/cli-reference.mdx.js +1 -1
- package/dist/cli-reference.mdx.js.map +1 -1
- package/dist/{preview-1777475960386.js → preview-1777488239091.js} +2 -2
- package/package.json +2 -2
package/cli-reference.docs.mdx
CHANGED
package/cli-reference.json
CHANGED
|
@@ -4952,6 +4952,11 @@
|
|
|
4952
4952
|
"",
|
|
4953
4953
|
"skip-push",
|
|
4954
4954
|
"skip pushing the changes to the remote repository (useful when CI handles the push separately)"
|
|
4955
|
+
],
|
|
4956
|
+
[
|
|
4957
|
+
"",
|
|
4958
|
+
"no-bitmap-commit",
|
|
4959
|
+
"skip the post-tag git add/commit/push entirely. The new versions still land in the scope, but no .bitmap (or lockfile) commit is created on the default branch. Pair with `bitmapAutoSync: true` in workspace.jsonc so developers auto-sync their local .bitmap on the first bit command after `git pull`."
|
|
4955
4960
|
]
|
|
4956
4961
|
],
|
|
4957
4962
|
"description": "Tags and exports new semantic versions after merging a PR to main.",
|
package/cli-reference.mdx
CHANGED
|
@@ -418,24 +418,25 @@ Resolves the lane name from --lane or the current Git branch, validates it, and
|
|
|
418
418
|
**Description**: Tags and exports new semantic versions after merging a PR to main.
|
|
419
419
|
By default, bumps patch versions when merging to main. If specific configuration variables are set, it can use commit messages or explicit flags to determine the version bump. Runs install, tag, build, and export, then archives the remote lane and syncs lockfiles. Use in merge-to-main CI pipelines to publish releases.
|
|
420
420
|
|
|
421
|
-
| **Option** | **Option alias** | **Description**
|
|
422
|
-
| --------------------------------------- | :--------------: |
|
|
423
|
-
| `--message <message>` | `-m` | If set, use it as the tag message, if not, try and grab from git-commit-message
|
|
424
|
-
| `--build` | `-b` | Set to true to build the app locally, false (default) will build on Ripple CI
|
|
425
|
-
| `--strict` | `-s` | Set to true to fail on warnings as well as errors, false (default) only fails on errors
|
|
426
|
-
| `--increment <level>` | `-l` | options are: [major, premajor, minor, preminor, patch, prepatch, prerelease], default to patch
|
|
427
|
-
| `--prerelease-id <id>` | | prerelease identifier (e.g. "dev" to get "1.0.0-dev.1")
|
|
428
|
-
| `--patch` | `-p` | syntactic sugar for "--increment patch"
|
|
429
|
-
| `--minor` | | syntactic sugar for "--increment minor"
|
|
430
|
-
| `--major` | | syntactic sugar for "--increment major"
|
|
431
|
-
| `--pre-release [identifier]` | | syntactic sugar for "--increment prerelease" and `--prerelease-id <identifier>`
|
|
432
|
-
| `--increment-by <number>` | | (default to 1) increment semver flag (patch/minor/major) by. e.g. incrementing patch by 2: 0.0.1 -> 0.0.3.
|
|
433
|
-
| `--versions-file <path>` | | path to a file containing component versions. format: "component-id: version"
|
|
434
|
-
| `--verbose` | | show verbose output
|
|
435
|
-
| `--auto-merge-resolve <merge-strategy>` | `-r` | in case of merge conflict during checkout, resolve according to the provided strategy: [ours, theirs, manual]
|
|
436
|
-
| `--force-theirs` | | do not merge during checkout, just overwrite with incoming files
|
|
437
|
-
| `--lane-name <name>` | | specify the lane name to delete after merge (auto-detected if not provided)
|
|
438
|
-
| `--skip-push` | | skip pushing the changes to the remote repository (useful when CI handles the push separately)
|
|
421
|
+
| **Option** | **Option alias** | **Description** |
|
|
422
|
+
| --------------------------------------- | :--------------: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
423
|
+
| `--message <message>` | `-m` | If set, use it as the tag message, if not, try and grab from git-commit-message |
|
|
424
|
+
| `--build` | `-b` | Set to true to build the app locally, false (default) will build on Ripple CI |
|
|
425
|
+
| `--strict` | `-s` | Set to true to fail on warnings as well as errors, false (default) only fails on errors |
|
|
426
|
+
| `--increment <level>` | `-l` | options are: [major, premajor, minor, preminor, patch, prepatch, prerelease], default to patch |
|
|
427
|
+
| `--prerelease-id <id>` | | prerelease identifier (e.g. "dev" to get "1.0.0-dev.1") |
|
|
428
|
+
| `--patch` | `-p` | syntactic sugar for "--increment patch" |
|
|
429
|
+
| `--minor` | | syntactic sugar for "--increment minor" |
|
|
430
|
+
| `--major` | | syntactic sugar for "--increment major" |
|
|
431
|
+
| `--pre-release [identifier]` | | syntactic sugar for "--increment prerelease" and `--prerelease-id <identifier>` |
|
|
432
|
+
| `--increment-by <number>` | | (default to 1) increment semver flag (patch/minor/major) by. e.g. incrementing patch by 2: 0.0.1 -> 0.0.3. |
|
|
433
|
+
| `--versions-file <path>` | | path to a file containing component versions. format: "component-id: version" |
|
|
434
|
+
| `--verbose` | | show verbose output |
|
|
435
|
+
| `--auto-merge-resolve <merge-strategy>` | `-r` | in case of merge conflict during checkout, resolve according to the provided strategy: [ours, theirs, manual] |
|
|
436
|
+
| `--force-theirs` | | do not merge during checkout, just overwrite with incoming files |
|
|
437
|
+
| `--lane-name <name>` | | specify the lane name to delete after merge (auto-detected if not provided) |
|
|
438
|
+
| `--skip-push` | | skip pushing the changes to the remote repository (useful when CI handles the push separately) |
|
|
439
|
+
| `--no-bitmap-commit` | | skip the post-tag git add/commit/push entirely. The new versions still land in the scope, but no .bitmap (or lockfile) commit is created on the default branch. Pair with `bitmapAutoSync: true` in workspace.jsonc so developers auto-sync their local .bitmap on the first bit command after `git pull`. |
|
|
439
440
|
|
|
440
441
|
---
|
|
441
442
|
|
package/dist/cli-reference.json
CHANGED
|
@@ -4952,6 +4952,11 @@
|
|
|
4952
4952
|
"",
|
|
4953
4953
|
"skip-push",
|
|
4954
4954
|
"skip pushing the changes to the remote repository (useful when CI handles the push separately)"
|
|
4955
|
+
],
|
|
4956
|
+
[
|
|
4957
|
+
"",
|
|
4958
|
+
"no-bitmap-commit",
|
|
4959
|
+
"skip the post-tag git add/commit/push entirely. The new versions still land in the scope, but no .bitmap (or lockfile) commit is created on the default branch. Pair with `bitmapAutoSync: true` in workspace.jsonc so developers auto-sync their local .bitmap on the first bit command after `git pull`."
|
|
4955
4960
|
]
|
|
4956
4961
|
],
|
|
4957
4962
|
"description": "Tags and exports new semantic versions after merging a PR to main.",
|