Releases: sigma67/ytmusicapi
Releases · sigma67/ytmusicapi
v1.3.2
Full Changelog: 1.3.1...1.3.2
v1.3.1
Full Changelog: 1.3.0...1.3.1
1.3.0
v1.2.1
v1.2.0
Features ✨
search
: added support forprofiles
filter andprofile
type search results
Fixes 🐞
v1.1.1
Fixes 🐞
- oauth refresh on request (#403) ( thanks @zeitmeister )
- fix 'secondSubtitle' KeyError for some playlists (#399) ( thanks @MarvinSchenkel )
v1.1.0
Features ✨
- add location support (#386). A new initialization parameter supports changing the region. This is equivalent to setting the region in your YouTube Music Settings.
- add external OAuth case to browser check (#396) (thanks @MarvinSchenkel ). This supports the case of using OAuth authentication with browser credentials, see the issue for more information
- added dutch translations ( thanks @Vistaus , #383)
- open browser on
ytmusic oauth
call (#384)
Fixes 🐞
- fixed unrecognized case sensitive headers during auth (thanks @czifumasa )
get_playlist
: fixed issues withviews
return value andlimit
parameter
v1.0.2
v1.0.1
v1.0.0
It's been 3 years since #10 was created, but now this project finally has a way of OAuth authentication. Therefore it is considered feature complete for now and ready for a v1.0 release, just in time for almost 1k 🌟! The next major release will be v2.0 featuring proper types with pydantic.
Overall there are not many breaking changes in this release, only the setup procedure has changed. It was a priority to integrate the new OAuth authentication as seamlessly as possible.
Features ✨
- support OAuth authentication (#10, thanks @vixalien).
get_search_suggestions
: get the suggestions that appear during typing on YouTube Music (thanks @omgupta15 )- CLI for setup. Call
ytmusicapi browser
for traditional auth using browser headers orytmusicapi oauth
to use the new OAuth authentication (it's simple and fast!)
Breaking Changes ⚒
- Setup procedure has been reworked. for library use, you can simple do
from ytmusicapi import setup
instead of importing theYTMusic
object
Fixes 🐞
search
has been a bit problematic since the recent server side changes to top results, it should now be more reliable. If you still notice some odd search results please create an issue