Skip to content

chore: prepare the 2.0.2 release - #62

Merged
gugarosa merged 1 commit into
mainfrom
release/opfython-2.0.2
Sep 6, 2026
Merged

gugarosa merged 1 commit into
mainfrom
release/opfython-2.0.2

Conversation

@gugarosa

@gugarosa gugarosa commented Sep 6, 2026

Copy link
Copy Markdown
Owner

Purpose

Prepare 2.0.2 for the release requested after #61 was reviewed and merged. Version 2.0.1 is already published on GitHub/PyPI and cannot be reused for the new code.

Changes

Only three version values change from 2.0.1 to 2.0.2:

  • opfython/__init__.py
  • pyproject.toml
  • the OPFython project entry in uv.lock

There are no implementation, dependency, or Python-support changes beyond the already reviewed #61 merge.

Validation

The merged #61 commit passed main-branch CI. The version declarations and generated wheel metadata agree on 2.0.2, wheel/source builds succeed, and existing quality hooks pass.

Release gate

This PR remains open for maintainer review; auto-merge is not enabled. After it is merged and CI succeeds for its exact main merge commit, publish v2.0.2 through the existing GitHub-release/PyPI workflow. Do not move or overwrite the existing v2.0.1 tag or distributions.

Bump only the package, project metadata, and locked project version after the reviewed quality changes in PR #61. Preserve all implementation code, dependency versions, and Python support.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 804ac811-6a11-4d29-8526-ab1643abf900
@gugarosa
gugarosa merged commit 10c58ec into main Sep 6, 2026
8 checks passed
@gugarosa
gugarosa deleted the release/opfython-2.0.2 branch October 4, 2026 19:04
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.

1 participant