docs(plugin developer guide): correction, additional details / advanced #1961
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
A correction to the earlier documentation: the "nextRelease" object is NOT similar to the lastRelease and there are some differences. Because of this, the object is now documented as a separate entry. Added also information on how the error handling should be done so that semantic-release would be able to handle errors from plugins properly and call "fail" lifecycle plugins. Included some more advanced information on how the analyzeCommits-lifecycle plugins work and how the result of the initial analyzer can be overridden. This is an edge case, but could happen and is good to understand.
JoA-MoS
pushed a commit
to semantic-release-plus/semantic-release
that referenced
this pull request
Jun 5, 2021
…ed (semantic-release#1961) A correction to the earlier documentation: the "nextRelease" object is NOT similar to the lastRelease and there are some differences. Because of this, the object is now documented as a separate entry. Added also information on how the error handling should be done so that semantic-release would be able to handle errors from plugins properly and call "fail" lifecycle plugins. Included some more advanced information on how the analyzeCommits-lifecycle plugins work and how the result of the initial analyzer can be overridden. This is an edge case, but could happen and is good to understand.
|
🎉 This PR is included in version 17.4.4 🎉 The release is available on: 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.
A correction to the earlier documentation: the "nextRelease" object is NOT similar to the
lastRelease and there are some differences. Because of this, the object is now documented as a
separate entry. Added also information on how the error handling should be done so that
semantic-release would be able to handle errors from plugins properly and call "fail" lifecycle
plugins. Included some more advanced information on how the analyzeCommits-lifecycle plugins work
and how the result of the initial analyzer can be overridden. This is an edge case, but could happen
and is good to understand.