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
BREAKING CHANGE: The `changelog` options has been removed. The `CHANGELOG.md` is not created or updated anymore.
Use https://github.com/semantic-release/changelog to create/update the `CHANGELOG.md`.
By default if a `CHANGELOG.md` file exists and has been modified it will be included in the release commit.
Copy file name to clipboardExpand all lines: README.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ Determine the Git tag and version of the last tagged release.
16
16
17
17
## publish
18
18
19
-
Update the `CHANGELOG.md` file and publish a release commit, optionnaly including addtional files.
19
+
Publish a release commit, including configurable files.
20
20
21
21
## Configuration
22
22
@@ -32,7 +32,7 @@ Using the `GIT_CREDENTIALS` environment variable is the recommended configuratio
32
32
33
33
`GIT_CREDENTIALS` can be your Git username and passort in the format `<username>:<password>` or a token for certain Git providers like [Github](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/), [Bitbucket](https://confluence.atlassian.com/bitbucketserver/personal-access-tokens-939515499.html) or [Gitlab](https://docs.gitlab.com/ce/user/profile/personal_access_tokens.html).
34
34
35
-
If the `GH_TOKEN` or `GITHUB_TOKEN` environment variables are defined their value will be used as a replacement for `GIT_CREDENTIALS`.
35
+
If the `GH_TOKEN` or `GITHUB_TOKEN` environment variables are defined their value will be used as a replacement for `GIT_CREDENTIALS`.
36
36
37
37
### Environment variables
38
38
@@ -46,7 +46,6 @@ If the `GH_TOKEN` or `GITHUB_TOKEN` environment variables are defined their valu
|`changelog`| Whether to create/update the `CHANGELOG.md` file. |`true`|
50
49
|`message`| The message for the release commit. See [message](#message). |`chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}`|
51
50
|`assets`| Files to include in the release commit. See [assets](#assets). |`["package.json", "npm-shrinkwrap.json"]`|
52
51
@@ -113,18 +112,19 @@ Options can be set within the plugin definition in the `semantic-release` config
113
112
}
114
113
```
115
114
116
-
When using with the [npm](https://github.com/semantic-release/npm) plugin or the [github](https://github.com/semantic-release/github) plugin:
117
-
- The [npm](https://github.com/semantic-release/npm) plugin must be called first in order to update the `package.json` file so the [git](https://github.com/semantic-release/git) plugin can include it in the release commit.
115
+
When using with the [changelog](https://github.com/semantic-release/changelog), [npm](https://github.com/semantic-release/npm) or [github](https://github.com/semantic-release/github) plugins:
116
+
- The [changelog](https://github.com/semantic-release/changelog) plugin must be called first in order to update the changelog file so the [git](https://github.com/semantic-release/git) and [npm](https://github.com/semantic-release/npm) plugin can include it in the release.
117
+
- The [npm](https://github.com/semantic-release/npm) plugin must be called second in order to update the `package.json` file so the [git](https://github.com/semantic-release/git) plugin can include it in the release commit.
118
118
- The [github](https://github.com/semantic-release/github) plugin must be called last to create a [Github Release](https://help.github.com/articles/about-releases/) that reference the tag created by the [git](https://github.com/semantic-release/git) plugin.
119
119
120
-
To use with [github](https://github.com/semantic-release/github), [npm](https://github.com/semantic-release/npm) and [condition-travis](https://github.com/semantic-release/condition-travis):
120
+
To use with the [changelog](https://github.com/semantic-release/changelog), [github](https://github.com/semantic-release/github), [npm](https://github.com/semantic-release/npm) and [condition-travis](https://github.com/semantic-release/condition-travis) plugins:
Add the [environment](https://github.com/travis-ci/travis.rb#env) variable `SSH_PASSPHRASE` to Travis with the value set during the [SSH keys generation](#generate-the-ssh-keys) step:
331
331
332
332
```bash
333
-
$ travis env set SSH_PASSPHRASE <ssh_passphrase>
333
+
$ travis env set SSH_PASSPHRASE <ssh_passphrase>
334
334
```
335
335
336
336
[Encrypt](https://github.com/travis-ci/travis.rb#encrypt) the `git_deploy_key` (private key) using a symmetric encryption (AES-256), and store the secret in a secure environment variable in the Travis environment:
0 commit comments