Skip to content

[v1.x] Set Development Status classifier to Production/Stable#2976

Open
maxisbey wants to merge 1 commit into
v1.xfrom
v1.x-dev-status-classifier-stable
Open

[v1.x] Set Development Status classifier to Production/Stable#2976
maxisbey wants to merge 1 commit into
v1.xfrom
v1.x-dev-status-classifier-stable

Conversation

@maxisbey

Copy link
Copy Markdown
Contributor

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

  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling — n/a
  • I have added or updated documentation as needed

Additional context

AI Disclaimer

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.
@maxisbey maxisbey marked this pull request as ready for review June 25, 2026 17:45

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 1 file

Re-trigger cubic

@claude claude Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants