ci: add release-please and conventional commit enforcement

[nicknisi]

Summary

• Derive SDK version from package.json instead of a hardcoded VERSION constant in src/workos.ts. This is required so release-please can bump the version in a single place (package.json) and have it propagate to the User-Agent header automatically.
• Add release-please configuration (release-please-config.json, .release-please-manifest.json, .github/workflows/release-please.yml) to automate version bumps, changelog generation, and GitHub Release creation via conventional commits.
• Add PR title linting (.github/workflows/lint-pr-title.yml) to enforce conventional commit format on PR titles. Since PRs are squash-merged, the PR title becomes the commit message that release-please parses. This check runs on all PRs after this one merges. Consider adding it as a required status check in branch protection for main.
• Replace ts-jest with the existing babel-jest transformer in jest.config.cjs. The import ... with { type: 'json' } syntax used for the package.json import is incompatible with ts-jest (which overrides module to "commonjs"). The project's existing jest-transform-esm.cjs (babel-jest + @babel/preset-typescript) handles this correctly. ts-jest is removed from devDependencies as it is no longer used anywhere.

How it works

1. Conventional commits (feat:, fix:, chore:, etc.) are enforced on PR titles via amannn/action-semantic-pull-request
2. PRs are squash-merged, so the PR title becomes the commit message on main
3. release-please-action opens (or updates) a release PR with a version bump and CHANGELOG.md entry
4. Merging the release PR creates a GitHub Release
5. The existing release.yml workflow triggers on the release: [published] event and publishes to npm

No changes to the existing publish workflow are needed — it already triggers on GitHub Release events.

Files changed

File	Change
src/workos.ts	Import VERSION from package.json instead of hardcoding
jest.config.cjs	Unified transform to jest-transform-esm.cjs for both .ts and .js
package.json	Removed ts-jest from devDependencies
package-lock.json	Removed ts-jest and its dependency tree
release-please-config.json	Release-please config (node type, bump-minor-pre-major)
.release-please-manifest.json	Version manifest seeded at 8.2.0
.github/workflows/release-please.yml	Workflow to run release-please on push to main
.github/workflows/lint-pr-title.yml	Enforce conventional commit format on PR titles

[greptile-apps]

Greptile Overview

Greptile Summary

Automated release management by integrating release-please to handle version bumps, changelog generation, and GitHub releases based on conventional commits.

Key Changes:

• Derived SDK version from package.json instead of hardcoded constant in src/workos.ts using import attributes syntax (with { type: 'json' })
• Unified Jest transformer to use jest-transform-esm.cjs (babel-jest) for both TypeScript and JavaScript files, removing ts-jest dependency
• Added release-please configuration files and GitHub workflow to automate release process
• Removed ts-jest from dependencies as it's incompatible with the import attributes syntax

Release Flow:

1. Conventional commits (feat:, fix:, etc.) trigger release-please to create/update a release PR
2. Merging the release PR creates a GitHub Release
3. Existing release.yml workflow publishes to npm on release events

The version in User-Agent headers will automatically reflect the current package version without manual updates.

Confidence Score: 5/5

• Safe to merge - well-structured automation changes with no breaking modifications to core logic
• All changes are infrastructure/tooling improvements with no impact on runtime behavior. The version derivation change is straightforward, Jest configuration correctly handles the new import syntax, and release-please is a widely-adopted standard tool.
• No files require special attention

Important Files Changed

Filename	Overview
src/workos.ts	Replaced hardcoded VERSION constant with dynamic import from package.json, enabling automated version management
jest.config.cjs	Unified transform configuration to use jest-transform-esm.cjs for both .ts and .js files, replacing ts-jest
.github/workflows/release-please.yml	Added workflow to automate version bumps and changelog generation using release-please action
release-please-config.json	Configured release-please for Node.js package with minor version bumps pre-1.0
.release-please-manifest.json	Initialized version manifest at 8.2.0 to track current release state
package.json	Removed ts-jest dependency as it's no longer needed with babel-jest transformer
package-lock.json	Removed ts-jest and its entire dependency tree from lockfile

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Git as Git (main branch)
    participant RP as Release Please Action
    participant GH as GitHub Release
    participant NPM as NPM Registry

    Dev->>Git: Push commit with conventional commit message<br/>(feat:, fix:, chore:, etc.)
    Git->>RP: Trigger release-please workflow
    RP->>RP: Parse commits since last release
    RP->>RP: Calculate new version number
    RP->>RP: Generate/update CHANGELOG.md
    RP->>Git: Create or update Release PR<br/>(version bump in package.json)
    
    Dev->>Git: Review and merge Release PR
    Git->>RP: Trigger release-please on merge
    RP->>GH: Create GitHub Release with tag
    
    GH->>NPM: Trigger release.yml workflow
    NPM->>NPM: Install dependencies
    NPM->>NPM: Run build (tsdown)
    NPM->>NPM: Run tests
    NPM->>NPM: Publish to npm registry
    
    Note over Dev,NPM: VERSION in User-Agent derived from package.json<br/>automatically reflects new version

Loading

[greptile-apps]

_{7 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}