Releases: apastel/ytmusic-deleter
3.2.5
What's Changed
- Bugfix: Added a check that a library item has an album before trying to get the album ID
Full Changelog: 3.2.4...3.2.5
3.2.4
What's Changed
- Added monkeypatch solution to ytmusicapi's
get_library_playlists
function that will skip playlists that don't have a "title" attribute, as has been seen in the case of one user: sigma67/ytmusicapi#805- Enable verbose logging to see the playlist data when this happens
Full Changelog: 3.2.3...3.2.4
3.2.3
What's New
- Chrome/Edge are now working again for browser authentication!
Full Changelog: 3.2.2...3.2.3
3.2.1
What's Changed
- Improved "Remove Duplicates" responsiveness and visual feedback -- no longer fails when duplicate count is too high
- Added message about Chrome/Edge currently not working for browser auth
- Check if browser.json is expired and display warning message, instead of silently failing on playlist actions
- Dropped support for Python 3.9
Full Changelog: 3.1.3...3.2.1
3.1.3
What's Changed
🐞Bugfix 🐞
Albums or Singles that don't have an artist were causing an IndexOutOfRange
error when deleting
Example: Sessanta E.P.P.P. https://music.youtube.com/playlist?list=OLAK5uy_kHAhmzlFF1rpD5T58Ddj2mnsQu9s5YG6U
Full Changelog: 3.1.2...3.1.3
3.1.1
What's Changed
- OAuth login is now available again, but requires special setup instructions to obtain a
Client ID
andClient Secret
.- See the Attention notice at the top of this page: https://ytmusicapi.readthedocs.io/en/stable/setup/oauth.html
- After setting up a Google Cloud project and obtaining your credentials, click File -> Settings in YTMusic Deleter, check the box to enable OAuth, and paste in your
client_id
andclient_secret
, then close the Settings window and click Sign In and follow the instructions.
- The MacOS ARM installer is now built using MacOS Sequoia (15) instead of MacOS Sonoma (14) in an attempt to hopefully fix #114
If you currently have a version of YTMusic Deleter below 3.0.0, please uninstall it before installing any version 3.0.0 and above.
Full Changelog: 3.1.0...3.1.1
3.0.1
What's Changed
- Sorting Playlists fix: Ignore case when sorting by Track Title.
If you currently have a version of YTMusic Deleter below 3.0.0, please uninstall it before installing any version 3.0.0 and above.
Full Changelog: 3.0.0...3.0.1
3.0.0
What's Changed
Update for Windows Installer
IMPORTANT: If you already have YTMusic Deleter installed on your Windows computer, please uninstall it before installing this new version. Your settings will not be erased.
This update makes some important changes to the Windows installer:
- It no longer asks for administrator privileges, since it will now install at the User level instead of the System level.
- This means that it will only be installed for the current user, and not all users on your computer.
- It will take care to append the application name "YTMusic_Deleter" if you browse for a directory to install to other than the default (#115)
- The application display name will now be "YTMusic Deleter" without an underscore, while the filename will still be "YTMusic_Deleter.exe".
Other changes
Full Changelog: 2.13.1...3.0.0
2.13.1
🐞One More Bugfix 🐞
- It seems that unliking a song can take more than 100 retries, so I bumped that up to 300 and now it will log an error if all 300 tries were exhausted, instead of saying "Removed from Likes".
Full Changelog: 2.13.0...2.13.1
2.13.0
🐞Bugfix Release 🐞
This release fixed some major bugs! If you experienced any issues with Remove Library, Unlike All, or the "add to library" feature of Delete Uploads, you will want to check out this release.
Three major bugs were fixed:
- "Unlike All" will now actually unlike all of your liked songs, what a concept! I won't get into what the issue was but basically the Google API sometimes lies when it says it removed a song from your likes.
- Removing individual library songs works again.
- The "add to library" checkbox of Delete Uploads will now actually add the album to your library.
2 and 3 were both due to this issue in ytmusicapi sigma67/ytmusicapi#743. It hasn't been fixed yet (It's an A/B testing issue) but I added a monkey patch solution that will handle it temporarily until that's fixed.
Full Changelog: 2.12.0...2.13.0