chore(deps): update dependency semantic-release to v15 by renovate[bot] · Pull Request #57 · bahmutov/npm-utils

renovate · 2018-03-15T20:37:56Z

This Pull Request updates dependency semantic-release from v6.3.6 to v15.1.6

Release Notes

`v7.0.0`

Bug Fixes

package: update @semantic-release/release-notes-generator to version 3.0.1 (1fa6d50)

BREAKING CHANGES

package: Dropped support for unmaintained Node.js versions (< v4)

`v7.0.1`

Bug Fixes

post: Create a tag before makeing a release (3f85597)
post: fix target_commitish to be the default branch (f148a61)

`v7.0.2`

Bug Fixes

post: create v1.2.3 tag tag instead of branch (3f85597)

Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY error :( To recover, follow these steps:
1. Make sure you are on your main branch and pulled the latest changes from remote
2. Edit the package.json file, set "version" to what ever should have been released. As an example, let's say the new version number would be 1.2.3. Save the change
3. run npm publish to release the new version. Make sure to run any pre-publish tasks first if you have any
4. revert the changes
5. create a tag with git tag v1.2.3 (put in the same version as in step 2. Push the tag to GitHub with git push --tags
6. Manually create a release for the tag
This will fix the problem and everything will work automagically again from here on now.

`v8.0.0`

Bug Fixes

bin: adapt build leader error message to new leader detection algorithm (33dfcff)

BREAKING CHANGES

Remove support for publishing a package with node < 8. Details.

`v8.0.1`

Bug Fixes

package: update [@semantic-release]/commit-analyzer to version 3.0.1 (8c44c31)
package: update [@semantic-release]/release-notes-generator to version 4.0.0 (dd60b46)

`v8.0.2`

Bug Fixes

package: update [@semantic]-release/last-release-npm to version 2.0.0 (2d14c53)

`v8.0.3`

Bug Fixes

package: Set minimum node version to 4 (#442) (9951cf7)

`v8.0.4`

Bug Fixes

package: update [@semantic]-release/error to version 2.0.0 (3a4334f)

`v8.1.0`

Features

Retrieve version gitHead from git tags and unshallow the repo if necessary (85dd69b), closes #447 #393 #280 #276

`v8.1.1`

Bug Fixes

Exit with 1 if unexpected error happens (90417c6)

`v8.1.2`

Bug Fixes

Always pass pluginConfig to plugins as a defined object (8e9d9f7)

`v8.2.0`

Features

Allow to recover from ENOTINHISTORY with a tag and handle detached head repo (580ad9c)

`v8.2.1`

Bug Fixes

handle errors when verifyConditions and verifyRelease are a pipeline (b0bc490)

`v8.2.2`

Bug Fixes

Log error messages on reject (f6aacd2)

`v8.2.3`

Bug Fixes

package: update github to version 12.0.0 (16a02e5)

`v9.0.0`

Features

Refactor CLI to run with one command, improve logs, modularize, add tests (e2a8a5c)

BREAKING CHANGES

Semantic-Release must now be executed with semantic-release instead of semantic-release pre && npm publish && semantic-release post.
The semantic-release command now returns with exit code 0 on expected exception (no release has to be done, running on a PR, gitHead not found, other CI job failed etc...). It only returns with 1 when there is an unexpected error (code error in a plugin, plugin not found, git command cannot be run etc..).
Calling the semantic-release command with unexpected argument(s) now exit with 1 and print an help message.
Semantic-Release does not rely on npmlog anymore and the log level cannot be configured. Debug logs can be activated with CLI option --debug or with environment variable DEBUG=semantic-release:*
The CLI options --debug doesn't enable the dry-run mode anymore but activate the debugs. The dry run mode is now set with the CLI command --dry-run or -d.
semantic-release pre && npm shrinkwrap && semantic-release post
If you depend on npm shrinkwrap, you have to run it before semantic-release now. You can set "presemantic-release": "npm shrinkwrap" in your package.json file

MIGRATION GUIDE

Update the semantic-release in your package.json from:

"scripts": {
   "semantic-release": "semantic-release pre && npm publish && semantic-release post"
}

To:

"scripts": {
   "semantic-release": "semantic-release"
}

`v9.0.1`

9.0.1 (2017-10-29)

Bug Fixes

package: update [@semantic-release]/release-notes-generator to version 5.0.0 (8a1dd7b)

`v9.0.2`

9.0.2 (2017-10-29)

Bug Fixes

Check SemanticReleaseError by error.semanticRelease property (65d344b)
Include Error properties in logs (c90765e)

`v9.0.3`

9.0.3 (2017-10-30)

Bug Fixes

package: update [@semantic-release]/commit-analyzer to version 4.0.0 (186950a)

`v9.1.0`

9.1.0 (2017-10-30)

Features

Additional commit information (d0180c4)

`v9.1.1`

9.1.1 (2017-11-10)

Bug Fixes

docs: remove unnecessary backticks in readme (a4951b7)

`v10.0.0`

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.

`v10.0.1`

Bug Fixes

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

`v11.0.0`

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.

`v11.0.1`

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.2`

Bug Fixes

log plugin type in addition of path (4053d8f)

`v11.0.3`

Bug Fixes

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

`v11.1.0`

Features

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

`v11.2.0`

Features

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

`v12.0.0`

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

`v12.1.0`

Features

allow to release from local machine (5bc46a0)

`v12.1.1`

Bug Fixes

security: Updated marked dependency (f4d9ebe)

`v12.2.0`

Features

allow to exclude commits from analysis (53f3de6)

`v12.2.1`

Bug Fixes

package: update execa to version 0.9.0 (93173e2)

`v12.2.2`

Bug Fixes

set node minimum version to 8.3 (cc0c312)

`v12.2.3`

Bug Fixes

package: update cosmiconfig to version 4.0.0 (51c02b9)

`v12.2.4`

Bug Fixes

package: update lodash to version 4.17.4 (fa2ca8a)

`v12.2.5`

Bug Fixes

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

`v12.3.0`

Features

log all verification errors (cdb98f9)

`v12.4.0`

Features

hide sensitive info in stdout/sdtin (fb0caa0)

`v13.0.0`

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`

Bug Fixes

hide sensitive info for Buffer and undefined

`v13.0.1`

Bug Fixes

hide sensitive info for Buffer and undefined (8b3605d)

`v13.0.2`

Bug Fixes

prioritize GIT_CREDENTIALS for gtit credentials (467635b)

`v13.1.0`

Bug Fixes

log all core verification errors (faabffb)

Features

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

`v13.1.1`

Bug Fixes

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

`v13.1.2`

Bug Fixes

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

`v13.1.3`

Bug Fixes

always transform git+https url to https (cbf5785)

`v13.1.4`

Bug Fixes

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

`v13.1.5`

Bug Fixes

debug log all options (7e785fa)

`v13.2.0`

Features

add debug logs for git commands (687435b)

`v13.3.0`

⚠️This release has been deprecated on npm as it was containing an unreported breaking change⚠️

Features

add success and fail notification plugins (49f5e70)
allow plugins to throw an iterable list of errors (9b2f6bf)

`v13.3.1`

⚠️This release has been deprecated on npm as it was containing an unreported breaking change⚠️

Bug Fixes

fix EPLUGINCONF error details (9dd127b)

`v13.4.0`

⚠️This release has been deprecated on npm as it was containing an unreported breaking change⚠️

Bug Fixes

log current version of semantic-release (f92677b)
set repository authentication when repositoryUrl is set as an option (ce1e74f)

Features

improve CLI (97cb354)

`v13.4.1`

Bug Fixes

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

`v14.0.0`

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.

`v14.0.1`

Bug Fixes

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

`v14.0.2`

Bug Fixes

verify branch first (1966f0e)

`v14.0.3`

Bug Fixes

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

`v14.0.4`

Bug Fixes

exclude empty env var value from replacement (20246c0)

`v15.0.0`

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.

`v15.0.1`

Bug Fixes

remove unecessary console.log (e5a73d8)

`v15.0.2`

Bug Fixes

exclude prereleases from version retrived by getLastRelease (e4618a2)

`v15.0.3`

Bug Fixes

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

`v15.0.4`

Bug Fixes

package: update execa to version 0.10.0 (f13ec6a)

`v15.1.0`

Features

allow to use shorthand for repositoryUrl (5f1d530)

`v15.1.1`

Bug Fixes

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

`v15.1.2`

Bug Fixes

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

`v15.1.3`

Bug Fixes

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

`v15.1.4`

Bug Fixes

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

`v15.1.5`

Bug Fixes

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

`v15.1.6`

Bug Fixes

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

Commits

v11.0.3

e00dd16 chore(package): update @semantic-release/github to version 2.2.3
d28b7e3 fix(package): update @semantic-release/github to version 3.0.0

v11.1.0

f707b1a feat: allow to define plugin options globally
2fc538b test: add test for missing custom plugin modules
754b420 feat: support sharable configuration

v11.2.0

996305d feat: move npm workaround for missing gitHead to the npm plugin

v12.0.0

8d57565 feat: make semantic-release CI agnostic
e145134 ci: fix travis-deploy-once install cmd

v12.1.0

3c80fd2 docs: update badges
7eded2f chore(package): update @semantic-release/github to version 3.0.1
95de6a5 test: update test for `@semantic-release/github@3.0.1`
5cc62e4 test: add missing mockserver mocks
5bc46a0 feat: allow to release from local machine

v12.1.1

f4d9ebe fix(security): Updated marked dependency

v12.2.0

ed89361 docs: documentation improvements
fdb995f docs: publish with gitbook
d6c398f docs: add heading anchor
75778bc docs: troubleshooting
ba79c85 docs: typos. clarifications
fd54eea docs: update Yarn FAQ
53f3de6 feat: allow to exclude commits from analysis

v12.2.1

e0b4e6a docs: add CONTRIBUTING guidelines
adbcca6 docs: add issue template
49ad198 docs(contrib): add atomic commits requirement
48ade92 chore(package): update prettier to version 1.10.0
93173e2 fix(package): update execa to version 0.9.0

v12.2.2

cc0c312 fix: set node minimum version to 8.3

v12.2.3

0c1f0a1 docs: typo
51c02b9 fix(package): update cosmiconfig to version 4.0.0

v12.2.4

fa2ca8a fix(package): update lodash to version 4.17.4

v12.2.5

e0fa20b ci(travis): use Build Stages
7e860c7 docs(travis): recommend to use the deploy step instead of script
0d2d1f2 fix: fix the --no-ci arg parsing

v12.3.0

03e117b chore(package): update ava to version 0.25.0
cdb98f9 feat: log all verification errors

v12.4.0

fb0caa0 feat: hide sensitive info in stdout/sdtin

v13.0.0

d0b304e feat: get last release with git tags
cb36dd4 fix: rename the --repositoryUrl CLI option to --repository-url

v13.0.1

8b3605d fix: hide sensitive info for Buffer and undefined

v13.0.2

467635b fix: prioritize GIT_CREDENTIALS for gtit credentials

v13.1.0

e3c9bb8 docs: recommend to execute semantic-release via npx
dc416b2 docs: explain npx alternatives for Yarn
2f75dff docs: fix image path (#625)
faabffb fix: log all core verification errors
39536fa feat: add tagFormat option to customize Git tag name

v13.1.1

d820823 fix: use long option to delete tag in git push

v13.1.2

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

v13.1.3

cbf5785 fix: always transform git+https url to https

v13.1.4

2edd9da fix(package): update git-url-parse to version 8.1.0
053c9ed test: add test to parse GitLab/Bitbucket URLs with groups

v13.1.5

7e785fa fix: debug log all options

v13.2.0

687435b feat: add debug logs for git commands

v13.3.0

5fd990a docs: fix typo in extending link
2f8d716 docs: make some grammatical, spelling, typo fixes.
9360caf docs: fix minor typo in FAQ
9b2f6bf feat: allow plugins to throw an iterable list of errors
49f5e70 feat: add success and fail notification plugins

v13.3.1

d72cfc2 docs: fix typo in travis recipe
fcb64e6 docs: remove unnecessary script override in travis recipe
7fbd272 docs: add Travis Build Stages recipe
c6e95b0 docs: add CircleCI workflows recipe
51f6e5f docs: simplify travis config
c9bd5de docs: simplify GitLAb-ci config
9dd127b fix: fix EPLUGINCONF error details

v13.4.0

f92677b fix: log current version of semantic-release
97cb354 feat: improve CLI
b6837a2 test: use older version of mockserver
ce1e74f fix: set repository authentication when repositoryUrl is set as an option

v13.4.1

8a2ef48 test: revert to mockserver:latest docker container
1b3c51d docs: add missing success and fail options
04f3061 fix: remove the github plugin from default success and fail hooks

v14.0.0

9788fca feat: use `@semantic-release/githubas default forsuccessandfail` hooks

v14.0.1

305f4ee fix: do not transform repositoryUrl if it allow to push

v14.0.2

1966f0e fix: verify branch first

v14.0.3

ce15b75 chore(package): update xo to version 0.20.0
aa724e8 chore(package): simplify xo configuration
4d04901 style: lint
857d418 fix: allow boolean option to be set in config file

v14.0.4

20246c0 fix: exclude empty env var value from replacement

v15.0.0

c2beb64 feat: add the prepare plugin hook

v15.0.1

a7c187f docs: fix grammar and typos in README, CONTRIBUTING, installation guide, and plugin guide
78f0937 chore(package): update proxyquire to version 2.0.0
50f3c6e docs(README): correct pluralization
e5a73d8 fix: remove unecessary console.log

v15.0.2

e4618a2 fix: exclude prereleases from version retrived by getLastRelease

v15.0.3

1129d47 docs(configuration): environment variable DEBUG must be set to semantic-release:*, not semantic-release
6f74dcb fix: use correct debug namespace
b0b4fc8 fix: convert git+https URL in package.json to https

v15.0.4

f13ec6a fix(package): update execa to version 0.10.0

v15.1.0

5f1d530 feat: allow to use shorthand for repositoryUrl

v15.1.1

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

v15.1.2

7c48afa fix: prevent git CLI to prompt user/password on CI

v15.1.3

dff0a34 docs: add "Introduction to Semantic Release" article
3c46455 fix: remove execa timeout
30ee231 fix: prevent git prompt before permissions verification

v15.1.4

51e340f fix: handle case with no last release in history

v15.1.5

e41726c docs: fix grammar and typos in CI configuration, configuration, and shareable configurations
02746aa fix(package): update git-url-parse to version 8.3.1

v15.1.6

a8a07b7 docs: clarify FAQ to publish non-JavaScript packages
31ad231 fix: match tag to tagFormat from the begining of the string

This PR has been generated by Renovate Bot.

renovate Bot force-pushed the renovate/semantic-release-15.x branch 5 times, most recently from 7f36e77 to 6948f77 Compare March 22, 2018 02:06

renovate Bot force-pushed the renovate/semantic-release-15.x branch from 6948f77 to a66f818 Compare April 3, 2018 21:53

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

b0c0674

renovate Bot force-pushed the renovate/semantic-release-15.x branch from a66f818 to b0c0674 Compare April 11, 2018 21:24

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

chore(deps): update dependency semantic-release to v15#57
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/semantic-release-15.x

renovate Bot commented Mar 15, 2018 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented Mar 15, 2018 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bug Fixes

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

BREAKING CHANGES

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Features

BREAKING CHANGES

MIGRATION GUIDE

9.0.1 (2017-10-29)

Bug Fixes

9.0.2 (2017-10-29)

Bug Fixes

9.0.3 (2017-10-30)

Bug Fixes

9.1.0 (2017-10-30)

Features

9.1.1 (2017-11-10)

Bug Fixes

Features

BREAKING CHANGES

Bug Fixes

11.0.0 (2017-11-25)

Features

BREAKING CHANGES

MIGRATION GUIDE

11.0.1 (2017-11-29)

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Features

BREAKING CHANGES

Migration Guide

Features

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Features

BREAKING CHANGES

Migration Guide

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

Make sure the Git authentication is configured

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Features

Bug Fixes

Bug Fixes

Features

renovate Bot commented Mar 15, 2018 •

edited

Loading

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