The using-scribe SKILL.md gained the "Where a new rule goes" rule-scope section in 50b6902, but plugin.json wasn't bumped — so autoUpdate clients stay on 0.1.3 and never reinstall the new skill content. This bump (0.1.3 → 0.1.4) propagates it.
Verified on disk before this: the marketplace clone and all cached versions (0.1.0–0.1.3) still carry the stale SKILL.md.
MCP tool descriptions are independent of this — they're served live by the remote app and refresh on the next session's MCP handshake, not via the plugin bundle.
CI note:plugin/** isn't in the .forgejo/workflows/ci.yml paths filter, so no CI runs for this change (nothing to typecheck/test/build).
The `using-scribe` SKILL.md gained the "Where a new rule goes" rule-scope section in 50b6902, but `plugin.json` wasn't bumped — so `autoUpdate` clients stay on 0.1.3 and never reinstall the new skill content. This bump (0.1.3 → 0.1.4) propagates it.
Verified on disk before this: the marketplace clone and all cached versions (0.1.0–0.1.3) still carry the stale SKILL.md.
MCP tool descriptions are independent of this — they're served live by the remote app and refresh on the next session's MCP handshake, not via the plugin bundle.
**CI note:** `plugin/**` isn't in the `.forgejo/workflows/ci.yml` paths filter, so no CI runs for this change (nothing to typecheck/test/build).
Refs #755
🤖 Generated with [Claude Code](https://claude.com/claude-code)
SKILL.md gained the 'Where a new rule goes' section (rule-scope model) in
50b6902 but plugin.json was not bumped, so autoUpdate clients stay on 0.1.3
and never reinstall the new skill content. Bump to propagate.
(MCP tool descriptions are unaffected by this — they are served live by the
remote app and refresh on the next session's MCP handshake, not via the
plugin bundle.)
Refs #755
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
using-scribeSKILL.md gained the "Where a new rule goes" rule-scope section in50b6902, butplugin.jsonwasn't bumped — soautoUpdateclients stay on 0.1.3 and never reinstall the new skill content. This bump (0.1.3 → 0.1.4) propagates it.Verified on disk before this: the marketplace clone and all cached versions (0.1.0–0.1.3) still carry the stale SKILL.md.
MCP tool descriptions are independent of this — they're served live by the remote app and refresh on the next session's MCP handshake, not via the plugin bundle.
CI note:
plugin/**isn't in the.forgejo/workflows/ci.ymlpaths filter, so no CI runs for this change (nothing to typecheck/test/build).Refs #755
🤖 Generated with Claude Code