Release 1.3.1 - #53
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
1 participant
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.
What
Folds the pending changesets into the 1.3.1 release. Version propagated by
scripts/create_version.dart, all version checks pass,.changes/emptied.Changelog
Why now
Published 1.3.0 pins flutter_webrtc 1.2.1 exactly, which forces resolution down to livekit_client 2.6.1 for every consumer including the agent starter (#49). This release depends on livekit_client ^2.10.0 with no flutter_webrtc pin, so resolution always follows whatever livekit_client pins.
After merge
Tag
v1.3.1to publish. With the pin gone there is no expected validation warning, so the stock publish workflow should pass as is.Downstream: agent-starter-flutter bumps to
livekit_components: ^1.3.1andlivekit_client: ^2.10.0.