chore(deps): bump @hono/node-server from 1.19.14 to 1.19.17

[dependabot]

Bumps @hono/node-server from 1.19.14 to 1.19.17.

Commits

• 71941da 1.19.17
• 0208500 ci: add stage option for publishing (#386)
• cbdf713 1.19.16
• 86e96c2 ci: add an action for trusted publisher (#385)
• 99c1a1a ci: run on v1.x branch pushes
• 84cb2ee Merge commit from fork
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​hono/node-server since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[cursor]

PR Summary

Low Risk
Patch/minor dependency updates with no direct code changes; impact is limited to transitive MCP/Hono server plumbing used by the Claude agent SDK.

Overview
Lockfile-only update bumping @hono/node-server from 1.19.14 to 1.19.17, with its hono peer moving 4.12.31 → 4.13.1.

That path comes in transitively through @modelcontextprotocol/sdk (used by @anthropic-ai/claude-agent-sdk in services/libs/anthropic-aws), so the lockfile also picks up related patch bumps in the MCP stack (e.g. jose, cors, ajv, express-rate-limit, eventsource-parser, and small Express 5 dependency tweaks). clearbit’s needle fork is recorded as a git resolution instead of a GitHub tarball URL, same commit.

No application source changes—only pnpm-lock.yaml.

^{Reviewed by Cursor Bugbot for commit bcb2f94. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit bcb2f94. Configure here.}

[cursor]

Lockfile forces SSH for needle

High Severity

The clearbit dependency’s needle resolution changed from a public HTTPS codeload tarball to a git clone of git@github.com:clearbit/needle.git. CI runs pnpm i --frozen-lockfile without GitHub SSH keys, so installs can fail with public-key errors even though the intended change is only the @hono/node-server bump.

Additional Locations (2)

• pnpm-lock.yaml#L15710-L15711
• pnpm-lock.yaml#L18577-L18578

 

^{Reviewed by Cursor Bugbot for commit bcb2f94. Configure here.}