Bump version to v5.38.0

[birdcar]

Description

Releases #507 to add support for WorkOS Pipes

Documentation

Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.

[ ] Yes

If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR bumps the package version from 5.37.0 to 5.38.0, preparing for a minor release that includes:

• WorkOS Pipes support (Add Python SDK support for WorkOS Pipes #507): New SDK functionality for retrieving access tokens from third-party providers via the Pipes API
• Vault API enhancement (Add read_object_by_name method for Vault API #506): Addition of read_object_by_name method for accessing vault objects by name
• Internal updates (Add context7.json to repo #504): Addition of context7.json configuration file

Version Bump Analysis

The version increment follows semantic versioning correctly:

• Previous: 5.37.0
• New: 5.38.0
• Type: Minor version bump (appropriate for new features with backward compatibility)

Technical Implementation

The version is defined in workos/__about__.py and automatically consumed by:

• setup.py - reads version via exec() to populate package metadata
• GitHub Actions release workflow - triggers on release publish, runs tests, and uploads to PyPI
• Build script - scripts/build_and_upload_dist.sh for manual releases

Verification

✅ Version format is valid (X.Y.Z semantic versioning)
✅ No hardcoded version references found elsewhere in codebase
✅ Tests use dynamic version or "test" placeholder
✅ No files requiring updates beyond __about__.py
✅ Version increment aligns with feature additions (minor release)

Note on PR Description

The PR description mentions only #507 (Pipes support) but the release includes additional features from #506 and #504. While the version bump itself is correct, the description could be more comprehensive to reflect all changes being released.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk - it's a straightforward version bump following established patterns
• The version bump is implemented correctly with proper semantic versioning (minor version increment for new features). The change is minimal, isolated to a single file, and follows the exact pattern used in previous releases. The version is automatically consumed by setup.py and release automation, requiring no additional manual updates. All custom security rules are inapplicable to this change. The only minor issue is that the PR description could be more comprehensive in listing all features being released (includes Add read_object_by_name method for Vault API #506 and Add context7.json to repo #504 in addition to the mentioned Add Python SDK support for WorkOS Pipes #507), but this is a documentation preference rather than a code issue.
• No files require special attention - the single changed file is a straightforward version string update

Important Files Changed

File Analysis

Filename	Score	Overview
workos/about.py	5/5	Version bumped from 5.37.0 to 5.38.0 following semantic versioning for minor release with new features

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PR as PR #509
    participant Version as __about__.py
    participant Setup as setup.py
    participant CI as GitHub Actions
    participant PyPI as Python Package Index
    
    Dev->>PR: Create version bump PR
    PR->>Version: Update __version__ = "5.38.0"
    Note over Version: Increments from 5.37.0<br/>to 5.38.0 (minor version)
    
    Dev->>PR: Merge to main
    PR->>CI: Trigger release workflow
    
    CI->>Setup: Read version
    Setup->>Version: Import __version__
    Version-->>Setup: Return "5.38.0"
    Setup-->>CI: Return version metadata
    
    CI->>CI: Run tests
    CI->>CI: Build sdist & wheel
    CI->>PyPI: Upload v5.38.0 package
    
    Note over PyPI: workos-python v5.38.0<br/>now available with:<br/>- Pipes support (#507)<br/>- Vault API method (#506)<br/>- Other improvements

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

The PR description states this "Releases #507 to add support for WorkOS Pipes", but v5.38.0 actually includes three feature additions merged since v5.37.0:

1. Add Python SDK support for WorkOS Pipes #507 - WorkOS Pipes support (mentioned in description)
2. Add read_object_by_name method for Vault API #506 - New Vault API read_object_by_name method (not mentioned)
3. Add context7.json to repo #504 - context7.json addition (not mentioned)

Consider updating the PR description to accurately reflect all changes being released, especially #506 which adds a new public API method. This helps users understand the full scope of the release when reviewing release notes or changelogs.

The version bump itself is correct - incrementing the minor version (5.37.0 → 5.38.0) is appropriate for these backward-compatible feature additions per semantic versioning.

_{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!}

Prompt To Fix With AI

This is a comment left during a code review.
Path: workos/__about__.py
Line: 15:15

Comment:
The PR description states this "Releases #507 to add support for WorkOS Pipes", but v5.38.0 actually includes three feature additions merged since v5.37.0:

1. **#507** - WorkOS Pipes support (mentioned in description)
2. **#506** - New Vault API `read_object_by_name` method (not mentioned)
3. **#504** - context7.json addition (not mentioned)

Consider updating the PR description to accurately reflect all changes being released, especially #506 which adds a new public API method. This helps users understand the full scope of the release when reviewing release notes or changelogs.

The version bump itself is correct - incrementing the minor version (5.37.0 → 5.38.0) is appropriate for these backward-compatible feature additions per semantic versioning.

<sub>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!</sub>

How can I resolve this? If you propose a fix, please make it concise.