---
title: "pygments Breaking Changes on PyPI | Since.dev"
description: "What each pygments release removed, renamed or changed: 3 breaking changes in 1 version on PyPI, each with its source."
canonical_url: https://since.dev/packages/pypi/pygments
last_updated: 2026-03-29
---

# pygments breaking changes

Every breaking API change we have recorded in pygments on PyPI: 3 breaking changes in 1 version. Below are its newest version, removals and renames first, each with its source.

Newest change March 29, 2026

## 2.20.0

3 breaking changes, first published March 29, 2026.

- **Removed**  

Python 3.8 is no longer supported; Python 3.14 is added as a supported version. [github.com](https://github.com/pygments/pygments/releases/tag/2.20.0)
- **Renamed** `Coq`  

The Coq lexer is renamed to Rocq. Code that refers to the old Coq name should switch to Rocq. [github.com](https://github.com/pygments/pygments/releases/tag/2.20.0)
- **Renamed** `pygments.lexers.theorem.CoqLexer`  

Use pygments.lexers.theorem.RocqLexer instead. [pypi.org](https://pypi.org/project/Pygments/2.20.0/)

## Check your code

These are the changes. To see which of them reach your code, [scan a public repository](https://since.dev/scan.md), or have your coding agent call `check_code` with your manifest or lockfile over [MCP](https://since.dev/docs.md#mcp). [The API](https://since.dev/docs.md#api) reads every change in every version, not only the newest. On Team and up, a fix pull request opens for the changes that reach a connected repository. Nothing merges or deploys.

## Put your code on continuous management.

Scan a public repository now, or give your agent one line.

### See how out of date your code is.

[Scan a repository](https://since.dev/scan.md). Any public GitHub repository. No sign-in.

### Tell your agent what changed since it was trained.

`claude mcp add --transport http since https://api.since.dev/mcp`

---

Every page on this site as Markdown: https://since.dev/sitemap.md. For agents: https://since.dev/llms.txt.