Releases: muxinc/mux-go
Releases · muxinc/mux-go
v3.2.0
Changed Operations
- added
embedded_subtitlestoLiveStreamResponse - added
live_stream_idtolist-delivery-usage
New Operations
update-live-streamupdate-assetcreate-playback-restrictionlist-playback-restrictionsdelete-playback-restrictionget-playback-restrictionupdate-referrer-domain-restriction
For more information, consult the API reference at https://docs.mux.com/api-reference/video .
Thanks for using Mux!
v3.1.0
v3.0.0
- breaking change: the
max_channel_layoutfield ofTrackwas an enum and is now an open string, as our internal implementation couldn't realistically and exhaustively enumerate all possible options. This should be a very small change that applies only to projects ingesting media with multi-channel, non-stereo audio (5.1, 7.1, etc.). for mux-go specifically, this breaking change is logical rather than in code, as our current OpenAPI templates do not validate enums; doing so is on the roadmap. We wanted to still go with a breaking change to signal to our users that the contract for their application has changed. - no, you're not missing a 2.x release - we've bumped this to 3.x to synchronize version numbering across our SDKs.
v1.1.1
- minor doc updates; check the API reference for more
v1.1.0
- Live Captions is now GA!
- Minor API documentation fixes; consult the API reference for full details.
v1.0.1
- re-release to override broken
1.0.0release; the prior1.0.0release, once ready to go, will become2.0.0 - added operation
get-live-stream-playback-id; consult https://docs.mux.com/api-reference for up-to-date details on our API
v0.15.1
v0.15.0
- Low latency (public beta) has landed! https://docs.mux.com/guides/video/reduce-live-stream-latency#lower-latency-options
- Minor API updates; consult https://docs.mux.com/api-reference for our canonical API reference.
v0.14.0
- new API endpoints and feature updates; consult https://docs.mux.com for details
This release replaces the attempted 1.0.0 release, which had some regressions we didn't intend in it. We'll be moving mux-go to our newer release platform as time permits and as we're confident that we won't cause developer-facing regressions. Sorry about the confusion!