warp-hr 0.3.0__tar.gz

warp_hr-0.3.0/.claude/skills/warp-python-sdk/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: warp-python-sdk
+description: "Python SDK for warp API. Use when writing Python code that calls warp API with the warp-hr package: installing it, constructing and authenticating the client, and calling API operations."
+---
+
+# warp Python SDK
+
+Generated Python client for warp API, published as `warp-hr`. Use the generated client instead of hand-writing HTTP requests.
+
+## Install
+
+```sh
+pip install warp-hr
+```
+
+## Client setup and authentication
+
+```python
+import os
+
+from warp_hr import Warp
+
+client = Warp(
+    api_key=os.environ.get("WARP_API_KEY"),
+)
+```
+
+Provide credentials using the options below. Environment variables are read automatically when the target runtime supports them:
+
+- `api_key` (env: `WARP_API_KEY`) — Credential for the apiKey scheme.
+
+## Calling operations
+
+```python
+import os
+
+from warp_hr import Warp
+
+client = Warp(
+    api_key=os.environ.get("WARP_API_KEY"),
+)
+
+health_plan = client.benefits.health_plans.list(
+    limit="limit",
+    statuses=["active"],
+)
+
+print(health_plan)
+```
+
+Method names, parameter shapes, and response types are generated from the API description — do not guess them. Look up the exact call signature in [api.md](../../../api.md) before writing a call.
+
+## Error handling
+
+Non-success responses throw generated API errors. Error objects expose status, headers, response body, and request metadata where the target runtime supports it.
+
+```python
+from warp_hr import APIStatusError
+
+try:
+    health_plan = client.benefits.health_plans.list(
+        limit="limit",
+        statuses=["active"],
+    )
+except APIStatusError as err:
+    print(err.status_code, err.message)
+    raise
+```
+
+## Requirements
+
+- Python 3.9 or newer
+
+## Reference files
+
+- [README.md](../../../README.md) — full feature tour: client options, retries and timeouts, webhooks, logging.
+- [api.md](../../../api.md) — complete catalogue of every operation with request and response types.

warp_hr-0.3.0/.github/workflows/release-please.yml

@@ -0,0 +1,127 @@
+name: Release Please
+
+on:
+  # A release is cut when a human merges the platform-managed release PR into
+  # main (the PR's base, so its diff shows the full pending release).
+  # Every other push here runs release-please as well — commits written straight to
+  # this branch included — and cuts nothing, there being no release commit at the tip.
+  push:
+    branches:
+      - main
+    # The Scalar platform pushes these workflow files straight to main to keep them
+    # current between releases; that is bookkeeping, never a release. Running anyway is worse
+    # than pointless on a branch that has not been handed a .release-please-manifest.json yet —
+    # release-please fails the run outright when it cannot read one. A release commit always
+    # rewrites the manifest and the changelog, so this filter can never swallow one.
+    paths-ignore:
+      - '.github/workflows/**'
+  # Manual fallback only; nothing in the automated chain depends on dispatch.
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  # Required to update the merged release PR's autorelease labels after tagging.
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+      # Consumed by the publish job's checkout: without this mapping the checkout ref would be
+      # empty and the publish would build the triggering branch head instead of the released
+      # tag's exact commit.
+      tag_name: ${{ steps.release.outputs.tag_name }}
+    steps:
+      - uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7 # v5.0.0
+        id: release
+        with:
+          target-branch: main
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
+          # Release PRs are opened and updated by the Scalar platform with its own
+          # credential (so their CI runs without manual approval); this workflow only
+          # cuts the tag + GitHub Release once a release PR is merged.
+          skip-github-pull-request: true
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        if: ${{ steps.release.outputs.release_created == 'true' }}
+        with:
+          fetch-depth: 0
+      # Merging the release PR into main is itself the promotion, but the
+      # version bump and changelog must also land back on scalar-next, or the next
+      # release PR would propose this release again. A real merge (never a plain
+      # commit push) so a squash- or rebase-merged release PR syncs just as well; the
+      # non-conventional message keeps the sync commit out of future changelogs.
+      #
+      # The Scalar platform merges main into scalar-next itself when the release
+      # PR merges, so this step routinely races it. The sync is done once the release commit
+      # is an ancestor of scalar-next, whoever merged it, so that is checked before every
+      # attempt. A rejected push retries from a fresh fetch rather than failing the release
+      # run. Plain (non-force) push on purpose: a concurrent regeneration push is never
+      # discarded, and a sync that still cannot land after the retries fails loudly.
+      - name: Sync release back to scalar-next
+        if: ${{ steps.release.outputs.release_created == 'true' }}
+        env:
+          RELEASE_SHA: ${{ steps.release.outputs.sha }}
+          RELEASE_TAG: ${{ steps.release.outputs.tag_name }}
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          # Explicit `|| return 1`s because `set -e` does not apply inside a function called
+          # as a condition, and a failed merge must never fall through to a no-op push.
+          sync_release() {
+            git fetch origin scalar-next || return 1
+            if git merge-base --is-ancestor "$RELEASE_SHA" origin/scalar-next; then
+              echo "$RELEASE_TAG is already on scalar-next."
+              return 0
+            fi
+            git checkout -B scalar-next origin/scalar-next || return 1
+            if ! git merge --no-edit -m "Sync release $RELEASE_TAG back to scalar-next" "$RELEASE_SHA"; then
+              git merge --abort
+              return 1
+            fi
+            git push origin scalar-next
+          }
+          for attempt in 1 2 3; do
+            if sync_release; then exit 0; fi
+            echo "Attempt $attempt of 3 to sync $RELEASE_TAG back to scalar-next failed."
+            if [ "$attempt" -lt 3 ]; then sleep $((attempt * 5)); fi
+          done
+          echo "::error::Could not sync $RELEASE_TAG back to scalar-next after 3 attempts."
+          exit 1
+  publish:
+    needs: release-please
+    # `!cancelled()` keeps publishing even when the back-sync to the integration branch
+    # failed: a raced integration branch must not block the release from reaching its
+    # registry.
+    if: ${{ !cancelled() && needs.release-please.outputs.release_created == 'true' }}
+    runs-on: ubuntu-latest
+    # Job-level permissions replace the workflow's release-cutting grants with the publish
+    # floor. OIDC trusted publishing verifies this run's claims, which name this workflow
+    # file — register release-please.yml as the trusted publisher on the registry.
+    permissions:
+      contents: read
+      id-token: write
+      packages: write
+    env:
+      VERSIONING_POLICY: manual
+    steps:
+      # Publishing runs inline — a top-level job of this same run — rather than dispatching
+      # sdk-release.yml: workflow_dispatch resolves the target workflow on the repository's
+      # default branch only, so a dispatch would 404 whenever the release line is any other
+      # branch, while OIDC trusted publishing accepts this job because it stays top-level
+      # (never a reusable-workflow call). The release-please job cut the tag earlier in this
+      # run; checking it out publishes exactly the released commit, not the branch head that
+      # triggered the workflow.
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          ref: ${{ needs.release-please.outputs.tag_name }}
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.11"
+      - run: python -m pip install --upgrade build
+      - run: python -m build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          skip-existing: true

warp_hr-0.3.0/.github/workflows/release-title-edit.yml

@@ -0,0 +1,93 @@
+name: Release PR Version
+
+on:
+  # `edited` is not one of the default pull_request types, but it is the point of this
+  # workflow: retitling the release PR is how a maintainer picks an exact version, and the
+  # check has to re-run on the new title. The other types keep the consistency check attached
+  # to the PR as it evolves.
+  pull_request:
+    types: [opened, reopened, edited, synchronize]
+
+# Read-only: the check reads the committed version, and polls the pull request while it waits
+# for a re-render.
+permissions:
+  contents: read
+  pull-requests: read
+
+jobs:
+  version-consistency:
+    # Also the check name the release PR's footer tells maintainers to wait for.
+    name: Release PR version
+    # A release-shaped title against the release branch is the whole test here, with no clause
+    # on who opened the pull request or what branch it is rendered onto. This job only reads,
+    # and a pull request claiming to be a release is worth checking against the committed
+    # version whoever opened it. Every other pull request skips this job, which GitHub reports
+    # as neutral.
+    #
+    # Loose on purpose: the prefix, not the full semver pattern the script matches. A version
+    # typo'd into the title still reaches the script and fails there, rather than falling out
+    # of the guard and leaving no check at all — a missing check is not a failing one, and this
+    # is the check the release PR's footer tells maintainers to wait for before merging.
+    if: >-
+      ${{ github.event.pull_request.base.ref == 'main'
+      && startsWith(github.event.pull_request.title, 'release: ') }}
+    runs-on: ubuntu-latest
+    # Bounds the wait below with room to spare; a re-render normally lands within a minute.
+    timeout-minutes: 15
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+        with:
+          # The version committed on the PR head is what merging would actually release.
+          ref: ${{ github.event.pull_request.head.sha }}
+      # A retitle is applied by the Scalar platform, which pushes a Release-As commit to the
+      # integration branch and re-renders the release PR at that version. Until it lands, the
+      # title and the committed version disagree, and a merge in that window would tag a release
+      # whose own files self-report the old version.
+      #
+      # So this waits rather than failing: the check stays pending, which blocks a merge just as
+      # a failure would where the check is required, but does not flash red on every retitle. It
+      # passes once the title and the committed version agree, and hands over once the head
+      # moves, since the re-render's push starts a run of its own on the new head. It never
+      # passes while the title still disagrees, even a newer title: the run started for that
+      # edit judges it, and a pass here would sit beside it on the same head. Only a re-render
+      # that never arrives, or a title that is not a version at all, fails it.
+      - name: Compare the title version with the committed version
+        env:
+          # The title is human input, so it is bound through the environment (never
+          # interpolated into the script) and matched against a strict semver pattern
+          # before it is read.
+          PR_TITLE: ${{ github.event.pull_request.title }}
+          HEAD_SHA: ${{ github.event.pull_request.head.sha }}
+          PR_NUMBER: ${{ github.event.pull_request.number }}
+          REPOSITORY: ${{ github.repository }}
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          pattern='^release: ((0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-[0-9A-Za-z.-]+)?(\+[0-9A-Za-z.-]+)?)$'
+          if [[ ! "$PR_TITLE" =~ $pattern ]]; then
+            echo "::error::Release PR title must be \"release: X.Y.Z\" with a full semver version, got: $PR_TITLE"
+            exit 1
+          fi
+          title_version="${BASH_REMATCH[1]}"
+          manifest_version="$(jq -r '.["."]' .release-please-manifest.json)"
+          if [[ "$title_version" == "$manifest_version" ]]; then
+            echo "Release PR title and committed version agree on $title_version."
+            exit 0
+          fi
+          echo "Release PR title says $title_version but the pull request is versioned $manifest_version. Waiting for it to be re-rendered at $title_version."
+          # Up to ten minutes: 60 polls, 10 seconds apart.
+          for _ in $(seq 60); do
+            sleep 10
+            # A failed read is retried on the next poll rather than failing the check.
+            current="$(gh api "repos/$REPOSITORY/pulls/$PR_NUMBER" --jq '[.head.sha, .title] | @tsv')" || continue
+            IFS=$'\t' read -r current_sha current_title <<< "$current"
+            if [[ "$current_sha" != "$HEAD_SHA" ]]; then
+              echo "The release PR has a new head; the run for that push checks it."
+              exit 0
+            fi
+            if [[ "$current_title" =~ $pattern && "${BASH_REMATCH[1]}" == "$manifest_version" ]]; then
+              echo "Release PR title and committed version agree on $manifest_version."
+              exit 0
+            fi
+          done
+          echo "::error::Release PR title says $title_version but the pull request is still versioned $manifest_version after 10 minutes. Rebuild the SDK from the Scalar dashboard to re-render it."
+          exit 1

warp_hr-0.3.0/.github/workflows/sdk-ci.yml

@@ -0,0 +1,27 @@
+name: Python SDK CI
+
+on:
+  push:
+  pull_request:
+
+# Least privilege for a verification-only workflow: every job below only reads the checked-out
+# tree, so the run's GITHUB_TOKEN is narrowed to that regardless of the repository's default
+# grants. Declared at the workflow level so a job added later inherits the floor.
+permissions:
+  contents: read
+
+jobs:
+  verify:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.11"
+      - run: python -m pip install --upgrade build
+      - run: python -m build
+      # Verification only, never auto-fix: the SDK is generated formatted, so a diff here means
+      # either hand-edited custom code or a regenerate that was not committed. ruff is pinned to
+      # the release that produced these bytes, since a formatter minor can change them.
+      - run: python -m pip install "ruff==0.16.8"
+      - run: ruff format --check .

warp_hr-0.3.0/.github/workflows/sdk-release.yml

@@ -0,0 +1,34 @@
+name: Python SDK Release
+
+on:
+  # Manual re-publish only: the automated publish for each release runs as the `publish` job
+  # inside release-please.yml, in the same run that cuts the tag (dispatching a workflow here
+  # instead would resolve it on the repository's default branch only, which breaks releasing
+  # from any other release line). Dispatch this workflow at an existing release tag to re-run
+  # a failed or skipped publish. A dispatched run is top-level, so OIDC trusted-publisher
+  # claims name this file; register it as an additional trusted publisher only when manual
+  # re-publishes are used. Never add a workflow_call trigger here — registries reject
+  # publishes from called (reusable) workflows.
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  id-token: write
+  packages: write
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    env:
+      VERSIONING_POLICY: manual
+    steps:
+      - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+        with:
+          python-version: "3.11"
+      - run: python -m pip install --upgrade build
+      - run: python -m build
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # v1.14.2
+        with:
+          skip-existing: true

warp_hr-0.3.0/.gitignore

@@ -0,0 +1,10 @@
+# Generated by Scalar SDK Generator.
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+/dist/
+/build/
+.mypy_cache/
+.pytest_cache/
+.ruff_cache/

warp_hr-0.3.0/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "0.3.0"
+}

warp_hr-0.3.0/CHANGELOG.md

@@ -0,0 +1,117 @@
+# Changelog
+
+## [0.3.0](https://github.com/TeamWarp/warp-sdk-python/compare/v0.2.0...v0.3.0) (2026-10-31)
+
+
+### ⚠ BREAKING CHANGES
+
+* **api:** 82 breaking changes to the SDK surface.
+    - URL of environment `production` changed from `https://api.joinwarp.com` to `https://api.joinwarp.com/public`.
+    - query param `limit` on `departments.list` is now required.
+    - `401` error response of `departments.list` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `429` error response of `departments.list` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `401` error response of `departments.create` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `409` error response of `departments.create` changed from `DepartmentAlreadyExists` to `department_already_exists_encoded`.
+    - `429` error response of `departments.create` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `401` error response of `departments.update` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `departments.update` changed from `DepartmentNotFound` to `department_not_found_encoded`.
+    - `409` error response of `departments.update` changed from `DepartmentAlreadyExists` to `department_already_exists_encoded`.
+    - `429` error response of `departments.update` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - query param `limit` on `timeOff.listAssignments` is now required.
+    - `401` error response of `timeOff.listAssignments` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `429` error response of `timeOff.listAssignments` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - query param `limit` on `timeOff.listBalances` is now required.
+    - `401` error response of `timeOff.listBalances` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `timeOff.listBalances` changed from `TimeOffPolicyNotFound` to `time_off_policy_not_found_encoded`.
+    - `429` error response of `timeOff.listBalances` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - query param `limit` on `timeOff.listRequests` is now required.
+    - `401` error response of `timeOff.listRequests` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `timeOff.listRequests` changed from `TimeOffRequestNotFoundError` to `time_off_request_not_found_error_encoded`.
+    - `429` error response of `timeOff.listRequests` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - query param `limit` on `timeOff.policies.list` is now required.
+    - `401` error response of `timeOff.policies.list` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `timeOff.policies.list` changed from `TimeOffPolicyNotFound` to `time_off_policy_not_found_encoded`.
+    - `429` error response of `timeOff.policies.list` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `401` error response of `workers.delete` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `workers.delete` changed from `WorkerNotFoundError` to `worker_not_found_error_encoded`.
+    - `409` error response of `workers.delete` changed from `CannotDeleteWorker` to `cannot_delete_worker_encoded`.
+    - `429` error response of `workers.delete` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - query param `limit` on `workers.list` is now required.
+    - `401` error response of `workers.list` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `429` error response of `workers.list` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `400` error response of `workers.createEmployee` changed from `application/json` to `state_registration_required_encoded`.
+    - `401` error response of `workers.createEmployee` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `429` error response of `workers.createEmployee` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `401` error response of `workers.createContractor` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `429` error response of `workers.createContractor` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `401` error response of `workers.invite` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `workers.invite` changed from `WorkerNotFoundError` to `worker_not_found_error_encoded`.
+    - `429` error response of `workers.invite` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - query param `limit` on `workplaces.list` is now required.
+    - `401` error response of `workplaces.list` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `429` error response of `workplaces.list` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `400` error response of `workplaces.create` changed from `application/json` to `address_invalid_encoded`.
+    - `401` error response of `workplaces.create` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `409` error response of `workplaces.create` changed from `WorkplaceAlreadyExists` to `workplace_already_exists_encoded`.
+    - `429` error response of `workplaces.create` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - `401` error response of `workplaces.update` changed from `ApiKeyUnauthorized` to `api_key_unauthorized_encoded`.
+    - `404` error response of `workplaces.update` changed from `WorkplaceNotFound` to `workplace_not_found_encoded`.
+    - `409` error response of `workplaces.update` changed from `WorkplaceAlreadyExists` to `workplace_already_exists_encoded`.
+    - `429` error response of `workplaces.update` changed from `RateLimitExceeded` to `rate_limit_exceeded_encoded`.
+    - Removed operation `timeOff.policies.retrieve` (`GET /v1/time_off/policies/{id}`).
+    - Removed operation `workers.retrieve` (`GET /v1/workers/{id}`).
+    - Removed schema `Date`.
+    - Removed schema `HttpApiDecodeError`.
+    - Removed schema `Issue`.
+    - Removed schema `PropertyKey`.
+    - Removed schema `InternalServerError`.
+    - Removed schema `ApiKeyUnauthorized`.
+    - Removed schema `RateLimitExceeded`.
+    - Removed schema `DateTimeUtc`.
+    - Removed schema `MissingRequiredCompanyPermissions`.
+    - Removed schema `ApiNotEnabled`.
+    - Removed schema `Trimmed`.
+    - Removed schema `DepartmentAlreadyExists`.
+    - Removed schema `DepartmentNotFound`.
+    - Removed schema `ManagerNotFoundError`.
+    - Removed schema `TimeOffPolicyNotFound`.
+    - Removed schema `TimeOffRequestNotFoundError`.
+    - Removed schema `WorkerNotFoundError`.
+    - Removed schema `OfficeWorkLocation`.
+    - Removed schema `RemoteWorkLocation`.
+    - Removed schema `StateRegistrationRequired`.
+    - Removed schema `WorkplaceNotFound`.
+    - Removed schema `PayScheduleNotConfigured`.
+    - Removed schema `SubscriptionLimitError`.
+    - Removed schema `InvalidWorkerStatusError`.
+    - Removed schema `WorkerAlreadyExistsError`.
+    - Removed schema `CannotDeleteWorker`.
+    - Removed schema `AddressInvalid`.
+    - Removed schema `WorkplaceAlreadyExists`.
+
+### Features
+
+* **api:** update environment production (+369 more changes) ([c63939f](https://github.com/TeamWarp/warp-sdk-python/commit/c63939f401df44fb74c2b492a3b45cc5c0b5ffcc))
+
+
+### Chores
+
+* **api:** update generated SDK content ([92d1432](https://github.com/TeamWarp/warp-sdk-python/commit/92d14323f0771d7d328dc80e559cc51124cb69d1))
+
+## [0.2.0](https://github.com/TeamWarp/warp-sdk-python/compare/v0.1.0...v0.2.0) (2026-07-21)
+
+
+### ⚠ BREAKING CHANGES
+
+* **api:** Property `MissingRequiredCompanyPermissions.requiredPermissions` type changed from `Array<object>` to `Array<object>`.
+
+### Features
+
+* **api:** initial SDK generation ([8e80652](https://github.com/TeamWarp/warp-sdk-python/commit/8e80652dbfd19bba60028ac25508c60f6c3b9a2c))
+* **api:** update SDK surface (2 changes) ([56a6df4](https://github.com/TeamWarp/warp-sdk-python/commit/56a6df4ac79da2f80635c2922e1bf6ffa1df4695))
+
+
+### Chores
+
+* **api:** regenerate SDK ([a5cd83d](https://github.com/TeamWarp/warp-sdk-python/commit/a5cd83dc52e0caed22292ea3555a39f88e1887ce))
+* initialize SDK repository ([525c5a0](https://github.com/TeamWarp/warp-sdk-python/commit/525c5a0fb87ef6ecce6e7421814b58e51688104d))