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
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
The devDependency semantic-release was updated from 15.14.0 to 16.0.0.
This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
fix(package): update @semantic-release/github back to a build from the beta branch (d120eae)
BREAKING CHANGES
Require Node.js >= 10.13
this feature change the way semantic-release keep track of the channels on which a version has been released.
It now use a JSON object stored in a Git note instead of Git tags formatted as v{version}@{channel}.
The tags formatted as v{version}@{channel} will now be ignored. If you have made releases with v16.0.0 on branches other than the default one you will have to update your repository.
The changes to make consist in:
Finding all the versions that have been released on a branch other than the default one by searching for all tags formatted v{version}@{channel}
For each of those version:
Create a tag without the {@channel} if none doesn't already exists
Add a Git note to the tag without the {@channel} containing the channels on which the version was released formatted as {"channels":["channel1","channel2"]} and using null for the default channel (for example.{"channels":[null,"channel1","channel2"]})
Push the tags and notes
Update the GitHub releases that refer to a tag formatted as v{version}@{channel} to use the tag without it
Delete the tags formatted as v{version}@{channel}
Git CLI version 2.7.1 or higher is now required
The --merge option of the git tag command has been added in Git version 2.7.1 and is now used by semantic-release
Require Node.js => 8.15
package: Regexp are not supported anymore for property matching in the releaseRules option.
Regex are replaced by globs. For example /core-.*/ should be changed to 'core-*'.
the branch option has been removed in favor of branches
The new branches option expect either an Array or a single branch definition. To migrate your configuration:
If you want to publish package from multiple branches, please the configuration documentation
If you use the default configuration and want to publish only from master: nothing to change
If you use the branch configuration and want to publish only from one branch: replace branch by branches ("branch": "my-release-branch" => "branches": "my-release-branch")
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.
The devDependency semantic-release was updated from
15.14.0to16.0.0.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Publisher: semantic-release-bot
License: MIT
Release Notes for v16.0.0
16.0.0 (2020-01-09)
Bug Fixes
channelto publish success log (5744c5e)ERELEASEBRANCHESerror message (#1188) (37bcc9e)cioption via API and config file (2faff26)getTagHeadonly when necessary (de77a79)successplugin only once for releases added to a channel (9a023b4)addChannelfor 2 merged branches configured with the same channel (4aad9cd)false(751a5f1)getError(f96c660)await(9a1af4d)get-tagsalgorithm (00420a8)@semantic-release/githuband@semantic-release/npm(d55fda3)@semantic-release/github(9a30f35)@semantic-release/npmand@semantic-release/github(d6731b9)branchparameter frompushfunction (968b996)Features
addChannelplugins to returnfalsein order to signify no release was done (e1c7269)publishplugins to returnfalsein order to signify no release was done (47484f5)Performance Improvements
git tag --merge <branch>to filter tags present in a branch history (cffe9a8)Reverts
^1.0.0(fa62d0b)BREAKING CHANGES
It now use a JSON object stored in a Git note instead of Git tags formatted as v{version}@{channel}.
The tags formatted as v{version}@{channel} will now be ignored. If you have made releases with v16.0.0 on branches other than the default one you will have to update your repository.
The changes to make consist in:
{"channels":["channel1","channel2"]}and usingnullfor the default channel (for example.{"channels":[null,"channel1","channel2"]})The
--mergeoption of thegit tagcommand has been added in Git version 2.7.1 and is now used by semantic-releasereleaseRulesoption.Regex are replaced by globs. For example
/core-.*/should be changed to'core-*'.branchoption has been removed in favor ofbranchesThe new
branchesoption expect either an Array or a single branch definition. To migrate your configuration:master: nothing to changebranchconfiguration and want to publish only from one branch: replacebranchbybranches("branch": "my-release-branch"=>"branches": "my-release-branch")Commits
The new version differs by 114 commits.
0785a84fix: update plugin versions152bf45Merge remote-tracking branch 'origin/beta'3ba8f2aMerge remote-tracking branch 'origin/master' into beta9772563fix: look also for previous prerelease versions to determine the next one61665befix: correct log when adding channel to taga8747c4fix: verify is branch is up to date by comparing remote and local HEAD9a1af4dfix: remove unnecessaryawait9ecc7a3fix: increase next version on prerelease branch based on highest commit typec16fcc9Merge branch 'master' into beta0716a45feat: require Node.js >=10.13916c268feat: allow to release any version on a branch if up to date with next branch534c0dbMerge branch 'master' into betaec54c0btest: fix calls tofetchin testscbef9d1fix: modify fetch function to handle CircleCI specificsb2c1b2cfeat: use Git notes to store the channels on which a version has been releasedThere are 114 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴