chore: prepare v1.52.1 release

[erraggy]

Summary

• Pre-release preparation for v1.52.1
• Includes CI benchmark results

Checklist

• All tests pass
• Benchmarks recorded
• Documentation reviewed

---

🤖 Generated by prepare-release.sh

[coderabbitai]

📝 Walkthrough

Walkthrough

Version bump from 1.52.0 to 1.52.1 applied to two configuration files. Benchmark data for the new version added. No functional code changes introduced.

Changes

Cohort / File(s)	Summary
Configuration Version Bumps .claude-plugin/marketplace.json, plugin/.claude-plugin/plugin.json	Version field updated from 1.52.0 to 1.52.1 in both configuration files.
Benchmark Data benchmarks/benchmark-v1.52.1.txt	New file containing Go benchmark results across multiple packages (parser, validator, fixer, httpvalidator, converter, joiner, differ, generator, builder, walker) with metrics including ns/op, bytes allocated, and allocs/op.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: prepare v1.51.4 release #325 — Performs identical release-prep changes: bumping plugin version in both configuration files and adding benchmarks file.
• chore: prepare v1.51.5 release #331 — Makes the same code-level changes to version fields and adds corresponding benchmarks file for the new release.
• chore: prepare v1.51.6 release #336 — Updates the same plugin version fields and adds a release-specific benchmarks file.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: prepare v1.52.1 release' directly and clearly describes the main purpose of the changeset: preparing a release for version 1.52.1.
Description check	✅ Passed	The description is directly related to the changeset, explaining the pre-release preparation for v1.52.1 and the inclusion of CI benchmark results, which aligns with the actual changes made.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/v1.52.1-release-prep

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.78%. Comparing base (bdf626c) to head (bbcd8e2).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #345   +/-   ##
=======================================
  Coverage   84.78%   84.78%           
=======================================
  Files         193      193           
  Lines       27249    27249           
=======================================
  Hits        23102    23102           
  Misses       2828     2828           
  Partials     1319     1319           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@benchmarks/benchmark-v1.52.1.txt`:
- Around line 1-364: You modified a generated benchmark file in the protected
benchmarks directory; revert the change to the added benchmark file
(benchmark-v1.52.1.txt), do not commit direct edits to benchmarks/, and instead
follow the documented process in BENCHMARK_UPDATE_PROCESS.md (regenerate via the
CI/workflow or run prepare-release.sh as specified) and confirm compliance with
AGENTS.md and GEMINI.md rules before re-submitting the PR.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Guideline violation: benchmarks/ directory must not be modified directly.

Both AGENTS.md and GEMINI.md rules prohibit modifying this directory; the prescribed path is BENCHMARK_UPDATE_PROCESS.md. Even though this file was produced by the CI benchmark workflow via prepare-release.sh, it still needs to land through whatever merge/commit mechanism that document describes. Please confirm this addition follows BENCHMARK_UPDATE_PROCESS.md before merging.

As per coding guidelines, "benchmarks/**: Do not modify benchmarks/ directory - see BENCHMARK_UPDATE_PROCESS.md for proper benchmark update procedures."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@benchmarks/benchmark-v1.52.1.txt` around lines 1 - 364, You modified a
generated benchmark file in the protected benchmarks directory; revert the
change to the added benchmark file (benchmark-v1.52.1.txt), do not commit direct
edits to benchmarks/, and instead follow the documented process in
BENCHMARK_UPDATE_PROCESS.md (regenerate via the CI/workflow or run
prepare-release.sh as specified) and confirm compliance with AGENTS.md and
GEMINI.md rules before re-submitting the PR.