chore(main): release 1.2.0

[workos-sdk-automation]

🤖 I have created a release beep boop

1.2.0 (2026-02-09)

Features

• Add external_id support for User and Organization entities (#83) (0394535)
• Add lint-pr-title workflow (#88) (4972e11)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR is a Release Please-generated release bump to 1.2.0: it updates the release manifest, bumps @version mix.exs, and adds a CHANGELOG.md entry for the external_id feature shipped in #83.

Main issue: mix.exs still sets project/0 source_ref to the bare version (e.g. 1.2.0), but the repository’s tags are v-prefixed (e.g. v1.1.4) and docs/0 already uses v#{@version}. This mismatch will cause hex metadata/source links to point at a non-existent ref for the release unless fixed.

Confidence Score: 4/5

• Mostly safe to merge, but fix the mix.exs source_ref/tag mismatch first.
• Changes are limited to release metadata and a changelog entry. The only functional integration risk identified is that source_ref in mix.exs likely points to a non-existent git ref for v-prefixed tags, which breaks published package source links.
• mix.exs

Important Files Changed

Filename	Overview
.release-please-manifest.json	Bumps release-please manifest version from 1.1.4 to 1.2.0; no functional code impact.
CHANGELOG.md	Adds initial CHANGELOG entry for 1.2.0; content matches release note for external_id feature.
mix.exs	Bumps project version to 1.2.0; project/0 still uses source_ref: "#{@version}" (no v-prefix) which likely doesn’t exist given repo tags are v-prefixed.

Sequence Diagram

sequenceDiagram
    participant Dev as Maintainer
    participant RP as Release Please
    participant Git as Git repo
    participant Hex as Hex.pm

    Dev->>RP: Merge release PR (#85)
    RP->>Git: Update manifest (.release-please-manifest.json)
    RP->>Git: Update project version (mix.exs @version)
    RP->>Git: Generate changelog (CHANGELOG.md)
    Dev->>Hex: Publish package
    Hex->>Git: Resolve source_ref from mix.exs metadata
    Note over Hex,Git: If source_ref doesn't match a real tag (e.g. needs v-prefix), source links break

Loading

[greptile-apps]

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (1)

mix.exs
Invalid source_ref tag

project/0 sets source_ref: "#{@version}", but this repo’s release tags are v-prefixed (e.g. v1.1.4) and docs/0 already uses source_ref: "v#{@version}". With @version "1.2.0", source_ref will likely point to a non-existent git ref (1.2.0), which breaks hex metadata/source links for the release. Consider changing it to "v#{@version}" to match the tag convention.

[workos-sdk-automation]

🤖 Created releases:

• v1.2.0

🌻