Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release/v3.33.1 #1386

Merged
merged 8 commits into from
Feb 21, 2024
Merged

Release/v3.33.1 #1386

merged 8 commits into from
Feb 21, 2024

Conversation

peaBerberian
Copy link
Collaborator

This is the PR for the v3.33.1 the last v3 release considered as latest on npm.

The official v4.0.0 will be released just after, and will mark our transition to a stable v4, now considered our main version.
v3 will still be maintained, and potential v3 releases may still be made (for bug fixes and minor improvements) under the legacy-v3 tag on npm.

To note that this release only brings minor bug fixes on top of the v3.33.0, none being regressions (those issues have been here since the corresponding features have been introduced). This reassure us that the v3 is stable enough for it to be reliable for people not having the time budget to make the switch to a v4 yet.

Left issues we know we have on v3 are:

  • niche issues on Tizen (Samsung TVs).
    For example we are aware of some live pre-roll use cases with weird player behavior. This has been fixed in v4 but the ""fix"" (more of a work-around really) is too complex to be backported to the v3 easily. We would have to re-do the development and testing there, for what seems to be very rare issues just on Tizen TVs.

  • The usual trail of DRM compatibilities issues.

    The "Encrypted Media Extensions" API allowing media decryption in a browser is notorious to break every other day on a random device when relying on specific configurations. Those issues come and go, sometimes they are fixed without any action on our part after a firmware update, other times we bring a work-around (on top of a work-around on top of a work-around, which may sometimes break legitimate use cases, yay!). Just yesterday we again noticed and fixed an issue arising in very specific conditions with the PlayStation 5 (we're trying a solution only for Canal+ applications for now).

    Most of those issues should be fixed in future v3 maintenance releases.

Changelog

Bug fixes

Other improvements

@peaBerberian peaBerberian merged commit c999760 into legacy-v3 Feb 21, 2024
3 checks passed
@peaBerberian peaBerberian modified the milestone: 3.33.0 Feb 23, 2024
@peaBerberian peaBerberian deleted the release/v3.33.1 branch July 26, 2024 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant