chore: bump @workos/oagen to ^0.15.0#77
Merged
gjtorikian merged 1 commit intomainfrom May 2, 2026
Merged
Conversation
oagen 0.13/0.14/0.15 ship the rename-detection passes that downgrade type/enum renames from breaking to soft-risk in compat reports (workos/oagen #49, #51, #53). Until this bump, downstream consumers that pull oagen-emitters still resolve to oagen 0.12.0 nested under node_modules/@workos/oagen-emitters/node_modules — so the new extractor + differ logic never runs and breaking-changes reports stay unchanged from pre-0.13 behaviour. Verified: workos/openapi-spec#17 currently shows breaking=11 because oagen-emitters is pinned to ^0.12.0; after this bump and an oagen-emitters release, the same diff drops to breaking=0 across all five languages (validated locally by re-extracting + re-diffing each SDK with oagen 0.15.0). All 399 tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why workos/openapi-spec#17 still shows breaking changes
oagen 0.13/0.14/0.15 ship rename-detection passes (#49, #51, #53) that downgrade type/enum renames from breaking to soft-risk in compat reports. But oagen-emitters declares `"@workos/oagen": "^0.12.0"` — a constraint that pins to 0.12.x and prevents npm from deduping with the root.
Concretely: when openapi-spec installs oagen 0.15.0 at the root, npm also installs a nested copy of oagen 0.12.0 under `node_modules/@workos/oagen-emitters/node_modules/@workos/oagen` to satisfy the `^0.12.0` constraint. At runtime, oagen-emitters' `import { phpExtractor } from '@workos/oagen/compat'` resolves through the nested 0.12.0 — so the new extractor + differ logic never runs.
Result: the compat report on PR #17 shows the same 11 breaking changes it would have shown before any of #49/#51/#53 were merged.
What this PR changes
One-line: bump the dependency constraint to `^0.15.0` so npm can dedup to the root install. `package-lock.json` updated.
Verified
Locally re-extracted + re-diffed all five language SDKs against PR #17's spec change with this bump applied:
(dotnet and go were already 0 because oagen-emitters' nested 0.12.0 happened to include the differ-side passes via re-export resolution, but the extractor changes from #53 — which give PHP/Python/Ruby their field/enum_member info — only kick in once oagen ≥ 0.15 is the resolved version.)
Once this lands and oagen-emitters cuts a release, openapi-spec only needs to bump oagen-emitters and CI on PR #17 should default-pass.
Test plan
🤖 Generated with Claude Code