-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update semantic-release to the latest version 🚀 #27
Open
greenkeeper
wants to merge
2
commits into
master
Choose a base branch
from
greenkeeper/semantic-release-16.0.0
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Deploy preview for elegant-bardeen-3e1193 ready! Built with commit 20afd33 https://deploy-preview-27--elegant-bardeen-3e1193.netlify.com |
|
|
|
|
|
|
|
|
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
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.
The devDependency semantic-release was updated from
15.14.0
to16.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
channel
to publish success log (5744c5e)ERELEASEBRANCHES
error message (#1188) (37bcc9e)ci
option via API and config file (2faff26)getTagHead
only when necessary (de77a79)success
plugin only once for releases added to a channel (9a023b4)addChannel
for 2 merged branches configured with the same channel (4aad9cd)false
(751a5f1)getError
(f96c660)await
(9a1af4d)get-tags
algorithm (00420a8)@semantic-release/github
and@semantic-release/npm
(d55fda3)@semantic-release/github
(9a30f35)@semantic-release/npm
and@semantic-release/github
(d6731b9)branch
parameter frompush
function (968b996)Features
addChannel
plugins to returnfalse
in order to signify no release was done (e1c7269)publish
plugins to returnfalse
in 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 usingnull
for the default channel (for example.{"channels":[null,"channel1","channel2"]}
)The
--merge
option of thegit tag
command has been added in Git version 2.7.1 and is now used by semantic-releasereleaseRules
option.Regex are replaced by globs. For example
/core-.*/
should be changed to'core-*'
.branch
option has been removed in favor ofbranches
The new
branches
option expect either an Array or a single branch definition. To migrate your configuration:master
: nothing to changebranch
configuration and want to publish only from one branch: replacebranch
bybranches
("branch": "my-release-branch"
=>"branches": "my-release-branch"
)Commits
The new version differs by 114 commits.
0785a84
fix: update plugin versions
152bf45
Merge remote-tracking branch 'origin/beta'
3ba8f2a
Merge remote-tracking branch 'origin/master' into beta
9772563
fix: look also for previous prerelease versions to determine the next one
61665be
fix: correct log when adding channel to tag
a8747c4
fix: verify is branch is up to date by comparing remote and local HEAD
9a1af4d
fix: remove unnecessary
await
9ecc7a3
fix: increase next version on prerelease branch based on highest commit type
c16fcc9
Merge branch 'master' into beta
0716a45
feat: require Node.js >=10.13
916c268
feat: allow to release any version on a branch if up to date with next branch
534c0db
Merge branch 'master' into beta
ec54c0b
test: fix calls to
fetch
in testscbef9d1
fix: modify fetch function to handle CircleCI specifics
b2c1b2c
feat: use Git notes to store the channels on which a version has been released
There 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 🌴