feat: transition to RPC for market tracking trends | LLMO-3922#2044
Merged
feat: transition to RPC for market tracking trends | LLMO-3922#2044
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
This PR will trigger no release when merged. |
vivesing
approved these changes
Mar 27, 2026
solaris007
pushed a commit
that referenced
this pull request
Apr 2, 2026
# [1.403.0](v1.402.0...v1.403.0) (2026-04-02) ### Features * transition to RPC for market tracking trends | LLMO-3922 ([#2044](#2044)) ([9fce656](9fce656))
Member
|
🎉 This PR is included in version 1.403.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
ravverma
pushed a commit
that referenced
this pull request
Apr 6, 2026
Please ensure your pull request adheres to the following guidelines: - [x] make sure to link the related issues in this description. Or if there's no issue created, make sure you describe here the problem you're solving. - [x] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes If the PR is changing the API specification: - [ ] make sure you add a "Not implemented yet" note the endpoint description, if the implementation is not ready yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet. - [ ] make sure you add at least one example of the request and response. If the PR is changing the API implementation or an entity exposed through the API: - [ ] make sure you update the API specification and the examples to reflect the changes. If the PR is introducing a new audit type: - [ ] make sure you update the API specification with the type, schema of the audit result and an example ## Related Issues https://jira.corp.adobe.com/browse/LLMO-3922
ravverma
pushed a commit
that referenced
this pull request
Apr 6, 2026
# [1.403.0](v1.402.0...v1.403.0) (2026-04-02) ### Features * transition to RPC for market tracking trends | LLMO-3922 ([#2044](#2044)) ([9fce656](9fce656))
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
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.
Please ensure your pull request adheres to the following guidelines:
describe here the problem you're solving.
If the PR is changing the API specification:
yet. Ideally, return a 501 status code with a message explaining the feature is not implemented yet.
If the PR is changing the API implementation or an entity exposed through the API:
If the PR is introducing a new audit type:
Related Issues
https://jira.corp.adobe.com/browse/LLMO-3922