chore: update stack component releases - #1999
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
WalkthroughThe ChangesOpenAPI version pins
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Approve — automated reviewThis PR updates stack component release versions, the Gateway OpenAPI source URL, and Speakeasy lock metadata. The changes are purely mechanical version/metadata updates with no logic modifications. No issues were identified across all reviews. No findings. |
Summary
Update the Stack v3.2 component inputs to their latest stable releases:
v2.4.6→v2.4.12v2.1.5→v2.2.0v2.3.2→v2.5.0v2.4.3→v2.5.0v2.2.2→v2.4.0v2.2.0→v2.3.1Payments
v3.4.0, Searchv2.1.0, and Flowsv2.6.0were already current.Gateway OpenAPI source
Gateway
v2.3.1is a published stable release, but its GitHub release does not include theopenapi.yamlasset that older releases exposed. The tagged source still contains the file, so the Gateway download now uses the immutable version tag onraw.githubusercontent.com.Impact
The next Stack v3.2 release will merge and publish the OpenAPI definitions from the current stable service releases.
Validation
nix develop --impure --command just pre-commit.speakeasy/workflow.lockgit diff --checkSpeakeasy reported existing validation warnings/hints and a non-fatal cross-device warning while attempting to promote its downloaded CLI binary; generation completed successfully.