Skip to content
CodeMop

Changelog

What changed in each release of the codemop package and the GitHub Action. The format follows Keep a Changelog, and versions follow semantic versioning.

1.0.1 (2026-10-23)

Section titled “1.0.1 (2026-10-23)”

Changed

Section titled “Changed”
  • The Action’s icon on the GitHub Marketplace is a yellow droplet (the wet floor), not a tick
  • The README, which is also the PyPI and Marketplace page, starts with Moppy and shows a real review

1.0.0 (2026-10-23)

Section titled “1.0.0 (2026-10-23)”

The first release of the GitHub Action.

Added

Section titled “Added”
  • The GitHub Action (uses: sgtwickool/codemop@v1): reviews every pull request, including ones from forks, on pull_request_target, without checking out or running their code
  • codemop review --post: posts the review on the pull request, as a comment on each issue with a one-click suggestion where there’s a fix, and one summary comment that later reviews update in place. A commit already reviewed isn’t reviewed again
  • Fixes you tick: a checkbox in the summary for each fix, and Commit the ticked fixes, which commits everything ticked as one commit (codemop apply). One problem in several places is one checklist item
  • Learning: resolving a conversation dismisses its issue for the pull request; replying /codemop learn <why> adds a note to .codemop-learned.yml, so it isn’t raised again in the repository (codemop learn)
  • Re-reviews: a new push is reviewed from the last commit reviewed, raising only bugs and security issues; conversations whose code has been fixed are resolved
  • The merge check: with merge_check: true in .codemop.yml, a “CodeMop” commit status that fails while bugs or security issues are open, for branch protection to require; /codemop check updates it (codemop check)
  • A “Reviewed by CodeMop” badge for READMEs, and a link to codemop.com in the summary’s footer
  • Received, at a glance: 👀 on the comment within seconds of ticking Commit the ticked fixes or commenting /codemop check or /codemop learn, taken off when it’s done, and 😕 if it failed
  • Repository context, on by default: the whole of each changed function, where the changed code is used in other files, and the definitions it uses, for Python, TypeScript and JavaScript. A finding can say where it shows up outside the diff, and changing it there counts as addressing it. --no-context, or the Action’s context: false, turns it off
  • --max-changed-lines N: doesn’t review a diff larger than this (a cost limit)
  • Each suggested fix is checked to fit the lines it replaces, and left out if it doesn’t

Changed

Section titled “Changed”
  • Licensed under Apache 2.0, from MIT (0.1.0 stays MIT), with a NOTICE file. The name, the logo and Moppy are trademarks: see TRADEMARKS.md

Fixed

Section titled “Fixed”
  • Reading pull requests with more than 100 comments
  • Ticks made on GitHub’s web page (which saves the comment with Windows line endings)
  • GitHub requests that fail briefly are tried again

0.1.0 (2026-10-09)

Section titled “0.1.0 (2026-10-09)”

The first release on PyPI: codemop review reviews a pull request (owner/repo#123 or a URL) or a diff on stdin and prints the issues it finds, with a fix where it has one, and the cost.

  • Providers: Anthropic (the default, Claude Opus 5.5 at high effort, chosen by the review eval), Mistral, OpenAI, OpenRouter, Ollama and any OpenAI-compatible endpoint
  • .codemop.yml on the default branch says how a repository is reviewed (ignored paths, minimum confidence, chunk size), and can’t choose the provider or model
  • --json for scripts