fix(deps): update dependency semantic-release to v15 #8
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Codecov Report
@@ Coverage Diff @@
## master #8 +/- ##
=======================================
Coverage 96.92% 96.92%
=======================================
Files 1 1
Lines 65 65
=======================================
Hits 63 63
Misses 2 2Continue to review full report at Codecov.
|
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
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
^12.2.2to^15.0.0Release Notes
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.
This PR has been generated by Renovate Bot.