Skip to content

v0.2.0

Choose a tag to compare

View all tags
@leggetter leggetter released this 21 Aug 13:06
· 16 commits to main since this release
v0.2.0
dde66f0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Summary

The Hookdeck Event Gateway Trigger no longer appears in an AI Agent's tool list. It was
never usable there — a trigger waits for Hookdeck to deliver an event, so an agent that
picked it got a tool it could not call. The Hookdeck Event Gateway action node is still
available as a tool, and is the one you want an agent using.

This is the only change to the nodes themselves since v0.1.0. Everything else in the range
is tests, CI and documentation.

Upgrading is enough — there is nothing to reconfigure and no need to republish a workflow.

Fixes

  • An AI Agent's tool list no longer offers Hookdeck Event Gateway Trigger Tool. n8n
    generated that entry automatically because the trigger declared itself usable as a tool;
    an agent that selected it wasted a turn on something that cannot be invoked. Removing it
    also brings the package in line with n8n's current community-node rules, which now treat a
    trigger opting into the tool picker as an error.

Internal

  • @n8n/scan-community-package 0.31.0 → 0.32.0, @n8n/node-cli 0.42.2 → 0.44.5.
    The newer scanner is what flags a trigger opting into the tool picker; a caret range on a
    0.x version could not reach the new minor, so the check kept passing against the old rule.
  • Live test suites consolidated under test/live and hardened against the Hookdeck API rate
    limit.

Full Changelog: v0.1.0...v0.2.0

Assets 2
Loading