Skip to content

fix: remove redundant hooks declaration from plugin.json - #5

Merged
nextbridgehq merged 1 commit into
mainfrom
fix/remove-redundant-hooks-declaration
Sep 14, 2026
Merged

nextbridgehq merged 1 commit into
mainfrom
fix/remove-redundant-hooks-declaration

Conversation

@nextbridgehq

@nextbridgehq nextbridgehq commented Sep 14, 2026 •

Copy link
Copy Markdown
Owner

Summary

.claude-plugin/plugin.json declares "hooks": "./hooks/hooks.json", which
the plugin runtime already loads by convention (the standard
hooks/hooks.json path). Declaring it explicitly causes plugin installation
to fail with:

Hook load failed: Duplicate hooks file detected: ./hooks/hooks.json resolves
to already-loaded file ...\hooks\hooks.json. The standard hooks/hooks.json is
loaded automatically, so manifest.hooks should only reference additional...

Confirmed via a clean, isolated install from this repo's current main
(45bbf22816d2f1e98e44d2c0a0e34f9799ed7539): the plugin installs but fails to
load.

Background

This exact fix was already made and merged into a local working copy of this
repository during an earlier hardening pass, but never reached this
repository — so the fix effectively regressed the moment anyone did a fresh
install rather than reusing that already-patched local checkout. This PR
publishes that fix for real.

Change

One line removed, nothing else:

   "author": {
     "name": "Nextbridge"
   },
-  "hooks": "./hooks/hooks.json",
   "license": "MIT",

Verification

  • .claude-plugin/plugin.json still parses as valid JSON.
  • git diff --check clean (no whitespace errors).
  • git diff --stat confirms exactly one file, one deleted line — no version
    bump, no lockfile change, no other file touched (version bumping is left to
    release-please, per this repo's existing convention).

@nextbridgehq
nextbridgehq merged commit c42c173 into main Sep 14, 2026
2 checks passed
@nextbridgehq
nextbridgehq deleted the fix/remove-redundant-hooks-declaration branch September 14, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants