Skip to content

chore(main): release 10.9.0 - #773

Merged
gjtorikian merged 3 commits into
mainfrom
release-please--branches--main
Nov 13, 2026
Merged

gjtorikian merged 3 commits into
mainfrom
release-please--branches--main

Conversation

@workos-sdk-automation

@workos-sdk-automation workos-sdk-automation Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

10.9.0 (2026-11-13)

Features

  • actions: Add verify_action returning a typed action context (#776) (043aa34)
  • pipes: Update Pipes API surface (#777) (2cb5d5e)
  • sso: Update SSO API surface (#778) (ef3fa56)

Bug Fixes

  • sdk: webhooks-django × codex-baseline — The agent hand-rolled HMAC signature verification (parsing a… (#736) (6e6d782)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Low impact] The release appears safe to merge, with non-blocking corrections needed in the release notes.

Findings

  1. P2 Directory upgrade notes are wrong ▶
  2. P2 Release note hides the change ▶
Fix with agent prompt
### Issue 1
CHANGELOG.md:18-21
These notes say `Directories.find` loses `id` and changes its return type. The Python API still exposes `get_directory(id) -> Directory`; the group lookup is a separate `get_directory_group(directory_id, group_id)` method. This tells users to prepare for a breaking change that does not affect their existing directory lookup.

Replace these claims, including the return-type claim below, with the actual Python additions and deprecations.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

### Issue 2
CHANGELOG.md:10-12
The new entry describes an agent hand-rolling HMAC verification and ends mid-sentence. The referenced commit only adds README guidance for existing webhook methods; it does not change verification behavior. Users checking whether to upgrade cannot tell what this release changes.

Replace the text with “Document webhook signature verification with Django” and place it under Documentation.

```suggestion
### Documentation

* Document webhook signature verification with Django ([#736](https://github.com/workos/workos-python/issues/736)) ([6e6d782](https://github.com/workos/workos-python/commit/6e6d782b0efb41fd21033b121ca6480c23da1f68))
```

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Prepares the 10.9.0 release.

  • The Python package release records now identify version 10.9.0.

Reviews (6) · Last reviewed commit: "chore: inline release notes from .change..." · Reviewed by Greptile

Comment thread CHANGELOG.md
Comment on lines +6 to +8
### Bug Fixes

* **sdk:** webhooks-django × codex-baseline — The agent hand-rolled HMAC signature verification (parsing a… ([#736](https://github.com/workos/workos-python/issues/736)) ([6e6d782](https://github.com/workos/workos-python/commit/6e6d782b0efb41fd21033b121ca6480c23da1f68))

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Release note hides the change

The new entry describes an agent hand-rolling HMAC verification and ends mid-sentence. The referenced commit only adds README guidance for existing webhook methods; it does not change verification behavior. Users checking whether to upgrade cannot tell what this release changes.

Replace the text with “Document webhook signature verification with Django” and place it under Documentation.

Suggested change
### Bug Fixes
* **sdk:** webhooks-django × codex-baseline — The agent hand-rolled HMAC signature verification (parsing a… ([#736](https://github.com/workos/workos-python/issues/736)) ([6e6d782](https://github.com/workos/workos-python/commit/6e6d782b0efb41fd21033b121ca6480c23da1f68))
### Documentation
* Document webhook signature verification with Django ([#736](https://github.com/workos/workos-python/issues/736)) ([6e6d782](https://github.com/workos/workos-python/commit/6e6d782b0efb41fd21033b121ca6480c23da1f68))
Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 6-8

Comment:
**Release note hides the change**

The new entry describes an agent hand-rolling HMAC verification and ends mid-sentence. The referenced commit only adds README guidance for existing webhook methods; it does not change verification behavior. Users checking whether to upgrade cannot tell what this release changes.

Replace the text with “Document webhook signature verification with Django” and place it under Documentation.

```suggestion
### Documentation

* Document webhook signature verification with Django ([#736](https://github.com/workos/workos-python/issues/736)) ([6e6d782](https://github.com/workos/workos-python/commit/6e6d782b0efb41fd21033b121ca6480c23da1f68))
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@workos-sdk-automation
workos-sdk-automation Bot force-pushed the release-please--branches--main branch from 4b9f211 to 10983d3 Compare November 10, 2026 17:55
@workos-sdk-automation workos-sdk-automation Bot changed the title chore(main): release 10.8.1 chore(main): release 10.9.0 Nov 11, 2026
@workos-sdk-automation
workos-sdk-automation Bot force-pushed the release-please--branches--main branch 2 times, most recently from 187d68c to ed9ad6c Compare November 13, 2026 20:23
@workos-sdk-automation
workos-sdk-automation Bot force-pushed the release-please--branches--main branch from 3281085 to ebf6b21 Compare November 13, 2026 20:41
Comment thread CHANGELOG.md
Comment on lines +18 to +21
* Added parameter `Directories.find.directoryId`
* Added parameter `Directories.find.groupId`
* Removed parameter `Directories.find.id`
* Changed path for endpoint `GET /directories/{directoryId}/groups/{groupId}`

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Directory upgrade notes are wrong

These notes say Directories.find loses id and changes its return type. The Python API still exposes get_directory(id) -> Directory; the group lookup is a separate get_directory_group(directory_id, group_id) method. This tells users to prepare for a breaking change that does not affect their existing directory lookup.

Replace these claims, including the return-type claim below, with the actual Python additions and deprecations.

Prompt To Fix With AI
This is a comment left during a code review.
Path: CHANGELOG.md
Line: 18-21

Comment:
**Directory upgrade notes are wrong**

These notes say `Directories.find` loses `id` and changes its return type. The Python API still exposes `get_directory(id) -> Directory`; the group lookup is a separate `get_directory_group(directory_id, group_id)` method. This tells users to prepare for a breaking change that does not affect their existing directory lookup.

Replace these claims, including the return-type claim below, with the actual Python additions and deprecations.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

@gjtorikian
gjtorikian merged commit fdb7024 into main Nov 13, 2026
16 of 17 checks passed
@gjtorikian
gjtorikian deleted the release-please--branches--main branch November 13, 2026 20:46
@workos-sdk-automation

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

1 participant