chore: consider docs-changes to be patch releases #66
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.
Since our docstrings and our README.md files ship with the code,
we should publish a new version when these docs are updated.
This change will at least satisfy those requirements, and also possible
ship some new patch version for other docs that aren't visible in
the published artifact, but that sounds okay to me.
You can see on the commit-analyzer readme that the default
presetis
angular1 (so no changes there, just making this explicit), andexplicit rules are additve to the base presets2.
Footnotes
https://github.com/semantic-release/commit-analyzer#configuration ↩
https://github.com/semantic-release/commit-analyzer#releaserules ↩