Skip to content

chore(main): release 2.0.0#71

Open
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main
Open

chore(main): release 2.0.0#71
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Mar 5, 2026

🤖 I have created a release beep boop

2.0.0 (2026-03-05)

⚠ BREAKING CHANGES

  • Plugin consolidation and skill renames

Features

  • add ci and local test automation (#41) (181c6a5)
  • add codeql-resolver plugin with 3-tier resolution architecture (#8) (a45ac3b)
  • add gh-aw agentic workflows and cspell config (#64) (9f90f33)
  • add token-validator and issue-limiter plugins (#2) (8a64289)
  • add webfetch-guard and markdown-validator plugins (705dbe8)
  • adopt conventional branch standard (feature/, bugfix/) (#74) (e826b67)
  • ci: add release-please and improve renovate auto-merge (#53) (94fbaca)
  • consolidate plugins from 15 to 8 with consistent naming (#31) (d36a028)
  • enhance resolve-pr-threads with comment reading (#46) (fc6a34c)
  • finalize-pr: add multi-PR modes, bot support, and skill authoring guidance (#70) (7704876)
  • finalize-pr: add Phase 4 to auto-update PR metadata (#65) (1c1e881)
  • git-guards: add GraphQL command guidance for known failure patterns (232eee3)
  • git-guards: allow git rm without confirmation (#63) (c94d959)
  • git-guards: block gh pr comment, enforce GraphQL review threads (#56) (c6b6234)
  • git-permission-guard: add centralized git/gh permission hook plugin (#12) (12268b0)
  • git-rebase-workflow: handle branch protection with CodeQL scanning (#25) (9b40416)
  • github-workflows: add trigger-ai-reviews skill (#47) (b505c82)
  • main-branch-guard: add PreToolUse hook to block main branch edits (#22) (9456f5d)
  • markdown-validator: add skip logic and MD013 fallback (#27) (77cd37b)
  • migrate 13 commands to skills in 6 new plugins (#23) (fb72d06)
  • pr-review-toolkit: add PR review thread resolution plugin (#24) (3368eaa)
  • process-cleanup: add Stop hook plugin for orphaned MCP process cleanup (#51) (27caa6f)
  • renovate: extend shared preset for org-wide auto-merge rules (#60) (b5197ed)
  • webfetch-guard: add grace period for previous year searches (#9) (18a39a5)

Bug Fixes

  • add explicit GITHUB_TOKEN permissions to workflow (a8f44d3)
  • agents-md: add resolve-pr-threads and shape-issues to github-workflows entry (81e61be)
  • ci: dispatch flake update to nix-ai instead of nonexistent nix repo (#73) (1ed7c40)
  • codeql-resolver: convert flat skill files to skill directories (#59) (81ab6af)
  • content-guards: clarify extract-to-files means committed artifacts (#62) (ed82608)
  • content-guards: handle empty config_flag array in bash 3.2 (#55) (0385c9b)
  • content-guards: improve token-validator error message with detailed resolution steps (#37) (cf355e3)
  • content-guards: resolve unbound variable error in markdown validator (#39) (2202144)
  • content-guards: support markdown linting in git worktrees (#48) (8cbf6a1)
  • convert GraphQL queries to single-line format in resolve-pr-threads (#35) (0b482c5)
  • correct plugin.json schema violations for all 8 plugins (#33) (770b2b4)
  • git-guards: auto-allow git worktree remove (#54) (9d0bec6)
  • git-guards: make test_graphql_guidance.py executable (2bbb4cf)
  • git-guards: use word-boundary regex for mutation name detection (3db588f)
  • improve GraphQL reliability and prevent git-guard false positives (500d893)
  • markdown-validator: bundle default config and add fallback resolution (#26) (103a108)
  • markdown-validator: use global markdownlint config with MD013=160 (#11) (326c27b)
  • prevent main-branch-guard from blocking non-repository files (#36) (7abe699)
  • replace jq != operator and add markdownlint troubleshooting (#68) (3c61cb5)
  • resolve-pr-threads: cut 40% of lines to eliminate hallucination failure modes (#52) (949151c)
  • resolve-pr-threads: rewrite negation rules as affirmative clarity (#58) (d5a25c4)
  • revert to cclint@latest (no versions published yet) (55c2488)
  • squash-merge-pr: use --delete-branch, git switch main, and consistent placeholder style (b2743f7)
  • squash-merge-pr: use @ import syntax and document git-workflows dependency (479baef)
  • use correct flake input name jacobpevans-cc-plugins (#28) (8c18e26)
  • use Go to install cclint, validate both plugins (0e0890c)

This PR was generated with Release Please. See documentation.

@greptile-apps
Copy link

greptile-apps bot commented Mar 5, 2026

Greptile Summary

This is an auto-generated Release Please PR that cuts the v2.0.0 release for claude-code-plugins, bumping all three version-tracking artifacts (VERSION, .release-please-manifest.json, and the newly created CHANGELOG.md) from 1.0.0 to 2.0.0. The major-version bump is warranted given the breaking change (plugin consolidation and skill renames) noted in the changelog. No application logic is modified; the PR is purely a versioning and changelog record.

  • .release-please-manifest.json — root package version updated to "2.0.0"
  • VERSION — plain-text version file updated to 2.0.0
  • CHANGELOG.md — new file generated by Release Please, capturing 23 features and 22 bug fixes since v1.0.0, including all PR/commit links

Confidence Score: 5/5

  • This PR is safe to merge — it contains only auto-generated version bumps and a changelog with no logic changes.
  • All three changed files are standard Release Please artifacts. Version numbers are consistent across every file (all read 2.0.0). The CHANGELOG accurately reflects accumulated commits. No code, hooks, scripts, or configuration beyond versioning is touched.
  • No files require special attention.

Important Files Changed

Filename Overview
.release-please-manifest.json Version bumped from "1.0.0" to "2.0.0" by Release Please automation — no issues found.
CHANGELOG.md New file created by Release Please; documents all features and bug fixes accumulated since v1.0.0, with correct links and commit SHAs — no issues found.
VERSION Version string updated from "1.0.0" to "2.0.0", consistent with the other two changed files — no issues found.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Commits merged to main\nsince v1.0.0] --> B[Release Please bot\ndetects version bump needed]
    B --> C{Breaking change\nin commits?}
    C -- Yes\nPlugin consolidation & renames --> D[Bump MAJOR version\n1.0.0 → 2.0.0]
    D --> E[Update VERSION\n1.0.0 → 2.0.0]
    D --> F[Update .release-please-manifest.json\n1.0.0 → 2.0.0]
    D --> G[Generate CHANGELOG.md\nfrom conventional commits]
    E & F & G --> H[Open PR #71\nchore: release 2.0.0]
    H --> I[Merge → GitHub tag v2.0.0\n& release created]
Loading

Last reviewed commit: 944447f

@JacobPEvans JacobPEvans self-requested a review March 5, 2026 13:43
Copy link
Owner

@JacobPEvans JacobPEvans left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bots are not allowed to initiate major version updates.

@github-actions github-actions bot force-pushed the release-please--branches--main branch from 944447f to b75bfd2 Compare March 5, 2026 13:45
@github-actions github-actions bot force-pushed the release-please--branches--main branch from b75bfd2 to 5cc40e5 Compare March 5, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant