Repository navigation
Describe 0.2.0 in the changelog - #3
Merged
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 0.2.0 release needs its notes on
mainbefore it is tagged. release-it also refuses to tag whilemainhas no commits since0.2.0-rc.1, so this is the commit the final0.2.0tag goes on.Docs only: it adds the 0.2.0 entry to
CHANGELOG.md. The same entry goes todevwith the version match after the release.0.2.0-rc.1is on npm undernextand passed n8n's community-package scan.Verify:
GITHUB_BASE_REF=main node scripts/review-check.mjspasses 40/40.test/docs-match-ui.mjsconfirms every Resource → Operation the entry names exists in the node.