Skip to content

Release 0.2.2

Compare
Choose a tag to compare
@github-actions github-actions released this 23 Aug 14:19
cee5d29

First GitHub tagged release!

# Docker Hub
$ docker pull jareddantis/blanco-bot:0.2.2

# GHCR
$ docker pull ghcr.io/jareddantis-bots/blanco-bot:0.2.2

For users

  • Added support for YouTube Music URLs
  • Artwork for non-Spotify sources will now be shown in the Now Playing card
  • Blanco will now attempt to match your search against Spotify's catalog
    • If a close enough match is not found, search queries will be forwarded to YouTube like before.
  • Added a /stats command for viewing Lavalink node statistics
    • This command currently only works if you own the bot instance.
    • This might be changed in the future to allow any server admin to use it.

For admins and developers

Breaking changes

  • Switched from Lavalink.py to Mafic for Lavalink v4 support

    • Parts of Blanco were rewritten to accommodate Mafic, with Lavalink v4 in mind.
    • Lavalink v3 will be unsupported once v4 is out of beta.
    • Blanco now expects a list of regions for every node in config.yml.
    Example config
    lavalink:
      - id: my-beautiful-node
        server: 127.0.0.1
        port: 2333
        password: 'anything as a password'
        ssl: false
    
        # Previously:
        # region: us-central
        regions:
          - hongkong
          - singapore
          - sydney

Other changes

  • Blanco's Docker image is now also available from ghcr.io
  • Blanco's Docker image is now also being built for ARMv7 targets
  • Blanco's console logs are now better formatted (with color!), thanks to the logging module
  • Updated base image to Python 3.11
    • Python 3.10 should still work for non-Docker deployments, but is now unsupported going forward.

Known bugs

  • /stats command
    • The uptime counter is currently broken. A node might be shown as having been up for three years when it's barely been two days.
    • Currently unclear if this is an issue with Mafic, the Lavalink v4 beta, or how uptimes work inside Docker containers.
    • Will probably be fixed in a future release, but it's not really breaking any important functionality...
  • Track matching
    • Due to Blanco's track matching logic, it is possible that an hour(s)-long loop on YouTube might be chosen as a playback candidate for a Spotify track without a matching ISRC.
    • This will be fixed in a future release.