chore(main): release 0.15.0

[github-actions]

🤖 I have created a release beepboop

0.15.0 (2026-05-13)

Features

• add workos migrations command (#149) (7f5138f)

Bug Fixes

• bump @workos/skills to 0.6.0 (#151) (bded17e)

---

This PR was generated with Release Please. See documentation.

[github-actions]

🤖 Created releases:

• v0.15.0

🌻

[greptile-apps]

Greptile Summary

Automated Release Please PR bumping the CLI from 0.14.0 to 0.14.1. The sole underlying change is a dependency bump of @workos/skills to 0.6.0 (landed in #151).

• package.json and .release-please-manifest.json reflect the new patch version.
• CHANGELOG.md gains the 0.14.1 entry referencing the skills-package bump.

Confidence Score: 5/5

Purely mechanical version-bump files generated by Release Please — safe to merge.

All three changed files are generated release artifacts (manifest, changelog, package version). No application logic is touched and the changes are consistent across all files.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 0.14.0 to 0.14.1 — no issues.
CHANGELOG.md	New 0.14.1 changelog entry added documenting the @workos/skills bump — no issues.
package.json	Package version bumped from 0.14.0 to 0.14.1 — no issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["PR #151 merged\n@workos/skills → 0.6.0"] --> B["Release Please bot\ngenerates release PR"]
B --> C["package.json\n0.14.0 → 0.14.1"]
B --> D[".release-please-manifest.json\n0.14.0 → 0.14.1"]
B --> E["CHANGELOG.md\nadd 0.14.1 entry"]
C & D & E --> F["Merge & tag v0.14.1"]
F --> G["Publish to npm"]

Loading

_{Reviews (1): Last reviewed commit: "chore(main): release 0.15.0" | Re-trigger Greptile}