feat: Release 1.2.0 #279
Merged
feat: Release 1.2.0 #279
Conversation
This file contains 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
Contributor
kevinshahfws
commented
Jun 14, 2024
kevinshahfws
commented
- User Interest
- Command and Control intents
## [1.1.1-next.1](v1.1.0...v1.1.1-next.1) (2024-02-28) ### Bug Fixes * Removed sdk as required field from Device.version ([#231](#231)) ([ef3de3e](ef3de3e))
## [1.1.1-next.2](v1.1.1-next.1...v1.1.1-next.2) (2024-03-06) ### Bug Fixes * Add PlaylistEntity to EntityIntent ([9769d6d](9769d6d))
Core sanity suite execution from Mock-Firebolt on the PR
* CPPSDK: manage test added (#189) * CPPSDK: standalone cpp test case added (#190) * CPPTest: CXX compilor target added (#191) * CPPSDK: test event sample test added (#192) * CPPSDK: test event sample test added * CPPSDK: more event test added * CPPSDK: test updates based on interface name changes + disable rpc-only based methods/events (#205) * CPPSDK: test case added for core (#209) * CPPSDK: test case added for core * Manage Test update based on provider integration * Manage Test update based on provider integration * Core test update to add more test case to link with provider sequence * Core/Manage test app updates * CPPSDK: templates added for metrics calls-metrics methods * CPPSDK: test updates * CPPSDK: Core test app updated with discovery.launch and watchNext * CPPSDK: Core test cases added for discovery and capabilities * CPPSDK: Core test cases updated based on openrpc generation support in features/cpp branch * CPPSDK: install command added (#218) * CoreTest: use has_value() check before accessing optional field (#222) * use cpp header for strtok (#228) * CPPSDK: use cpp header for strtok and cleanup (#230) * CPP: update based on merge with next branch (#237) * CPPSDK: updated Core test app to align with next branch merge changes (#238) * CPPSDK: Async test case updates (#249) * Pointed openrpc to cpp branch * Pointed openrpc to cpp branch * fix: Upgrade to latest firebolt-openrpc next build --------- Co-authored-by: Santhosh Ramani <[email protected]> Co-authored-by: Shah, Kevin <[email protected]> Co-authored-by: Jeremy LaCivita <[email protected]>
* New workflow * Fix: Not really * Undo comments * Undo comments * Added merge workflows * fix: Reversed version override flow * Less logins on GH Actions
# [1.2.0-next.2](v1.2.0-next.1...v1.2.0-next.2) (2024-04-08) ### Features * CI/CD docs (next-major) and merges (next-major/main) ([#245](#245)) ([49ab03d](49ab03d))
Standardizing Intent Message requirements
In additional to traditional discovery APIs such as Watch History and Watch Next, Firebolt provides a more abstract API that facilitates impromptu content discovery connections between first-party Aggregated Experiences and third-party Apps. The User Interest Capability enables Apps to provide meta-data on content that the user has expressed an interest in to Aggregated Experience Apps that have been given access to use this Capability. This allows for open ended design of Aggregated Experience App features that present App-specific content to re-engage the user with the content inside the originating App. While the functionality and UX is left to the Aggregated Experience App, typically designed by each Firebolt Distributor, the Firebolt API enables events to register user interest and pass entity meta-data. Which generally enables Aggregated Experiences to present that entity meta-data in some way that leads to re-launching the original App at a later point, using a `navigateTo` notification. This is just one example of what an Aggregated Experience App might do with the User Interest API. Note that this API **SHOULD NOT** be used to implement Watch History or Watch Next features. These concepts are much more fundamental to Firebolt and have explicit APIs so that Firebolt Distributors can keep track of which apps are using them separately.
# [1.2.0-next.3](v1.2.0-next.2...v1.2.0-next.3) (2024-06-06) ### Features * User Interest ([#170](#170)) ([48a1094](48a1094))
* feat: Command and Control Intents * Addition of the intents to control Firebolt compliant devices. Control intents are for user intentions that will be needed regardless of whether there are any apps installed such as Power Intents, Volume Intents, Channel Intents, Media Control Intents
# [1.2.0-next.4](v1.2.0-next.3...v1.2.0-next.4) (2024-06-06) ### Features * Command and Control Intents ([#251](#251)) ([c8f8dae](c8f8dae))
* chore(capabilities): Adding missing specs * fix: Cleanup of Capabilities requirements * Remove dangling requirements or replaced them with "This concept is out of scope for this document"
* fix: Remove x-alternatives that don't exist * fix: Cut ProviderPolicy from App Pass-through
# [1.2.0-next.5](v1.2.0-next.4...v1.2.0-next.5) (2024-06-13) ### Bug Fixes * Remove x-alternatives that don't exist ([#278](#278)) ([e38ad5a](e38ad5a))
jlacivita
approved these changes
Jun 14, 2024
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.0-next.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
1 similar comment
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.