You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: MAINTAINERS.md
+4-6
Original file line number
Diff line number
Diff line change
@@ -279,18 +279,16 @@ This is not necessarily ideal, and we should consider another method of using br
279
279
1. Decide whether this is a `patch`, `minor`, or `major` release by the PRs which have been merged since the last release.
280
280
1. Checkout `master` in your working copy & pull.
281
281
1. Modify `CHANGELOG.md`; follow the existing conventions in that file. Commit this file only; add `[ci skip]` to the commit message to avoid a build.
282
-
1. Use `npm version` to bump the version; see `npm version --help` for more info. (Hint--use `-m`: e.g. `npm version patch -m 'Release v%s'`)
283
-
1. Push `master` to origin with your new tag; e.g. `git push origin master --tags`
282
+
1. Use `npm version`(use `npm@6+`) to bump the version; see `npm version --help` for more info. (Hint--use `-m`: e.g.,`npm version patch -m 'Release v%s'`)
283
+
1. Push `master` to `origin` with your new tag; e.g. `git push origin master --tags`
284
284
1. Copy & paste the added lines to a new GitHub "release". Be sure to add any missing link references (use "preview" button). Save release as draft.
285
285
1. Meanwhile, you can check [the build](https://travis-ci.org/mochajs/mocha) on Travis-CI.
286
-
1. Once it's green and you're satisfied with the release notes, open your draft release on GitHub, then click "publish"
286
+
1. Once the build is green, and you're satisfied with the release notes, open your draft release on GitHub, then click "publish."
287
287
1. Back in your working copy, run `npm publish`.
288
-
1. Announce the update on Twitter or just tell your dog or something.
288
+
1. Announce the update on Twitter or just tell your dog or something. New releases will be automatically tweeted by [@b0neskull](https://twitter.com/b0neskull).
289
289
290
290
*Note: there are too many steps above.*
291
291
292
-
> As of this writing, `npm version` (using npm@5) is not working well, and you may have to tag manually. Commit the change to the version in `package.json` with a message of the format `Release vX.Y.Z`, then tag the changeset using `vX.Y.Z`.
293
-
294
292
## Projects
295
293
296
294
There are [Projects](https://github.com/mochajs/mocha/projects), but we haven't yet settled on how to use them.
0 commit comments