Chore/sync with platform api 2026.02.24#186
Merged
harshadixit12 merged 4 commits intorelease/0.16.0from Feb 24, 2026
Merged
Conversation
mheap
approved these changes
Feb 24, 2026
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.
Summary
In this PR, we are syncing with platform-api.
Notable changes are for Event Gateways - breaking changes in some resources to improve the field names based on past feedback. (Included in CHANGELOG.md)
To help with breaking change, we wrote an initial draft of doc to remove and import resources - but this is not ready yet. I'll update it and share with docs team.
We chose not to build state migrators to avoid overhead of adding them on every breaking change, which is not rare on the beta provider - a generic doc on removing from state and importing should be useful enough IMO.
Issues resolved
Related PRs on platform-api (if any)
Checklist ✅
CHANGELOG.mdto clearly mention any breaking changes, new features and bug fixesrelease/x.y.z) andgit cherry-pickif necessary)