autorel 0.0.21 → 0.0.22

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.
Files changed (2) hide show
  1. package/README.md +13 -11
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -114,7 +114,7 @@ Whether to skip creating a release on GitHub. If `true`, the release will not be
114
114
 
115
115
  ## run
116
116
 
117
- A command to run after the release is complete. This will be run via `child_process`. The following environment variables are available:
117
+ A command to run after the release is complete. The following environment variables are available:
118
118
 
119
119
  | Variable | Description |
120
120
  | --- | --- |
@@ -127,9 +127,9 @@ A command to run after the release is complete. This will be run via `child_proc
127
127
 
128
128
  ## runScript (YAML only)
129
129
 
130
- A bash script to run after the release is complete. This will be run via `bash` and `child_process`. Environment variables are available as above.
130
+ A bash script to run after the release is complete. Environment variables are available as above.
131
131
 
132
- > This requires `bash` to be installed on the system.
132
+ > ❗️ This requires `bash` to be installed on the system.
133
133
 
134
134
  You can use the multi-line string syntax in YAML to write a script:
135
135
 
@@ -142,14 +142,6 @@ runScript: |
142
142
  - Argument: `runScript: string`
143
143
  - Default: `undefined`
144
144
 
145
- ## tag
146
-
147
- The tag to use for the release. This will be used verbatim, instead of being generated from the version number. Always results in a release being created unless `noRelease` is `true`. **Advanced usage only.**
148
-
149
- - CLI: `--tag`
150
- - Argument: `tag: string`
151
- - Default: `undefined`
152
-
153
145
  ## pre-release
154
146
 
155
147
  The pre-release channel to use. This will be appended to the version number. For example, if the version is `1.0.0` and the pre-release is `alpha`, the version will be `1.0.0-alpha.1`. For "production" releases, leave this blank. In this case, "latest" will be used for the NPM tag/channel.
@@ -192,6 +184,16 @@ The above will release to the `latest` channel (production) on NPM for the `main
192
184
 
193
185
  - Argument: `branches: ReleaseBranch[]`
194
186
 
187
+ ## useVersion
188
+
189
+ The version to use for the release INSTEAD of the version being generated. Always results in a release being created unless `noRelease` is `true`. **Advanced usage only, not recommended for most users.**
190
+
191
+ - CLI: `--use-version`
192
+ - Argument: `useVersion: string`
193
+ - Default: `undefined`
194
+
195
+ > ❗️ Must be a valid SemVer version, without the `v`.
196
+
195
197
  # Sample YAML Configuration
196
198
 
197
199
  <sub>_.autorel.yaml_</sub>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "autorel",
3
- "version": "0.0.21",
3
+ "version": "0.0.22",
4
4
  "description": "Automate semantic releases based on conventional commits. Similar to semantic-release but much simpler.",
5
5
  "license": "MIT",
6
6
  "author": "Marc H. Weiner <mhweiner234@gmail.com> (https://mhweiner.com)",