Update semantic-release in / from 11.2.0 to 13.0.0 #23
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
![dependencies[bot]](https://avatars.githubusercontent.com/in/2310?s=60&v=4){kind=small}
Codecov Report
@@ Coverage Diff @@
## master #23 +/- ##
============================================
- Coverage 89.6% 88.98% -0.62%
Complexity 58 58
============================================
Files 8 8
Lines 125 118 -7
============================================
- Hits 112 105 -7
Misses 13 13
|
TysonAndre
added a commit
to tysonandre-patches/php-advanced-json-rpc
that referenced
this pull request
Jul 27, 2019
Add a method that does the exact same thing, as a simple workaround. Fixes felixfbecker#23
TysonAndre
added a commit
to tysonandre-patches/php-advanced-json-rpc
that referenced
this pull request
Jul 27, 2019
Use ReflectionNamedType for php 7.1+, instead. Fixes felixfbecker#23
TysonAndre
added a commit
to tysonandre-patches/php-advanced-json-rpc
that referenced
this pull request
Jul 27, 2019
Use ReflectionNamedType->getName() for php 7.1+, instead. Continue supporting php 7.0 Fixes felixfbecker#23
TysonAndre
added a commit
to tysonandre-patches/php-advanced-json-rpc
that referenced
this pull request
Sep 10, 2019
Use ReflectionNamedType->getName() for php 7.1+, instead. Continue supporting php 7.0 Fixes felixfbecker#23
TysonAndre
added a commit
to tysonandre-patches/php-advanced-json-rpc
that referenced
this pull request
Sep 12, 2019
Use ReflectionNamedType->getName() for php 7.1+, instead. Continue supporting php 7.0 Fixes felixfbecker#23
felixfbecker
pushed a commit
that referenced
this pull request
Sep 12, 2019
) Use ReflectionNamedType->getName() for php 7.1+, instead. Continue supporting php 7.0 Fixes #23
|
🎉 This issue has been resolved in version 3.0.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Dependencies.io has updated
semantic-release(a npm dependency in/) from "11.2.0" to "13.0.0".13.0.0
13.0.0 (2018-01-27)
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.