Skip to content

chore(main): release 10.5.0 - #735

Merged
csrbarber merged 3 commits into
mainfrom
release-please--branches--main
Sep 24, 2026
Merged

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

Conversation

@workos-sdk-automation

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

10.5.0 (2026-09-24)

Features

  • generated: Authorization (batch c64ce1e7) (#734) (0037bc3)

This PR was generated with Release Please. See documentation.

@greptile-apps

greptile-apps Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerConfidence Score: 4/5

The PR appears safe to merge, though the release note should direct readers to Authorization.

Findings

  1. P2 Wrong feature category ▶
Fix with agent prompt
### Issue 1
CHANGELOG.md:8
The 10.5.0 notes list the new role-assignment group model and field under User Management, but both belong to `workos.authorization.models`. Readers following this category and its link will look in the wrong API area. Please categorize the entry under Authorization and link the relevant documentation.

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

The PR prepares the 10.5.0 release by synchronizing version metadata and moving the pending feature note into the changelog.

  • The release note’s product category points readers to User Management instead of Authorization.

Reviews (1) · Last reviewed commit: "chore: inline release notes from .change..."

Comment thread CHANGELOG.md
* [#734](https://github.com/workos/workos-python/pull/734) feat(generated): regenerate from spec

**Features**
* **[user_management](https://workos.com/docs/reference/authkit/user)**:

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 Wrong feature category The 10.5.0 notes list the new role-assignment group model and field under User Management, but both belong to workos.authorization.models. Readers following this category and its link will look in the wrong API area. Please categorize the entry under Authorization and link the relevant documentation.

Knowledge Base Used: SSO and authorization

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

Comment:
**Wrong feature category** The 10.5.0 notes list the new role-assignment group model and field under User Management, but both belong to `workos.authorization.models`. Readers following this category and its link will look in the wrong API area. Please categorize the entry under Authorization and link the relevant documentation.

**Knowledge Base Used:** [SSO and authorization](https://app.greptile.com/workos/-/custom-context/knowledge-base/workos/workos-python/-/docs/sso-and-authorization.md)

---

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!

@csrbarber
csrbarber merged commit 83af6f5 into main Sep 24, 2026
15 checks passed
@csrbarber
csrbarber deleted the release-please--branches--main branch September 24, 2026 14:23
@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