[v1.x] Set Development Status classifier to Production/Stable - #2976
Conversation
Sorry, something went wrong.
The 1.x line has been in wide production use for well over a year; the classifier has read 'Beta' since the project was first published in Nov 2024. Companion to #2975 on main.
There was a problem hiding this comment.
LGTM — straightforward one-line trove classifier bump, metadata only.
Extended reasoning...Overview
The PR changes a single line in pyproject.toml: the Development Status trove classifier goes from 4 - Beta to 5 - Production/Stable. No code, dependencies, or build configuration are touched.
Security risks
None. This is package metadata only; it has no effect on runtime behavior, dependency resolution, or the published code.
Level of scrutiny
Minimal scrutiny is warranted. The change is a one-line, purely descriptive metadata update for the next 1.x release, with no functional impact. The stated rationale (the 1.x line has been in wide production use) is consistent with the project's status, and a companion PR (#2975) covers the broader rationale.
Other factors
The bug hunting system found no issues, and there are no outstanding reviewer comments on the PR. The change is self-contained and trivially reversible.
Sorry, something went wrong.
Companion to #2975 — bumps the Development Status trove classifier on the stable line from 4 - Beta (unchanged since the project was first published in Nov 2024) to 5 - Production/Stable.
Motivation and Context
The 1.x line has been in wide production use for well over a year; Beta no longer reflects reality. See #2975 for the full rationale on treating this classifier as project maturity rather than per-release stage.
PyPI classifiers are immutable on existing uploads, so this takes effect with the next 1.x release.
How Has This Been Tested?
n/a — metadata only.
Breaking Changes
None.
Types of changes
Checklist
Additional context
AI Disclaimer