chore(deps): update dependency semantic-release to v15 - autoclosed

log with signale and allow to customize stdin and stdout (0626d57)
return lastRelease, commits, nextRelease, releases from JS API (417779e)

v15.8.1

Compare Source

Bug Fixes

do not override env variable with default if defined (3fb3fa8)

v15.8.0

Compare Source

Features

pass cwd and env context to plugins (a94e08d)

v15.7.2

Compare Source

Bug Fixes

package: update git-url-parse to version 10.0.1 (d3c7232)

v15.7.1

Compare Source

Bug Fixes

set default path to generateNotes object config (d8e59cc)

v15.7.0

Compare Source

Bug Fixes

do not set path to plugin config defined as a Function or an Array (f93eeb7)

Features

allow to define multiple generateNotes plugins (5989989)

v15.6.6

Compare Source

Bug Fixes

use unauthenticated URL to check if branch is up to date (071dcce)

v15.6.5

Compare Source

Bug Fixes

allow empty release notes in dry-run mode (5847514)

v15.6.4

Compare Source

Bug Fixes

package: update hosted-git-info to version 2.7.1 (0862480)

v15.6.3

Compare Source

Bug Fixes

fetch all tags even if the repo is not shallow (45eee4a)

v15.6.2

Compare Source

Bug Fixes

add debug log for git fetch command (4abda31)

v15.6.1

Compare Source

Bug Fixes

package: update yargs to version 12.0.0 (d4f68a5)

v15.6.0

Compare Source

Features

allow to disable the publish plugin hook (4454d57)

v15.5.5

Compare Source

Bug Fixes

package: update read-pkg-up to version 4.0.0 (9137f85)

v15.5.4

Compare Source

Bug Fixes

use git ls-remote to verify if the remote branch is ahead (2b6378f)

v15.5.3

Compare Source

Bug Fixes

package: update p-locate to version 3.0.0 (0ab0426)

v15.5.2

Compare Source

Bug Fixes

package: update hook-std to version 1.0.0 (29e7ebf)

v15.5.1

Compare Source

Bug Fixes

plugin-load: clarify load message (6a36832), closes #811

v15.5.0

Compare Source

Features

add support for git version 2.0.0 (47c73eb)
verify minimum required git version is installed (db1cc60)

v15.4.4

Compare Source

Bug Fixes

package: update marked-terminal to version 3.0.0 (cd8ff5d)

v15.4.3

Compare Source

Bug Fixes

package: update marked to version 0.4.0 (a387c04)

v15.4.2

Compare Source

Bug Fixes

add clarification in EGITNOPERMISSION error message (a72d8f5)

v15.4.1

Compare Source

Bug Fixes

use git rev-parse origin/${branch} to verify origin head (d7081fa)

v15.4.0

Compare Source

Features

set tag author and committer name/email (61d7d38)

v15.3.2

Compare Source

Bug Fixes

correct git merge-base error code handling (4352144)

v15.3.1

Compare Source

Bug Fixes

package: update cosmiconfig to version 5.0.0 (349b2e8)

v15.3.0

Compare Source

Features

log git error message when authentication verification fails (cd9f2bd)

v15.2.0

Compare Source

Features

add support for Bitbucket token in environment variables (c93775c)

v15.1.11

Compare Source

Bug Fixes

fix Bitbucket authenticated URL (e88ac63)

v15.1.10

Compare Source

Bug Fixes

verify the local branch is up to date with the remote one (d15905c)

v15.1.9

Compare Source

Bug Fixes

unshallow repository with credentials (45d7e6f)

v15.1.8

Compare Source

Bug Fixes

package: update env-ci to version 2.0.0 (b9bd650)

v15.1.7

Compare Source

Bug Fixes

package: update git-url-parse to version 9.0.0 (7c9ec41)
add trailing .git to repositoryUrl only if it's present in the configured URL (cb1f80c)

v15.1.6

Compare Source

Bug Fixes

match tag to tagFormat from the begining of the string (31ad231)

v15.1.5

Compare Source

Bug Fixes

package: update git-url-parse to version 8.3.1 (02746aa)

v15.1.4

Compare Source

Bug Fixes

handle case with no last release in history (51e340f)

v15.1.3

Compare Source

Bug Fixes

prevent git prompt before permissions verification (30ee231)
remove execa timeout (3c46455)

v15.1.2

Compare Source

Bug Fixes

prevent git CLI to prompt user/password on CI (7c48afa)

v15.1.1

Compare Source

Bug Fixes

package: Remove commander.js dependency (#704) (c84ac15)

v15.1.0

Compare Source

Features

allow to use shorthand for repositoryUrl (5f1d530)

v15.0.4

Compare Source

Bug Fixes

package: update execa to version 0.10.0 (f13ec6a)

v15.0.3

Compare Source

Bug Fixes

convert git+https URL in package.json to https (b0b4fc8)
use correct debug namespace (6f74dcb)

v15.0.2

Compare Source

Bug Fixes

exclude prereleases from version retrived by getLastRelease (e4618a2)

v15.0.1

Compare Source

Bug Fixes

remove unecessary console.log (e5a73d8)

v15.0.0

Compare Source

Features

add the prepare plugin hook (c2beb64)

BREAKING CHANGES

Committing or creating files in the publish plugin hook is not supported anymore and now must be done in the prepare hook

Plugins with a publish hook that makes a commit or create a file that can be committed must use the prepare hook.

v14.0.4

Compare Source

Bug Fixes

exclude empty env var value from replacement (20246c0)

v14.0.3

Compare Source

Bug Fixes

allow boolean option to be set in config file (857d418)

v14.0.2

Compare Source

Bug Fixes

verify branch first (1966f0e)

v14.0.1

Compare Source

Bug Fixes

do not transform repositoryUrl if it allow to push (305f4ee)

v14.0.0

Compare Source

Features

use @semantic-release as default for success and fail hooks (9788fca)

BREAKING CHANGES

success and fail hooks are now enabled by default

In order to disable the @semantic-release/github plugin for the success and fail hook, the corresponding options have to be set to false in the semantic-release configuration:

{
  "release": {
    "success": false,
    "fail": false
  }
}

Users who do not use the @semantic-release/github plugin, should disable it in the success and fail by setting the corresponding options to false or to alternative plugin providing success and fail hooks.

Migration Guide

For non GitHub users

If you do no want the success and fail notification on GitHub or if you are not using GitHub you need to disable the success and fail plugin hooks by adding the following to your semantic-release configuration:

Add the following to your semantic-release configuration:

{
  "release": {
    "success": false,
    "fail": false
  }
}

For GitHub users

GitHub users do not need to change anything. You will get comments on PR and issues when a release that resolved them is publish as well as an issue when a problem happen that prevent to perform a release.

v13.4.1

Compare Source

Bug Fixes

remove the github plugin from default success and fail hooks (04f3061)

v13.2.0

Compare Source

Features

add debug logs for git commands (687435b)

v13.1.5

Compare Source

Bug Fixes

debug log all options (7e785fa)

v13.1.4

Compare Source

Bug Fixes

package: update git-url-parse to version 8.1.0 (2edd9da)

v13.1.3

Compare Source

Bug Fixes

always transform git+https url to https (cbf5785)

v13.1.2

Compare Source

Bug Fixes

package: update @semantic-release/github to version 4.0.2 (af8c830)

v13.1.1

Compare Source

Bug Fixes

use long option to delete tag in git push (d820823)

v13.1.0

Compare Source

Bug Fixes

log all core verification errors (faabffb)

Features

add tagFormat option to customize Git tag name (39536fa)

v13.0.2

Compare Source

Bug Fixes

prioritize GIT_CREDENTIALS for gtit credentials (467635b)

v13.0.1

Compare Source

Bug Fixes

hide sensitive info for Buffer and undefined (8b3605d)

v13.0.0

Compare Source

Bug Fixes

rename the --repositoryUrl CLI option to --repository-url (cb36dd4)

Features

get last release with git tags (d0b304e)

BREAKING CHANGES

The --repositoryUrl CLI options is replaced by --repository-url
Remove the getLastRelease plugin type

The getLastRelease plugins will not be called anymore.

Git repository authentication is now mandatory

The Git authentication is now mandatory and must be set via GH_TOKEN, GITHUB_TOKEN, GL_TOKEN, GITLAB_TOKEN or GIT_CREDENTIALS as described in CI configuration.

Migration Guide

Make sure the commit associated with the last release is tagged with `v<last_release_version>`

This will already be the case for all semantic-release users using the GitHub (default), Git or GitLab plugins or for any release done manually with npm publish.

Make sure the Git authentication is configured

This will already be the case for all semantic-release users using the GitHub (default), Git or GitLab plugins. See CI configuration.

v12.4.1

Compare Source

Bug Fixes

hide sensitive info for Buffer and undefined

v12.4.0

Compare Source

Features

hide sensitive info in stdout/sdtin (fb0caa0)

v12.3.0

Compare Source

Features

log all verification errors (cdb98f9)

v12.2.5

Compare Source

Bug Fixes

fix the --no-ci arg parsing (0d2d1f2)

v12.2.4

Compare Source

Bug Fixes

package: update lodash to version 4.17.4 (fa2ca8a)

v12.2.3

Compare Source

Bug Fixes

package: update cosmiconfig to version 4.0.0 (51c02b9)

v12.2.2

Compare Source

Bug Fixes

set node minimum version to 8.3 (cc0c312)

v12.2.1

Compare Source

Bug Fixes

package: update execa to version 0.9.0 (93173e2)

v12.2.0

Compare Source

Features

allow to exclude commits from analysis (53f3de6)

v12.1.1

Compare Source

Bug Fixes

security: Updated marked dependency (f4d9ebe)

v12.1.0

Compare Source

Features

allow to release from local machine (5bc46a0)

v12.0.0

Compare Source

Features

make semantic-release CI agnostic (8d57565)

BREAKING CHANGES

semantic-release doesn't make sure it runs only on one Travis job anymore.

The CI configuration has to be done such that semantic-release

runs only once per build
runs only after all tests are successful on every jobs of the build
runs on Node >=8

This can easily be done with travis-deploy-once.

For Yarn users semantic-release has to be installed with the option --ignore-engines when running on Node <= 8.

See Can I use semantic-release with Yarn? for more details.

Migration Guide

Install travis-deploy-once:

$ npm install --save-dev travis-deploy-once

Add thetravis-deploy-once script in your package.json:

"scripts": {
    "semantic-release": "semantic-release",
    "travis-deploy-once": "travis-deploy-once"
  }

Modify your .travis.yml to use travis-deploy-once.
Replace:

after_success:
  - npm run semantic-release

by:
Replace

after_success:
  - npm run travis-deploy-once "npm run semantic-release"

For Yarn users or any project with a yarn.lock file, adds the --ignore-engines option to yarn install.
If the install is not defined you have to define it with:

install:
  - yarn install --ignore-engines

v11.2.0

Compare Source

Features

move npm workaround for missing gitHead to the npm plugin (996305d)

v11.1.0

Compare Source

Features

allow to define plugin options globally (f707b1a)
support sharable configuration (754b420)

v11.0.3

Compare Source

Bug Fixes

package: update @semantic-release/github to version 3.0.0 (d28b7e3)

v11.0.2

Compare Source

Bug Fixes

log plugin type in addition of path (4053d8f)

v11.0.1

Compare Source

11.0.1 (2017-11-29)

Bug Fixes

Accept undefined values for the getLastRelease and generateNotes plugins (d7b323d)
remove name from log as it's not an existing option anymore (fcb832b)
Typo in error messages (613a646)

v11.0.0

Compare Source

11.0.0 (2017-11-25)

Features

Expect plugins to return Promises (5bec59b)
Make semantic-release language agnostic (0c67ba5)

BREAKING CHANGES

pkg and env are not passed to plugin anymore.
Plugins relying on a package.json must verify the presence of a valid package.json and load it.
Plugins can use process.env instead of env.
Each plugin is expected to return an async function or a Promise returning function. The callback parameter is not passed to plugins anymore.

MIGRATION GUIDE

If you are using a third-party plugin, please verify its documentation and repository to make sure it has been updated to work with semantic-release version 11.0.0.

v10.0.1

Compare Source

Bug Fixes

Use default plugin if the path property is missing from a single plugin configuration (d4c7605)

v10.0.0

Compare Source

Features

Extract npm and github publish to plugins (d548edc)

BREAKING CHANGES

githubToken, githubUrl and githubApiPathPrefix have to be set at the github plugin level. They can be set via GH_TOKEN, GH_URL and GH_PREFIX environment variables.
the npm parameter is no longer passed to plugins. We recommend using npm-conf to read out information from the .npmrc file.

v9.1.1

Compare Source

ahmadnassri / node-metalsmith-pug