Skip to content

chore(main): release 1.1.0#96

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

chore(main): release 1.1.0#96
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 6, 2026

🤖 I have created a release beep boop

1.1.0 (2026-03-06)

⚠ 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 full AI workflow suite (#75) (4a1d6fe)
  • add gh-aw agentic workflows and cspell config (#64) (9f90f33)
  • add rate limiting, README validation, and externalize init-worktree (#72) (97bfa05)
  • 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 best-practices permissions and add ref-scoped concurrency (#77) (f5806d5)
  • correct plugin.json schema violations for all 8 plugins (#33) (770b2b4)
  • finalize-pr: remove pre-PR steps from workflow diagram (#76) (6dca3fc)
  • git-guards: always scan subcommand for hook-path bypass pattern (#88) (63bd1c6)
  • git-guards: auto-allow git worktree remove (#54) (9d0bec6)
  • git-guards: check DENY patterns against extracted subcommand for git global options (#80) (48daad8)
  • git-guards: make test_graphql_guidance.py executable (2bbb4cf)
  • git-guards: use shlex tokenisation in hook-path fallback to prevent false positives (#93) (a0edfa0)
  • 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)
  • release: replace bump-minor-pre-major with versioning always-bump-minor (#89) (d8a1670)
  • 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)
  • sync-main: remove confirmation gates — merge immediately on invoke (#78) (0add171)
  • 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 6, 2026

Greptile Summary

This is an automated release PR generated by Release Please that promotes the repository from v1.0.0 to v2.0.0. The major version bump is justified by the breaking change: plugin consolidation and skill renames. The PR touches exactly three files — the Release Please manifest, the VERSION file, and a newly created CHANGELOG.md — all of which are updated consistently to 2.0.0.

  • .release-please-manifest.json: version field updated 1.0.02.0.0
  • VERSION: plain-text version updated 1.0.02.0.0
  • CHANGELOG.md (new file): auto-generated changelog covering ~25 features and ~20 bug fixes accumulated since v1.0.0, with a ⚠ breaking change entry for plugin consolidation and skill renames

All three files are internally consistent; no logic or code changes are introduced by this PR.

Confidence Score: 5/5

  • This PR is safe to merge — it contains only auto-generated version metadata and changelog with no executable code changes.
  • All three changed files are purely administrative (version strings and a generated changelog). The changes are consistent with each other and produced by the trusted Release Please automation. There is zero risk of runtime regressions.
  • No files require special attention.

Important Files Changed

Filename Overview
.release-please-manifest.json Version bumped from 1.0.0 to 2.0.0 in the Release Please manifest; consistent with the other version files.
CHANGELOG.md New CHANGELOG.md auto-generated by Release Please; documents all features and bug fixes included in the 2.0.0 release along with the breaking change note for plugin consolidation and skill renames.
VERSION Plain-text VERSION file bumped from 1.0.0 to 2.0.0; consistent with the manifest and changelog.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([Commits merged to main since v1.0.0]) --> B[Release Please bot detects\nconventional commits]
    B --> C{Major bump triggered\nby BREAKING CHANGE}
    C --> D[Bump .release-please-manifest.json\n1.0.0 → 2.0.0]
    C --> E[Bump VERSION\n1.0.0 → 2.0.0]
    C --> F[Generate CHANGELOG.md\nwith all features & fixes]
    D & E & F --> G([PR #96 merged → v2.0.0 tag created])
Loading

Last reviewed commit: 495ee2f

@github-actions github-actions bot changed the title chore(main): release 2.0.0 chore(main): release 1.1.0 Mar 6, 2026
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 495ee2f to 11b8c41 Compare March 6, 2026 23:18
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 11b8c41 to 2dd1fb1 Compare March 6, 2026 23:19
@JacobPEvans JacobPEvans enabled auto-merge (squash) March 6, 2026 23:29
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.

0 participants