Skip to content

Repository navigation

chore: prepare email metadata patch 0.52.1 #340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
m1ngshum merged 1 commit into from
Nov 9, 2026
Merged

chore: prepare email metadata patch 0.52.1 #340

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,13 @@ _Add entries here, never under a stamped version_ — a release commit renames t
heading, and a branch that wrote beneath it merges without conflict straight into a
published section (it happened to #170).

## [0.52.1] - 2026-11-10

### Changed

- Publish an email-metadata patch using the verified npm maintainer contact `hello@m1ngshum.com`; runtime code and dependencies are unchanged from 0.52.0. Historical npm versions retain their original metadata.
- Keep guard-playground and mcp-guardbench pinned to their tested 0.52.0 baseline for this metadata-only patch; no companion merge or deployment is included.

## [0.52.0] - 2026-11-08

### Added
Expand Down
Loading