chore: update dependency semantic-release to v15 #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## master #20 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 6 6
Lines 137 137
=====================================
Hits 137 137Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This Pull Request updates dependency semantic-release from
v6.3.6tov15.4.1Release Notes
v15.4.1Compare Source
Bug Fixes
git rev-parse origin/${branch}to verify origin head (d7081fa)v15.4.0Compare Source
Features
v15.3.2Compare Source
Bug Fixes
git merge-baseerror code handling (4352144)v15.3.1Compare Source
Bug Fixes
v15.3.0Compare Source
Features
giterror message when authentication verification fails (cd9f2bd)v15.2.0Compare Source
Features
v15.1.11Compare Source
Bug Fixes
v15.1.10Compare Source
Bug Fixes
v15.1.9Compare Source
Bug Fixes
v15.1.8Compare Source
Bug Fixes
v15.1.7Compare Source
Bug Fixes
.gittorepositoryUrlonly if it's present in the configured URL (cb1f80c)v15.1.6Compare Source
Bug Fixes
tagFormatfrom the begining of the string (31ad231)v15.1.5Compare Source
Bug Fixes
v15.1.4Compare Source
Bug Fixes
v15.1.3Compare Source
Bug Fixes
execatimeout (3c46455)v15.1.2Compare Source
Bug Fixes
v15.1.1Compare Source
Bug Fixes
v15.1.0Compare Source
Features
repositoryUrl(5f1d530)v15.0.4Compare Source
Bug Fixes
v15.0.3Compare Source
Bug Fixes
git+httpsURL in package.json tohttps(b0b4fc8)v15.0.2Compare Source
Bug Fixes
getLastRelease(e4618a2)v15.0.1Compare Source
Bug Fixes
console.log(e5a73d8)v15.0.0Compare Source
Features
prepareplugin hook (c2beb64)BREAKING CHANGES
publishplugin hook is not supported anymore and now must be done in thepreparehookPlugins with a
publishhook that makes a commit or create a file that can be committed must use thepreparehook.v14.0.4Compare Source
Bug Fixes
v14.0.3Compare Source
Bug Fixes
v14.0.2Compare Source
Bug Fixes
v14.0.1Compare Source
Bug Fixes
v14.0.0Compare Source
Features
successandfailhooks (9788fca)BREAKING CHANGES
successandfailhooks are now enabled by defaultIn order to disable the
@semantic-release/githubplugin for thesuccessandfailhook, the corresponding options have to be set tofalsein the semantic-release configuration:{ "release": { "success": false, "fail": false } }Users who do not use the
@semantic-release/githubplugin, should disable it in thesuccessandfailby setting the corresponding options tofalseor to alternative plugin providingsuccessandfailhooks.Migration Guide
For non GitHub users
If you do no want the
successandfailnotification on GitHub or if you are not using GitHub you need to disable thesuccessandfailplugin 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.1Compare Source
Bug Fixes
v13.4.0Compare Source
⚠️ This release has been deprecated on npm as it was containing an unreported breaking change⚠️
Bug Fixes
repositoryUrlis set as an option (ce1e74f)Features
v13.3.1Compare Source
⚠️ This release has been deprecated on npm as it was containing an unreported breaking change⚠️
Bug Fixes
EPLUGINCONFerror details (9dd127b)v13.3.0Compare Source
⚠️ This release has been deprecated on npm as it was containing an unreported breaking change⚠️
Features
successandfailnotification plugins (49f5e70)v13.2.0Compare Source
Features
v13.1.5Compare Source
Bug Fixes
v13.1.4Compare Source
Bug Fixes
v13.1.3Compare Source
Bug Fixes
git+httpsurl tohttps(cbf5785)v13.1.2Compare Source
Bug Fixes
v13.1.1Compare Source
Bug Fixes
v13.1.0Compare Source
Bug Fixes
Features
tagFormatoption to customize Git tag name (39536fa)v13.0.2Compare Source
Bug Fixes
GIT_CREDENTIALSfor gtit credentials (467635b)v13.0.1Compare Source
Bug Fixes
Bufferandundefined(8b3605d)v13.0.0Compare Source
Bug Fixes
--repositoryUrlCLI option to--repository-url(cb36dd4)Features
BREAKING CHANGES
--repositoryUrlCLI options is replaced by--repository-urlgetLastReleaseplugin typeThe
getLastReleaseplugins will not be called anymore.The Git authentication is now mandatory and must be set via
GH_TOKEN,GITHUB_TOKEN,GL_TOKEN,GITLAB_TOKENorGIT_CREDENTIALSas 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.1Compare Source
Bug Fixes
Bufferandundefinedv12.4.0Compare Source
Features
v12.3.0Compare Source
Features
v12.2.5Compare Source
Bug Fixes
--no-ciarg parsing (0d2d1f2)v12.2.4Compare Source
Bug Fixes
v12.2.3Compare Source
Bug Fixes
v12.2.2Compare Source
Bug Fixes
v12.2.1Compare Source
Bug Fixes
v12.2.0Compare Source
Features
v12.1.1Compare Source
Bug Fixes
v12.1.0Compare Source
Features
v12.0.0Compare Source
Features
BREAKING CHANGES
semantic-releasedoesn't make sure it runs only on one Travis job anymore.The CI configuration has to be done such that
semantic-releaseThis 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:Add the
travis-deploy-oncescript in yourpackage.json:Modify your
.travis.ymlto usetravis-deploy-once.Replace:
by:
Replace
For Yarn users or any project with a
yarn.lockfile, adds the--ignore-enginesoption toyarn install.If the
installis not defined you have to define it with:v11.2.0Compare Source
Features
v11.1.0Compare Source
Features
v11.0.3Compare Source
Bug Fixes
v11.0.2Compare Source
Bug Fixes
v11.0.1Compare Source
11.0.1 (2017-11-29)
Bug Fixes
undefinedvalues for thegetLastReleaseandgenerateNotesplugins (d7b323d)namefrom log as it's not an existing option anymore (fcb832b)v11.0.0Compare Source
11.0.0 (2017-11-25)
Features
BREAKING CHANGES
pkgandenvare not passed to plugin anymore.Plugins relying on a
package.jsonmust verify the presence of a validpackage.jsonand load it.Plugins can use
process.envinstead ofenv.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-releaseversion11.0.0.v10.0.1Compare Source
Bug Fixes
v10.0.0Compare Source
Features
BREAKING CHANGES
githubToken,githubUrlandgithubApiPathPrefixhave to be set at the github plugin level. They can be set viaGH_TOKEN,GH_URLandGH_PREFIXenvironment variables.npmparameter is no longer passed to plugins. We recommend using npm-conf to read out information from the.npmrcfile.v9.1.1Compare Source
9.1.1 (2017-11-10)
Bug Fixes
v9.1.0Compare Source
9.1.0 (2017-10-30)
Features
v9.0.3Compare Source
9.0.3 (2017-10-30)
Bug Fixes
v9.0.2Compare Source
9.0.2 (2017-10-29)
Bug Fixes
v9.0.1Compare Source
9.0.1 (2017-10-29)
Bug Fixes
v9.0.0Compare Source
Features
BREAKING CHANGES
semantic-releaseinstead ofsemantic-release pre && npm publish && semantic-release post.semantic-releasecommand 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..).semantic-releasecommand with unexpected argument(s) now exit with 1 and print an help message.npmloganymore and the log level cannot be configured. Debug logs can be activated with CLI option--debugor with environment variableDEBUG=semantic-release:*--debugdoesn't enable the dry-run mode anymore but activate the debugs. The dry run mode is now set with the CLI command--dry-runor-d.semantic-release pre && npm shrinkwrap && semantic-release post
npm shrinkwrap, you have to run it beforesemantic-releasenow. You can set"presemantic-release": "npm shrinkwrap"in your package.json fileMIGRATION GUIDE
Update the
semantic-releasein yourpackage.jsonfrom:To:
v8.2.3Compare Source
Bug Fixes
v8.2.2Compare Source
Bug Fixes
v8.2.1Compare Source
Bug Fixes
v8.2.0Compare Source
Features
v8.1.2Compare Source
Bug Fixes
v8.1.1Compare Source
Bug Fixes
v8.1.0Compare Source
Features
v8.0.4Compare Source
Bug Fixes
v8.0.3Compare Source
Bug Fixes
v8.0.2Compare Source
Bug Fixes
v8.0.1Compare Source
Bug Fixes
v8.0.0Compare Source
Bug Fixes
BREAKING CHANGES
v7.0.2Compare Source
Bug Fixes
post: create
v1.2.3tag tag instead of branch (3f85597)Note that if a version was released with v7.0.1, you will run into the
ENOTINHISTORYerror :( To recover, follow these steps:"version"to what ever should have been released. As an example, let's say the new version number would be1.2.3. Save the changenpm publishto release the new version. Make sure to run any pre-publish tasks first if you have anygit tag v1.2.3(put in the same version as in step 2. Push the tag to GitHub withgit push --tagsThis will fix the problem and everything will work automagically again from here on now.
v7.0.1Compare Source
Bug Fixes
v7.0.0Compare Source
Bug Fixes
@semantic-release/release-notes-generatorto version 3.0.1 (1fa6d50)BREAKING CHANGES
🚀 This PR has been generated by Renovate using COB-LVS/renovate configuration.