You'll notice
Plugin release git tags now get signed using your git signing configuration
What
When Claude Code creates a git tag for a plugin release, it now reads your git commit/tag signing configuration and applies it when creating the tag. If that configuration can't be read, it falls back to creating an unsigned tag and shows a warning that the tag was created unsigned. The tag creation now also runs through a sanitized, isolated environment.
Why
This lets plugin release tags be signed the same way your other git tags are, instead of always being created unsigned, while still working (with a clear warning) if signing configuration isn't available.