Release 0.2.1 - #24
Merged
Merged
Conversation
Promotes `## [Unreleased]` and bumps `package.json` in the same commit, which is the process #23 established and the first release to follow it. The version on `main` will match npm the moment this publishes, which is the state n8n's verification review asked for. PATCH: the shipped delta since v0.2.0 is an error message that reads as a sentence, a field description, two codex categories and a set of search aliases. No resource, operation, option or parameter is added, renamed or removed, and `SourceTypes.ts` is byte-identical to v0.2.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U6ZF876ibkomShmV6rSKLn
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.
Release PR for
0.2.1. Bumpspackage.jsonand promotes## [Unreleased]in one commit — the process #23 established, and the first release to follow it.Shipped delta since
v0.2.0describeHookdeckPayloadreads string entries out ofbody.data, so a Hookdeck 422 that carries its reason there renders as a sentence instead of a raw JSON body (Read the error reason out ofdata, not justmessage#15)data, not justmessage#15)Developer Toolsremoved from both codex files;Communicationadded alongsideDevelopment; both nodes gainaliasentries the nodes panel searches (Make package.json the version, and fix the codex category n8n drops #23)package.jsonversion now tracks npm, enforced by a tag guard inpublish.ymland a CHANGELOG check inverify-package-load.mjs(Make package.json the version, and fix the codex category n8n drops #23)Everything else on
mainsincev0.2.0is repo-only —examples/,README.md,CONTRIBUTING.md, tests, thedemo-setup/deletion — and ships in no tarball.Why PATCH
No resource, operation, option or parameter added, renamed or removed. The node-identity check over
v0.2.0..mainfornodesandcredentialsreturns nothing, andSourceTypes.tsis byte-identical tov0.2.0.Not in this release: #16, which gives the action node the trigger's source questions. That is MINOR and becomes
0.3.0once it is rebased past #20 and reviewed.Verification
lint,scan,build,verify-package-load.mjs(37 checks — including the new one asserting0.2.1has a CHANGELOG section) and 109 unit tests pass locally.