release-it 15.10.1 → 15.10.2

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 +169 -100
  2. package/package.json +17 -9
package/README.md CHANGED
@@ -1,24 +1,23 @@
1
1
  # Release It! 🚀
2
2
 
3
- 🚀 Generic CLI tool to automate versioning and package publishing related tasks:
3
+ 🚀 Generic CLI tool to automate versioning and package publishing-related tasks:
4
4
 
5
5
  <img align="right" src="./docs/assets/release-it.svg?raw=true" height="280">
6
6
 
7
7
  - Bump version (in e.g. `package.json`)
8
- - [Git commit, tag, push](#git)
9
- - Execute any (test or build) commands using [hooks](#hooks)
10
- - [Create release at GitHub](#github-releases) or [GitLab](#gitlab-releases)
11
- - [Generate changelog](#changelog)
12
- - [Publish to npm](#publish-to-npm)
13
- - [Manage pre-releases](#manage-pre-releases)
14
- - Extend with [plugins](#plugins)
15
- - Release from any [CI/CD environment](./docs/ci.md)
8
+ - [Git commit, tag, push][1]
9
+ - Execute any (test or build) commands using [hooks][2]
10
+ - [Create release at GitHub][3] or [GitLab][4]
11
+ - [Generate changelog][5]
12
+ - [Publish to npm][6]
13
+ - [Manage pre-releases][7]
14
+ - Extend with [plugins][8]
15
+ - Release from any [CI/CD environment][9]
16
16
 
17
17
  Use release-it for version management and publish to anywhere with its versatile configuration, a powerful plugin
18
18
  system, and hooks to execute any command you need to test, build, and/or publish your project.
19
19
 
20
- [![Action Status](https://github.com/release-it/release-it/workflows/Cross-OS%20Tests/badge.svg)](https://github.com/release-it/release-it/actions)
21
- [![npm version](https://badge.fury.io/js/release-it.svg)](https://www.npmjs.com/package/release-it)
20
+ [![Action Status][11]][10] [![npm version][13]][12]
22
21
 
23
22
  ## Installation
24
23
 
@@ -59,9 +58,18 @@ npx release-it
59
58
 
60
59
  You will be prompted to select the new version, and more prompts will follow based on your configuration.
61
60
 
61
+ ## Experimental: knowledge base
62
+
63
+ You might want to ask your questions in the [Release It! knowledge base][14] (powered by OpenAI and [7-docs][15]). This
64
+ is an experimental knowledge base, answers may be incorrect.
65
+
62
66
  ## Yarn
63
67
 
64
- Using Yarn? Please see the [npm section on Yarn](./docs/npm.md#yarn).
68
+ Using Yarn? Please see the [npm section on Yarn][16].
69
+
70
+ ## Monorepos
71
+
72
+ Using a monorepo? Please see this [monorepo recipe][17].
65
73
 
66
74
  ## Global Installation
67
75
 
@@ -72,18 +80,15 @@ Per-project installation as shown above is recommended, but global installs are
72
80
 
73
81
  ## GitHub Actions
74
82
 
75
- Want to use release-it with GitHub Actions to fully automate the whole process? Enjoy this great walk-through:
76
- [How to use GitHub Actions & Release-It to Easily Release Your Code](https://www.youtube.com/watch?v=7pBcuT7j_A0) (by
77
- [David from Kodaps](https://twitter.com/KodapsAcademy)).
83
+ Want to use release-it with GitHub Actions to fully automate the whole process? Enjoy this great walk-through: [How to
84
+ use GitHub Actions & Release-It to Easily Release Your Code][18] (by [David from Kodaps][19]).
78
85
 
79
- → See [Continuous Integration environments](./docs/ci.md) for more details.
86
+ → See [Continuous Integration environments][9] for more details.
80
87
 
81
88
  ## Configuration
82
89
 
83
- Out of the box, release-it has sane defaults, and [plenty of options](./config/release-it.json) to configure it. Most
84
- projects use a `.release-it.json` file in the project root, or a `release-it` property in `package.json`.
85
-
86
- → See [Configuration](./docs/configuration.md) for more details.
90
+ Out of the box, release-it has sane defaults, and [plenty of options][20] to configure it. Most projects use a
91
+ `.release-it.json` file in the project root, or a `release-it` property in `package.json`.
87
92
 
88
93
  Here's a quick example `.release-it.json`:
89
94
 
@@ -98,6 +103,8 @@ Here's a quick example `.release-it.json`:
98
103
  }
99
104
  ```
100
105
 
106
+ → See [Configuration][21] for more details.
107
+
101
108
  ## Interactive vs. CI mode
102
109
 
103
110
  By default, release-it is **interactive** and allows you to confirm each task before execution:
@@ -105,7 +112,7 @@ By default, release-it is **interactive** and allows you to confirm each task be
105
112
  <img src="./docs/assets/release-it-interactive.gif?raw=true" height="290">
106
113
 
107
114
  By using the `--ci` option, the process is fully automated without prompts. The configured tasks will be executed as
108
- demonstrated in the first animation above. On a Continuous Integration (CI) environment, this non-interactive mode is
115
+ demonstrated in the first animation above. In a Continuous Integration (CI) environment, this non-interactive mode is
109
116
  activated automatically.
110
117
 
111
118
  Use `--only-version` to use a prompt only to determine the version, and automate the rest.
@@ -114,16 +121,15 @@ Use `--only-version` to use a prompt only to determine the version, and automate
114
121
 
115
122
  How does release-it determine the latest version?
116
123
 
117
- 1. For projects with a `package.json`, its `version` will be used (see [npm](./docs/npm.md) to skip this).
118
- 2. Otherwise, release-it uses the latest Git tag to determine which version should be released.
119
- 3. As a last resort, `0.0.0` will be used as the latest version.
124
+ 1. For projects with a `package.json`, its `version` will be used (see [npm][22] to skip this).
125
+ 2. Otherwise, release-it uses the latest Git tag to determine which version should be released.
126
+ 3. As a last resort, `0.0.0` will be used as the latest version.
120
127
 
121
128
  Alternatively, a plugin can be used to override this (e.g. to manage a `VERSION` or `composer.json` file):
122
129
 
123
- - [@release-it/bumper](https://github.com/release-it/bumper) to read from or bump the version in any file
124
- - [@release-it/conventional-changelog](https://github.com/release-it/conventional-changelog) to get a recommended bump
125
- based on commit messages
126
- - [release-it-calver-plugin](https://github.com/casmith/release-it-calver-plugin) to use CalVer (Calendar Versioning)
130
+ - [@release-it/bumper][23] to read from or bump the version in any file
131
+ - [@release-it/conventional-changelog][24] to get a recommended bump based on commit messages
132
+ - [release-it-calver-plugin][25] to use CalVer (Calendar Versioning)
127
133
 
128
134
  Add the `--release-version` flag to print the **next** version without releasing anything.
129
135
 
@@ -132,68 +138,68 @@ Add the `--release-version` flag to print the **next** version without releasing
132
138
  Git projects are supported well by release-it, automating the tasks to stage, commit, tag and push releases to any Git
133
139
  remote.
134
140
 
135
- → See [Git](./docs/git.md) for more details.
141
+ → See [Git][26] for more details.
136
142
 
137
143
  ## GitHub Releases
138
144
 
139
145
  GitHub projects can have releases attached to Git tags, containing release notes and assets. There are two ways to add
140
- [GitHub releases](https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases) in your
141
- release-it flow:
146
+ [GitHub releases][27] in your release-it flow:
142
147
 
143
- 1. Automated (requires a `GITHUB_TOKEN`)
144
- 2. Manual (using the GitHub web interface with pre-populated fields)
148
+ 1. Automated (requires a `GITHUB_TOKEN`)
149
+ 2. Manual (using the GitHub web interface with pre-populated fields)
145
150
 
146
- → See [GitHub Releases](./docs/github-releases.md) for more details.
151
+ → See [GitHub Releases][28] for more details.
147
152
 
148
153
  ## GitLab Releases
149
154
 
150
- GitLab projects can have releases attached to Git tags, containing release notes and assets. To automate
151
- [GitLab releases](https://docs.gitlab.com/ce/user/project/releases/):
155
+ GitLab projects can have releases attached to Git tags, containing release notes and assets. To automate [GitLab
156
+ releases][29]:
152
157
 
153
158
  - Configure `gitlab.release: true`
154
- - Obtain a [personal access token](https://gitlab.com/profile/personal_access_tokens) (release-it only needs the "api"
155
- scope).
156
- - Make sure the token is [available as an environment variable](./docs/environment-variables.md).
159
+ - Obtain a [personal access token][30] (release-it only needs the "api" scope).
160
+ - Make sure the token is [available as an environment variable][31].
157
161
 
158
- → See [GitLab Releases](./docs/gitlab-releases.md) for more details.
162
+ → See [GitLab Releases][32] for more details.
159
163
 
160
164
  ## Changelog
161
165
 
162
166
  By default, release-it generates a changelog, to show and help select a version for the new release. Additionally, this
163
167
  changelog serves as the release notes for the GitHub or GitLab release.
164
168
 
165
- The [default command](./config/release-it.json) is based on `git log ...`. This setting (`git.changelog`) can be
166
- overridden. To further customize the release notes for the GitHub or GitLab release, there's `github.releaseNotes` or
167
- `gitlab.releaseNotes`. Make sure any of these commands output the changelog to `stdout`. Note that release-it by default
168
- is agnostic to commit message conventions. Plugins are available for:
169
+ The [default command][20] is based on `git log ...`. This setting (`git.changelog`) can be overridden. To further
170
+ customize the release notes for the GitHub or GitLab release, there's `github.releaseNotes` or `gitlab.releaseNotes`.
171
+ Make sure any of these commands output the changelog to `stdout`. Note that release-it by default is agnostic to commit
172
+ message conventions. Plugins are available for:
169
173
 
170
174
  - GitHub and GitLab Releases
171
175
  - auto-changelog
172
176
  - Conventional Changelog
173
177
  - Keep A Changelog
174
178
 
175
- See [Changelog](./docs/changelog.md) for more details.
179
+ To print the changelog without releasing anything, add the `--changelog` flag.
180
+
181
+ → See [Changelog][33] for more details.
176
182
 
177
183
  ## Publish to npm
178
184
 
179
185
  With a `package.json` in the current directory, release-it will let `npm` bump the version in `package.json` (and
180
186
  `package-lock.json` if present), and publish to the npm registry.
181
187
 
182
- → See [Publish to npm](./docs/npm.md) for more details.
188
+ → See [Publish to npm][22] for more details.
183
189
 
184
190
  ## Manage pre-releases
185
191
 
186
192
  With release-it, it's easy to create pre-releases: a version of your software that you want to make available, while
187
- it's not in the stable semver range yet. Often "alpha", "beta", and "rc" (release candidate) are used as identifier for
193
+ it's not in the stable semver range yet. Often "alpha", "beta", and "rc" (release candidate) are used as identifiers for
188
194
  pre-releases. An example pre-release version is `2.0.0-beta.0`.
189
195
 
190
- → See [Manage pre-releases](./docs/pre-releases.md) for more details.
196
+ → See [Manage pre-releases][34] for more details.
191
197
 
192
198
  ## Update or re-run existing releases
193
199
 
194
200
  Use `--no-increment` to not increment the last version, but update the last existing tag/version.
195
201
 
196
- This may be helpful in cases where the version was already incremented. Here's a few example scenarios:
202
+ This may be helpful in cases where the version was already incremented. Here are a few example scenarios:
197
203
 
198
204
  - To update or publish a (draft) GitHub Release for an existing Git tag.
199
205
  - Publishing to npm succeeded, but pushing the Git tag to the remote failed. Then use
@@ -217,8 +223,8 @@ Use the optional `:plugin` part in the middle to hook into a life cycle method e
217
223
  The core plugins include `version`, `git`, `npm`, `github`, `gitlab`.
218
224
 
219
225
  Note that hooks like `after:git:release` will not run when either the `git push` failed, or when it is configured not to
220
- be executed (e.g. `git.push: false`). See [execution order](./docs/plugins.md#execution-order) for more details on
221
- execution order of plugin lifecycle methods.
226
+ be executed (e.g. `git.push: false`). See [execution order][35] for more details on execution order of plugin lifecycle
227
+ methods.
222
228
 
223
229
  All commands can use configuration variables (like template strings). An array of commands can also be provided, they
224
230
  will run one after another. Some example release-it configuration:
@@ -235,8 +241,7 @@ will run one after another. Some example release-it configuration:
235
241
  }
236
242
  ```
237
243
 
238
- The variables can be found in the [default configuration](./config/release-it.json). Additionally, the following
239
- variables are exposed:
244
+ The variables can be found in the [default configuration][20]. Additionally, the following variables are exposed:
240
245
 
241
246
  ```text
242
247
  version
@@ -267,15 +272,11 @@ Using Inquirer.js inside custom hook scripts might cause issues (since release-i
267
272
 
268
273
  Use `--dry-run` to show the interactivity and the commands it _would_ execute.
269
274
 
270
- → See [Dry Runs](./docs/dry-runs.md) for more details.
271
-
272
- To print the next version without releasing anything, add the `--release-version` flag.
273
-
274
- To print the changelog without releasing anything, add the `--changelog` flag.
275
+ → See [Dry Runs][36] for more details.
275
276
 
276
277
  ## Troubleshooting & debugging
277
278
 
278
- - With `release-it --verbose` (or `-V`), release-it prints the output of every user-defined [hook](#hooks).
279
+ - With `release-it --verbose` (or `-V`), release-it prints the output of every user-defined [hook][2].
279
280
  - With `release-it -VV`, release-it also prints the output of every internal command.
280
281
  - Use `NODE_DEBUG=release-it:* release-it [...]` to print configuration and more error details.
281
282
 
@@ -285,64 +286,132 @@ Use `verbose: 2` in a configuration file to have the equivalent of `-VV` on the
285
286
 
286
287
  Since v11, release-it can be extended in many, many ways. Here are some plugins:
287
288
 
288
- | Plugin | Description |
289
- | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
290
- | [@release-it/bumper](https://github.com/release-it/bumper) | Read & write the version from/to any file |
291
- | [@release-it/conventional-changelog](https://github.com/release-it/conventional-changelog) | Provides recommended bump, conventional-changelog, and updates `CHANGELOG.md` |
292
- | [@release-it/keep-a-changelog](https://github.com/release-it/keep-a-changelog) | Maintain CHANGELOG.md using the Keep a Changelog standards |
293
- | [@release-it-plugins/lerna-changelog](https://github.com/release-it-plugins/lerna-changelog) | Integrates lerna-changelog into the release-it pipeline |
294
- | [@release-it-plugins/workspaces](https://github.com/release-it-plugins/workspaces) | Releases each of your projects configured workspaces |
295
- | [release-it-calver-plugin](https://github.com/casmith/release-it-calver-plugin) | Enables Calendar Versioning (calver) with release-it |
296
- | [@grupoboticario/news-fragments](https://github.com/grupoboticario/news-fragments) | An easy way to generate your changelog file |
297
- | [@j-ulrich/release-it-regex-bumper](https://github.com/j-ulrich/release-it-regex-bumper) | Regular expression based version read/write plugin for release-it |
289
+ | Plugin | Description |
290
+ | ----------------------------------------- | ----------------------------------------------------------------------------- |
291
+ | [@release-it/bumper][23] | Read & write the version from/to any file |
292
+ | [@release-it/conventional-changelog][24] | Provides recommended bump, conventional-changelog, and updates `CHANGELOG.md` |
293
+ | [@release-it/keep-a-changelog][37] | Maintain CHANGELOG.md using the Keep a Changelog standards |
294
+ | [@release-it-plugins/lerna-changelog][38] | Integrates lerna-changelog into the release-it pipeline |
295
+ | [@release-it-plugins/workspaces][39] | Releases each of your projects configured workspaces |
296
+ | [release-it-calver-plugin][25] | Enables Calendar Versioning (calver) with release-it |
297
+ | [@grupoboticario/news-fragments][40] | An easy way to generate your changelog file |
298
+ | [@j-ulrich/release-it-regex-bumper][41] | Regular expression based version read/write plugin for release-it |
298
299
 
299
300
  Internally, release-it uses its own plugin architecture (for Git, GitHub, GitLab, npm).
300
301
 
301
- → See all [release-it plugins on npm](https://www.npmjs.com/search?q=keywords:release-it-plugin).
302
+ → See all [release-it plugins on npm][42].
302
303
 
303
- → See [plugins](./docs/plugins.md) for documentation to write plugins.
304
+ → See [plugins][43] for documentation to write plugins.
304
305
 
305
306
  ## Use release-it programmatically
306
307
 
307
- While mostly used as a CLI tool, release-it can be used as a dependency to integrate in your own scripts. See
308
- [use release-it programmatically](./docs/recipes/programmatic.md) for example code.
308
+ While mostly used as a CLI tool, release-it can be used as a dependency to integrate in your own scripts. See [use
309
+ release-it programmatically][44] for example code.
309
310
 
310
311
  ## Example projects using release-it
311
312
 
312
- - [axios/axios](https://github.com/axios/axios)
313
- - [blockchain/blockchain-wallet-v4-frontend](https://github.com/blockchain/blockchain-wallet-v4-frontend)
314
- - [callstack/react-native-paper](https://github.com/callstack/react-native-paper)
315
- - [ember-cli/ember-cli](https://github.com/ember-cli/ember-cli)
316
- - [js-cookie/js-cookie](https://github.com/js-cookie/js-cookie)
317
- - [metalsmith/metalsmith](https://github.com/metalsmith/metalsmith)
318
- - [mozilla/readability](https://github.com/mozilla/readability)
319
- - [pahen/madge](https://github.com/pahen/madge)
320
- - [redis/node-redis](https://github.com/redis/node-redis)
321
- - [reduxjs/redux](https://github.com/reduxjs/redux)
322
- - [saleor/saleor](https://github.com/saleor/saleor)
323
- - [Semantic-Org/Semantic-UI-React](https://github.com/Semantic-Org/Semantic-UI-React)
324
- - [shipshapecode/shepherd](https://github.com/shipshapecode/shepherd)
325
- - [StevenBlack/hosts](https://github.com/StevenBlack/hosts)
326
- - [swagger-api/swagger-ui](https://github.com/swagger-api/swagger-ui) +
327
- [swagger-editor](https://github.com/swagger-api/swagger-editor)
328
- - [tabler/tabler](https://github.com/tabler/tabler) + [tabler-icons](https://github.com/tabler/tabler-icons)
329
- - [youzan/vant](https://github.com/youzan/vant)
330
- - [Repositories that depend on release-it](https://github.com/release-it/release-it/network/dependents)
331
- - GitHub search for [path:\*\*/.release-it.json](https://github.com/search?q=path%3A**%2F.release-it.json&type=code)
313
+ - [axios/axios][45]
314
+ - [blockchain/blockchain-wallet-v4-frontend][46]
315
+ - [callstack/react-native-paper][47]
316
+ - [ember-cli/ember-cli][48]
317
+ - [js-cookie/js-cookie][49]
318
+ - [metalsmith/metalsmith][50]
319
+ - [mozilla/readability][51]
320
+ - [pahen/madge][52]
321
+ - [redis/node-redis][53]
322
+ - [reduxjs/redux][54]
323
+ - [saleor/saleor][55]
324
+ - [Semantic-Org/Semantic-UI-React][56]
325
+ - [shipshapecode/shepherd][57]
326
+ - [StevenBlack/hosts][58]
327
+ - [swagger-api/swagger-ui][59] + [swagger-editor][60]
328
+ - [tabler/tabler][61] + [tabler-icons][62]
329
+ - [youzan/vant][63]
330
+ - [Repositories that depend on release-it][64]
331
+ - GitHub search for [path:\*\*/.release-it.json][65]
332
332
 
333
333
  ## Legacy Node.js
334
334
 
335
335
  The latest major version is v15, supporting Node.js 14 and up (as Node.js v12 is EOL). Use release-it v14 for
336
- environments running Node.js v10 and v12. Also see [CHANGELOG.md](./CHANGELOG.md).
336
+ environments running Node.js v10 and v12. Also see [CHANGELOG.md][66].
337
337
 
338
338
  ## Links
339
339
 
340
- - See [CHANGELOG.md](./CHANGELOG.md) for major/breaking updates, and
341
- [releases](https://github.com/release-it/release-it/releases) for a detailed version history.
342
- - To **contribute**, please read [CONTRIBUTING.md](./.github/CONTRIBUTING.md) first.
343
- - Please [open an issue](https://github.com/release-it/release-it/issues/new) if anything is missing or unclear in this
344
- documentation.
340
+ - See [CHANGELOG.md][66] for major/breaking updates, and [releases][67] for a detailed version history.
341
+ - To **contribute**, please read [CONTRIBUTING.md][68] first.
342
+ - Please [open an issue][69] if anything is missing or unclear in this documentation.
345
343
 
346
344
  ## License
347
345
 
348
- [MIT](./LICENSE)
346
+ [MIT][70]
347
+
348
+ [1]: #git
349
+ [2]: #hooks
350
+ [3]: #github-releases
351
+ [4]: #gitlab-releases
352
+ [5]: #changelog
353
+ [6]: #publish-to-npm
354
+ [7]: #manage-pre-releases
355
+ [8]: #plugins
356
+ [9]: ./docs/ci.md
357
+ [10]: https://github.com/release-it/release-it/actions
358
+ [11]: https://github.com/release-it/release-it/workflows/Cross-OS%20Tests/badge.svg
359
+ [12]: https://www.npmjs.com/package/release-it
360
+ [13]: https://badge.fury.io/js/release-it.svg
361
+ [14]: https://release-it.deno.dev
362
+ [15]: https://github.com/7-docs/7-docs
363
+ [16]: ./docs/npm.md#yarn
364
+ [17]: ./docs/recipes/monorepo.md
365
+ [18]: https://www.youtube.com/watch?v=7pBcuT7j_A0
366
+ [19]: https://twitter.com/KodapsAcademy
367
+ [20]: ./config/release-it.json
368
+ [21]: ./docs/configuration.md
369
+ [22]: ./docs/npm.md
370
+ [23]: https://github.com/release-it/bumper
371
+ [24]: https://github.com/release-it/conventional-changelog
372
+ [25]: https://github.com/casmith/release-it-calver-plugin
373
+ [26]: ./docs/git.md
374
+ [27]: https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases
375
+ [28]: ./docs/github-releases.md
376
+ [29]: https://docs.gitlab.com/ce/user/project/releases/
377
+ [30]: https://gitlab.com/profile/personal_access_tokens
378
+ [31]: ./docs/environment-variables.md
379
+ [32]: ./docs/gitlab-releases.md
380
+ [33]: ./docs/changelog.md
381
+ [34]: ./docs/pre-releases.md
382
+ [35]: ./docs/plugins.md#execution-order
383
+ [36]: ./docs/dry-runs.md
384
+ [37]: https://github.com/release-it/keep-a-changelog
385
+ [38]: https://github.com/release-it-plugins/lerna-changelog
386
+ [39]: https://github.com/release-it-plugins/workspaces
387
+ [40]: https://github.com/grupoboticario/news-fragments
388
+ [41]: https://github.com/j-ulrich/release-it-regex-bumper
389
+ [42]: https://www.npmjs.com/search?q=keywords:release-it-plugin
390
+ [43]: ./docs/plugins.md
391
+ [44]: ./docs/recipes/programmatic.md
392
+ [45]: https://github.com/axios/axios
393
+ [46]: https://github.com/blockchain/blockchain-wallet-v4-frontend
394
+ [47]: https://github.com/callstack/react-native-paper
395
+ [48]: https://github.com/ember-cli/ember-cli
396
+ [49]: https://github.com/js-cookie/js-cookie
397
+ [50]: https://github.com/metalsmith/metalsmith
398
+ [51]: https://github.com/mozilla/readability
399
+ [52]: https://github.com/pahen/madge
400
+ [53]: https://github.com/redis/node-redis
401
+ [54]: https://github.com/reduxjs/redux
402
+ [55]: https://github.com/saleor/saleor
403
+ [56]: https://github.com/Semantic-Org/Semantic-UI-React
404
+ [57]: https://github.com/shipshapecode/shepherd
405
+ [58]: https://github.com/StevenBlack/hosts
406
+ [59]: https://github.com/swagger-api/swagger-ui
407
+ [60]: https://github.com/swagger-api/swagger-editor
408
+ [61]: https://github.com/tabler/tabler
409
+ [62]: https://github.com/tabler/tabler-icons
410
+ [63]: https://github.com/youzan/vant
411
+ [64]: https://github.com/release-it/release-it/network/dependents
412
+ [65]: https://github.com/search?q=path%3A**%2F.release-it.json&type=code
413
+ [66]: ./CHANGELOG.md
414
+ [67]: https://github.com/release-it/release-it/releases
415
+ [68]: ./.github/CONTRIBUTING.md
416
+ [69]: https://github.com/release-it/release-it/issues/new
417
+ [70]: ./LICENSE
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "release-it",
3
- "version": "15.10.1",
4
- "description": "Generic CLI tool to automate versioning and package publishing related tasks.",
3
+ "version": "15.10.2",
4
+ "description": "Generic CLI tool to automate versioning and package publishing-related tasks.",
5
5
  "keywords": [
6
6
  "build",
7
7
  "changelog",
@@ -50,6 +50,7 @@
50
50
  "scripts": {
51
51
  "lint": "eslint lib test",
52
52
  "format": "prettier --write \"{lib,test}/**/*.js\"",
53
+ "docs": "remark README.md 'docs/**/*.md' '.github/*.md' -o",
53
54
  "test": "ava --no-worker-threads",
54
55
  "release": "./bin/release-it.js"
55
56
  },
@@ -66,9 +67,9 @@
66
67
  "cosmiconfig": "8.1.3",
67
68
  "execa": "7.1.1",
68
69
  "git-url-parse": "13.1.0",
69
- "globby": "13.1.3",
70
+ "globby": "13.1.4",
70
71
  "got": "12.6.0",
71
- "inquirer": "9.1.5",
72
+ "inquirer": "9.2.0",
72
73
  "is-ci": "3.0.1",
73
74
  "issue-parser": "6.0.0",
74
75
  "lodash": "4.17.21",
@@ -80,7 +81,7 @@
80
81
  "os-name": "5.1.0",
81
82
  "promise.allsettled": "1.0.6",
82
83
  "proxy-agent": "5.0.0",
83
- "semver": "7.3.8",
84
+ "semver": "7.5.0",
84
85
  "shelljs": "0.8.5",
85
86
  "update-notifier": "6.0.2",
86
87
  "url-join": "5.0.0",
@@ -90,19 +91,26 @@
90
91
  "devDependencies": {
91
92
  "@octokit/request-error": "3.0.3",
92
93
  "ava": "5.2.0",
93
- "eslint": "8.37.0",
94
+ "eslint": "8.39.0",
94
95
  "eslint-config-prettier": "8.8.0",
95
96
  "eslint-plugin-ava": "14.0.0",
96
97
  "eslint-plugin-import": "2.27.5",
97
98
  "eslint-plugin-prettier": "4.2.1",
98
99
  "mock-fs": "5.2.0",
99
100
  "mock-stdio": "1.0.3",
100
- "nock": "13.3.0",
101
- "prettier": "2.8.7",
102
- "sinon": "15.0.3",
101
+ "nock": "13.3.1",
102
+ "prettier": "2.8.8",
103
+ "remark-cli": "11.0.0",
104
+ "remark-preset-webpro": "0.0.2",
105
+ "sinon": "15.0.4",
103
106
  "strip-ansi": "7.0.1"
104
107
  },
105
108
  "engines": {
106
109
  "node": ">=14.9"
110
+ },
111
+ "remarkConfig": {
112
+ "plugins": [
113
+ "preset-webpro"
114
+ ]
107
115
  }
108
116
  }