Skip to content

Conversation

@workos-sdk-automation
Copy link
Contributor

Summary

  • Replace manual version-bump.yml and release.yml workflows with release-please
  • release-please automatically creates release PRs with version bumps and changelogs based on conventional commits
  • When a release PR is merged, the workflow publishes the package to Hex
  • Uses the SDK bot app token for authentication (same SDK_BOT_APP_ID / SDK_BOT_PRIVATE_KEY secrets)

Changes

  • Added .github/workflows/release-please.yml - Combined workflow that runs release-please and publishes to Hex on release
  • Added release-please-config.json - Configuration using the elixir release type
  • Added .release-please-manifest.json - Tracks current version (1.1.4)
  • Removed .github/workflows/version-bump.yml - Replaced by release-please
  • Removed .github/workflows/release.yml - Replaced by release-please

Test plan

  • Verify release-please action runs on push to main
  • Verify release PR is created with correct version bump and changelog
  • Verify Hex publish job triggers when release PR is merged

🤖 Generated with Claude Code

Replace the manual version-bump and release workflows with
release-please, which automatically creates release PRs with
version bumps and changelogs based on conventional commits.
When a release PR is merged, it publishes to Hex.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@greptile-apps
Copy link

greptile-apps bot commented Feb 9, 2026

Greptile Overview

Greptile Summary

This PR replaces the manual version bump and release workflows with release-please automation. The new workflow automatically creates release PRs based on conventional commits and publishes to Hex when merged.

Key changes:

  • Automated version bumping and changelog generation via release-please
  • Single workflow handles both release PR creation and Hex publishing
  • Maintains same authentication pattern (SDK bot app token)
  • Eliminates manual workflow_dispatch for version bumps
  • Uses proper job dependencies and output passing between jobs

The implementation correctly uses GitHub App token generation, appropriate permissions scoping, and the elixir release type for release-please.

Confidence Score: 5/5

  • This PR is safe to merge - it's a clean migration to standard release automation
  • The changes are well-structured and follow GitHub Actions best practices. The workflow correctly uses job dependencies, output passing, and conditional execution. Authentication uses the same secure pattern as existing workflows. The configuration files are minimal and properly formatted.
  • No files require special attention

Important Files Changed

Filename Overview
.github/workflows/release-please.yml Added new workflow combining release-please automation and Hex publishing with proper permissions and token handling
release-please-config.json Added release-please configuration using elixir release type with pre-major versioning settings
.release-please-manifest.json Added manifest tracking current version (1.1.4) for release-please state management

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Main as main branch
    participant RP as release-please action
    participant GH as GitHub
    participant Hex as Hex.pm

    Dev->>Main: Push commits with conventional commit messages
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>RP: Analyze commits since last release
    RP->>GH: Create/update release PR with version bump & changelog
    
    Note over Dev,GH: Release PR is reviewed and merged
    
    Dev->>Main: Merge release PR
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>GH: Create GitHub release with tag
    RP->>RP: Set release_created=true output
    
    Note over RP,Hex: Publish job starts (if release created)
    
    RP->>GH: Checkout code
    RP->>RP: Setup Elixir & Erlang (1.15, OTP 26.0)
    RP->>RP: Install dependencies (mix deps.get)
    RP->>Hex: Publish package (mix hex.publish --yes)
    Hex-->>RP: Publish success
Loading

3 similar comments
@greptile-apps
Copy link

greptile-apps bot commented Feb 9, 2026

Greptile Overview

Greptile Summary

This PR replaces the manual version bump and release workflows with release-please automation. The new workflow automatically creates release PRs based on conventional commits and publishes to Hex when merged.

Key changes:

  • Automated version bumping and changelog generation via release-please
  • Single workflow handles both release PR creation and Hex publishing
  • Maintains same authentication pattern (SDK bot app token)
  • Eliminates manual workflow_dispatch for version bumps
  • Uses proper job dependencies and output passing between jobs

The implementation correctly uses GitHub App token generation, appropriate permissions scoping, and the elixir release type for release-please.

Confidence Score: 5/5

  • This PR is safe to merge - it's a clean migration to standard release automation
  • The changes are well-structured and follow GitHub Actions best practices. The workflow correctly uses job dependencies, output passing, and conditional execution. Authentication uses the same secure pattern as existing workflows. The configuration files are minimal and properly formatted.
  • No files require special attention

Important Files Changed

Filename Overview
.github/workflows/release-please.yml Added new workflow combining release-please automation and Hex publishing with proper permissions and token handling
release-please-config.json Added release-please configuration using elixir release type with pre-major versioning settings
.release-please-manifest.json Added manifest tracking current version (1.1.4) for release-please state management

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Main as main branch
    participant RP as release-please action
    participant GH as GitHub
    participant Hex as Hex.pm

    Dev->>Main: Push commits with conventional commit messages
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>RP: Analyze commits since last release
    RP->>GH: Create/update release PR with version bump & changelog
    
    Note over Dev,GH: Release PR is reviewed and merged
    
    Dev->>Main: Merge release PR
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>GH: Create GitHub release with tag
    RP->>RP: Set release_created=true output
    
    Note over RP,Hex: Publish job starts (if release created)
    
    RP->>GH: Checkout code
    RP->>RP: Setup Elixir & Erlang (1.15, OTP 26.0)
    RP->>RP: Install dependencies (mix deps.get)
    RP->>Hex: Publish package (mix hex.publish --yes)
    Hex-->>RP: Publish success
Loading

@greptile-apps
Copy link

greptile-apps bot commented Feb 9, 2026

Greptile Overview

Greptile Summary

This PR replaces the manual version bump and release workflows with release-please automation. The new workflow automatically creates release PRs based on conventional commits and publishes to Hex when merged.

Key changes:

  • Automated version bumping and changelog generation via release-please
  • Single workflow handles both release PR creation and Hex publishing
  • Maintains same authentication pattern (SDK bot app token)
  • Eliminates manual workflow_dispatch for version bumps
  • Uses proper job dependencies and output passing between jobs

The implementation correctly uses GitHub App token generation, appropriate permissions scoping, and the elixir release type for release-please.

Confidence Score: 5/5

  • This PR is safe to merge - it's a clean migration to standard release automation
  • The changes are well-structured and follow GitHub Actions best practices. The workflow correctly uses job dependencies, output passing, and conditional execution. Authentication uses the same secure pattern as existing workflows. The configuration files are minimal and properly formatted.
  • No files require special attention

Important Files Changed

Filename Overview
.github/workflows/release-please.yml Added new workflow combining release-please automation and Hex publishing with proper permissions and token handling
release-please-config.json Added release-please configuration using elixir release type with pre-major versioning settings
.release-please-manifest.json Added manifest tracking current version (1.1.4) for release-please state management

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Main as main branch
    participant RP as release-please action
    participant GH as GitHub
    participant Hex as Hex.pm

    Dev->>Main: Push commits with conventional commit messages
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>RP: Analyze commits since last release
    RP->>GH: Create/update release PR with version bump & changelog
    
    Note over Dev,GH: Release PR is reviewed and merged
    
    Dev->>Main: Merge release PR
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>GH: Create GitHub release with tag
    RP->>RP: Set release_created=true output
    
    Note over RP,Hex: Publish job starts (if release created)
    
    RP->>GH: Checkout code
    RP->>RP: Setup Elixir & Erlang (1.15, OTP 26.0)
    RP->>RP: Install dependencies (mix deps.get)
    RP->>Hex: Publish package (mix hex.publish --yes)
    Hex-->>RP: Publish success
Loading

@greptile-apps
Copy link

greptile-apps bot commented Feb 9, 2026

Greptile Overview

Greptile Summary

This PR replaces the manual version bump and release workflows with release-please automation. The new workflow automatically creates release PRs based on conventional commits and publishes to Hex when merged.

Key changes:

  • Automated version bumping and changelog generation via release-please
  • Single workflow handles both release PR creation and Hex publishing
  • Maintains same authentication pattern (SDK bot app token)
  • Eliminates manual workflow_dispatch for version bumps
  • Uses proper job dependencies and output passing between jobs

The implementation correctly uses GitHub App token generation, appropriate permissions scoping, and the elixir release type for release-please.

Confidence Score: 5/5

  • This PR is safe to merge - it's a clean migration to standard release automation
  • The changes are well-structured and follow GitHub Actions best practices. The workflow correctly uses job dependencies, output passing, and conditional execution. Authentication uses the same secure pattern as existing workflows. The configuration files are minimal and properly formatted.
  • No files require special attention

Important Files Changed

Filename Overview
.github/workflows/release-please.yml Added new workflow combining release-please automation and Hex publishing with proper permissions and token handling
release-please-config.json Added release-please configuration using elixir release type with pre-major versioning settings
.release-please-manifest.json Added manifest tracking current version (1.1.4) for release-please state management

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Main as main branch
    participant RP as release-please action
    participant GH as GitHub
    participant Hex as Hex.pm

    Dev->>Main: Push commits with conventional commit messages
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>RP: Analyze commits since last release
    RP->>GH: Create/update release PR with version bump & changelog
    
    Note over Dev,GH: Release PR is reviewed and merged
    
    Dev->>Main: Merge release PR
    Main->>RP: Trigger release-please workflow
    RP->>GH: Generate app token (SDK_BOT)
    GH-->>RP: Return token
    RP->>GH: Create GitHub release with tag
    RP->>RP: Set release_created=true output
    
    Note over RP,Hex: Publish job starts (if release created)
    
    RP->>GH: Checkout code
    RP->>RP: Setup Elixir & Erlang (1.15, OTP 26.0)
    RP->>RP: Install dependencies (mix deps.get)
    RP->>Hex: Publish package (mix hex.publish --yes)
    Hex-->>RP: Publish success
Loading

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

3 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

@gjtorikian gjtorikian merged commit 482d690 into main Feb 9, 2026
4 checks passed
@gjtorikian gjtorikian deleted the add-release-please branch February 9, 2026 17:13
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