From d26d3736ecc2c08bacbba508de643184e73ffd85 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 30 Jul 2026 23:02:12 +0000 Subject: [PATCH] Restore setuptools_scm dynamic versioning reverted by SDK regeneration The SDK regeneration in #45 reverted the PLAT-193 fix (a1fa54f): pyproject.toml went back to a hardcoded version = "1.0.0", so every tag push built opal_security-1.0.0, which already exists on PyPI, and twine --skip-existing silently skipped the upload. Re-apply the fix (dynamic version via setuptools_scm) and add pyproject.toml to .openapi-generator-ignore so regeneration cannot revert it again. Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01Ssy8nmvQp1U5d73pCMFNXi --- .openapi-generator-ignore | 5 +++++ pyproject.toml | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/.openapi-generator-ignore b/.openapi-generator-ignore index 7484ee5..8570bfd 100644 --- a/.openapi-generator-ignore +++ b/.openapi-generator-ignore @@ -21,3 +21,8 @@ #docs/*.md # Then explicitly reverse the ignore rule for a single file: #!docs/README.md + +# pyproject.toml is hand-maintained: it uses setuptools_scm dynamic versioning +# (PLAT-193) so releases derive their version from git tags. Regenerating it +# would revert to a hardcoded version and silently break PyPI publishing. +pyproject.toml diff --git a/pyproject.toml b/pyproject.toml index bfd1432..4bed9f2 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "opal_security" -version = "1.0.0" +dynamic = ["version"] description = "Opal API" authors = [ {name = "Opal Team",email = "hello@opal.dev"}, @@ -32,7 +32,7 @@ mypy = ">= 1.5" [build-system] -requires = ["setuptools"] +requires = ["setuptools", "setuptools_scm"] build-backend = "setuptools.build_meta" [tool.pylint.'MESSAGES CONTROL']