feat(api): sync OpenAPI spec from production - #43
Merged
Merged
Conversation
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
2 participants
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.
Empty commit carrying the conventional subject release-please needs.
The SDK content for this release is already on
main— promoted from staging after sent-dm-sdk-pipeline#52. The generate workflow uses the merged pipeline PR title as the SDK commit subject, and that PR was titled descriptively rather than as a conventional commit, so release-please saw nothing releasable and cut no version (or, where a separatefix:commit existed, only a patch).No file changes — the SDK is unchanged and already correct. This only gives release-please a
feat(api):commit so it cuts a minor release with a changelog that reflects the actual surface: Sender Profiles v3, the Multi-Partner Solutions WhatsApp pool, RCS agents, sub-country curfews and the compliance contract.The equivalent commit is already on the staging trunk, but an empty commit cannot travel through
Promote SDKs— that workflow compares trees and correctly treats a no-op as nothing to promote.