Skip to content

chore: release 0.2.0 - #3

Merged
Vincent (vincent-ycw) merged 1 commit into
mainfrom
release-candidate
Oct 1, 2026
Merged

Vincent (vincent-ycw) merged 1 commit into
mainfrom
release-candidate

Conversation

@photon-action-bot

@photon-action-bot photon-action-bot Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

0.2.0 (2026-10-01)

⚠ BREAKING CHANGES

  • Upgrading from 0.1.x:
    • Type names now come from the API contract. Names that 0.1.x derived from operations are gone, for example AssignSmsLineCampaignResponse200ApplicationJson is now AssignSmsLineCampaignResponse. Update imports of renamed types. Methods, requests and responses on the wire keep their names.
    • Account deletion and account service keys no longer accept OAuth tokens with account:write; use an account service key.
    • The SMS line campaign response drops campaignObservedAt, observedAt, operationId, providerAssignmentStatus and requestedCampaignId.

Features

  • Add auth.disableOrganizationSso (POST /v1/auth/organizations/{orgId}/sso/disable).

Bug Fixes

  • Python: the attachment upload body is typed as bytes.
  • The Sunset response header is documented as an HTTP date.

Documentation

  • postman: add the Run in Postman button and the public workspace link

Files

These files were built from the head of this pull request, passed the production smoke test and are published unchanged to npm, PyPI and crates.io.

0234e501c7f187ccd43fb0089cf449d5434dff60d35579392e41f0c1057490ab  photon-ai-api-0.2.0.tgz
0dd5385ba78314d62712a35b7d1ccbbbfde04940ccc1bdf79fb2ffe7211e25d0  photonhq_api-0.2.0-py3-none-any.whl
5018963ae0281a26640f45f1da4b4d67b75744e25868d8e7875e1763d439acd1  photonhq_api-0.2.0.tar.gz
d726b2bc52920fcc959c83472f0d0c4ace84dd4a77c6090d0d3120b62757066f  photonhq-api-0.2.0.crate

Important

Merge this pull request with Create a merge commit only. Squash and rebase merges replace the tested commit, and the release is then refused. Do not push changes to this pull request; they are refused too. Merging publishes the release: the tag and the GitHub release follow automatically, and npm, PyPI and crates.io receive exactly the files listed above.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Public contract SHA-256: 7a951ba8d4d6bf9cd13ea582bb27952081b2a3241c8e56dd53a177079ed59510

Contract change: feat!
- DELETE /v1/account: the endpoint scheme security `oauth2: [account:write]` was removed from the API
- DELETE /v1/account: added `#/components/schemas/ForbiddenProblem, #/components/schemas/InsufficientScopeProblem, #/components/schemas/OrganizationSsoRequiredProblem, #/components/schemas/ResourceMismatchProblem` to the response body `oneOf` list for the response status `403`
- DELETE /v1/account: added `#/components/schemas/InternalErrorProblem, #/components/schemas/InvalidAuthContextProblem` to the response body `oneOf` list for the response status `500`
- DELETE /v1/account: added `#/components/schemas/UpstreamTimeoutProblem, #/components/schemas/RequestTimeoutProblem` to the response body `oneOf` list for the response status `504`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `200`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `403`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `404`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `409`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `500`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `502`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `503`
- DELETE /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `504`
- DELETE /v1/account: the `status` response's property `type` was widened from `integer` to `number` for status `401`
- GET /v1/account: added `#/components/schemas/ForbiddenProblem, #/components/schemas/InsufficientScopeProblem, #/components/schemas/OrganizationSsoRequiredProblem, #/components/schemas/ResourceMismatchProblem` to the response body `oneOf` list for the response status `403`
- GET /v1/account: added `#/components/schemas/InternalErrorProblem, #/components/schemas/InvalidAuthContextProblem` to the response body `oneOf` list for the response status `500`
- GET /v1/account: added `#/components/schemas/UpstreamTimeoutProblem, #/components/schemas/RequestTimeoutProblem` to the response body `oneOf` list for the response status `504`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `200`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `403`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `404`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `410`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `500`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `502`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `503`
- GET /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `504`
- GET /v1/account: the `status` response's property `type` was widened from `integer` to `number` for status `401`
- PATCH /v1/account: added `#/components/schemas/ForbiddenProblem, #/components/schemas/InsufficientScopeProblem, #/components/schemas/OrganizationSsoRequiredProblem, #/components/schemas/ResourceMismatchProblem` to the response body `oneOf` list for the response status `403`
- PATCH /v1/account: added `#/components/schemas/HttpErrorProblem, #/components/schemas/InvalidArgumentProblem, #/components/schemas/IdempotencyKeyInvalidProblem, #/components/schemas/IdempotencyKeyRequiredProblem` to the response body `oneOf` list for the response status `400`
- PATCH /v1/account: added `#/components/schemas/IdempotencyKeyReusedProblem, #/components/schemas/ValidationFailedProblem` to the response body `oneOf` list for the response status `422`
- PATCH /v1/account: added `#/components/schemas/InternalErrorProblem, #/components/schemas/InvalidAuthContextProblem` to the response body `oneOf` list for the response status `500`
- PATCH /v1/account: added `#/components/schemas/UpstreamTimeoutProblem, #/components/schemas/RequestTimeoutProblem` to the response body `oneOf` list for the response status `504`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `200`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `400`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `403`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `404`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `410`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `413`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `422`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `500`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `502`
- PATCH /v1/account: the `sunset` response header's `format` changed from `date-time` to `none` for the status `503`
- and 2414 more
@coderabbitai

coderabbitai Bot commented Oct 1, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 02271253-48f4-42dd-880b-5891b8ae4a67

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.


Comment @coderabbitai help to get the list of available commands.

@vincent-ycw
Vincent (vincent-ycw) merged commit 1a97667 into main Oct 1, 2026
19 checks passed

This branch was successfully deployed

3 active deployments
npm — 80e137ff Deployed Oct 1, 2026 by photon-action-bot[bot] via npm #3
pypi — 80e137ff Deployed Oct 1, 2026 by photon-action-bot[bot] via pypi #3
crates-io — 80e137ff Deployed Oct 1, 2026 by photon-action-bot[bot] via crates-io #3
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