Chore/unpin openapi spec validator and update target python versions by v-v-v-v-v-v-v-v · Pull Request #103 · stax-labs/lib-stax-python-sdk

v-v-v-v-v-v-v-v · 2026-03-30T04:54:20Z

What kind of change does this PR introduce?
- Unpins openapi-spec-validator. This is because the version it is currently pinned at (0.2.9) uses some deprecated/obsolete imports that would require setuptools to be pinned to 81.0.0 or lower for the SDK to continue working. More importantly, openapi-spec-validator is severely out of date, the latest version is 0.8.4. By unpinning openapi-spec-validator, the hope is that there should be less need to pin other dependencies just to support the Stax SDK.

Also updates classifiers and other targets to indicate that the Stax SDK supports at minimum Python 3.9; I believe this has been somewhat indicated with build jobs targetting 3.9, but this is explicit now.

What is the current behavior?
- Assuming a version of Python with the Stax SDK installed and setuptools at version >81.0.0, importing openapi_spec_validator will result in the following:

Traceback (most recent call last):
  File "<python-input-1>", line 1, in <module>
    import openapi_spec_validator
  File "/var/venv/lib/python3.13/site-packages/openapi_spec_validator/__init__.py", line 6, in <module>
    from openapi_spec_validator.schemas import get_openapi_schema
  File "/var/venv/lib/python3.13/site-packages/openapi_spec_validator/schemas.py", line 4, in <module>
    from pkg_resources import resource_filename
ModuleNotFoundError: No module named 'pkg_resources'

pkg_resources is deprecated and removed from newer versions of setuptools.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
- Unlikely, but worth pointing out that the SDK requires Python 3.9 or higher, which we also indicate in our classifiers. To minimise disruption across different versions of Python between 3.9 and 3.13, the GitHub Actions workflow for building and testing now includes a mapping for multiple Python versions.

…ate-target-python-versions

sentry · 2026-04-30T04:26:27Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (a98d1e5) to head (8b45b3a).

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #103   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          515       514    -1     
=========================================
- Hits           515       514    -1

Files with missing lines	Coverage Δ
staxapp/__init__.py	`100.00% <100.00%> (ø)`
staxapp/config.py	`100.00% <100.00%> (ø)`
staxapp/contract.py	`100.00% <ø> (ø)`
staxapp/openapi.py	`100.00% <100.00%> (ø)`

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Levence · 2026-04-30T04:38:23Z

        uses: actions/setup-python@82c7e631bb3cdc910f68e0081d67478d79c6982d # 5.1.0
        with:
-          python-version: '3.9'
+          python-version: ${{ matrix.python-version }}


Levence · 2026-04-30T04:38:39Z

@@ -1 +1 @@
-__version__ = "1.3.1"
+__version__ = "1.3.2"


atleast a 1.4.0 :P

You can clearly see when things started out as "bump a few dependencies" into something much more involved. 😛 Will bump the version proper.

Levence · 2026-04-30T04:40:05Z

                method = path[method_type]

-                operation = method.get("operationId", "").split(".")
+                operation = method.get("x-stax-sdk-operation-id", "").split(".")


looks pretty straightforward

Levence · 2026-04-30T04:56:13Z

    @classmethod
    def schema_url(cls):
-        return f"https://{cls.hostname}/{cls.API_VERSION}/public/api-document"
+        return f"https://{cls.hostname}/{cls.API_VERSION}/public/oas3-document"


I think it would be good to have some tests to validate the current calls are still valid. The sdk knows about these, for example:

>>> accounts.ffff() Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/levence/.pyenv/versions/3.9.20/lib/python3.9/site-packages/staxapp/openapi.py", line 100, in stax_wrapper raise ValidationException( staxapp.exceptions.ValidationException: No such operation: ffff for accounts. Please use one of ['UpdateAccountTypeMembers', 'ReadAccounts', 'CreateAccount', 'CloseAccount', 'DiscoverAccounts', 'OnboardAccount', 'ReadAccountTypes', 'CreateAccountType', 'UpdateAccountTypeAccess', 'DeleteAccountType', 'UpdateAccountType', 'UpdateAccount', 'ReadAccountPolicyAttachments'] accounts.UpdateAccount(x=1) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/levence/.pyenv/versions/3.9.20/lib/python3.9/site-packages/staxapp/openapi.py", line 122, in stax_wrapper raise ValidationException( staxapp.exceptions.ValidationException: Missing one or more parameters: ['account_id']

There is probably a smart way to retrieve these on the old schema and assert in the new schema yeah?

v-v-v-v-v-v-v-v added 2 commits March 30, 2026 15:15

chore(deps): unpin openapi-spec-validator dependency

55f2706

chore(platform): update target python versions to 3.9 minimum up to 3.13

5b1562d

v-v-v-v-v-v-v-v requested a review from a team March 30, 2026 04:54

v-v-v-v-v-v-v-v added 2 commits March 30, 2026 15:56

chore(deps): add setuptools as an explicit dependency

2470478

chore(platform): derive schema and operations from oas3 spec

5074843

v-v-v-v-v-v-v-v requested a review from a team as a code owner April 30, 2026 04:14

Merge branch 'master' into chore/unpin-openapi-spec-validator-and-upd…

8b45b3a

…ate-target-python-versions

v-v-v-v-v-v-v-v force-pushed the chore/unpin-openapi-spec-validator-and-update-target-python-versions branch from 1c77fc2 to 8b45b3a Compare April 30, 2026 04:24

Levence reviewed Apr 30, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Chore/unpin openapi spec validator and update target python versions#103

Chore/unpin openapi spec validator and update target python versions#103
v-v-v-v-v-v-v-v wants to merge 5 commits intomasterfrom
chore/unpin-openapi-spec-validator-and-update-target-python-versions

v-v-v-v-v-v-v-v commented Mar 30, 2026

Uh oh!

sentry Bot commented Apr 30, 2026

Uh oh!

Levence Apr 30, 2026

Uh oh!

Levence Apr 30, 2026

Uh oh!

v-v-v-v-v-v-v-v Apr 30, 2026

Uh oh!

Levence Apr 30, 2026

Uh oh!

Levence Apr 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		@@ -1 +1 @@
		__version__ = "1.3.1"
		__version__ = "1.3.2"

Conversation

v-v-v-v-v-v-v-v commented Mar 30, 2026

Uh oh!

sentry Bot commented Apr 30, 2026

Codecov Report

Uh oh!

Levence Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

Levence Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

v-v-v-v-v-v-v-v Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

Levence Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

Levence Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants