Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Sep 26, 2025

This PR contains the following updates:

Package Change Age Confidence
discord-player (source) 6.6.2 -> 6.7.1 age confidence

Release Notes

Androz2091/discord-player (discord-player)

v6.7.1

Compare Source

What's Changed

  • fix(queue): add check for null on bridge property by @​Kamiloo13 in #​1925
  • fix(IPRotator): require manual ip package installation

New Contributors

Full Changelog: https://github.com/Androz2091/discord-player/compare/[email protected]@6.7.1

v6.7.0

Compare Source

What's Changed

Full Changelog: https://github.com/Androz2091/discord-player/compare/[email protected]@6.7.0

v6.6.10

Compare Source

What's Changed

Full Changelog: https://github.com/Androz2091/discord-player/compare/[email protected]@6.6.10

v6.6.9

Compare Source

New Features

  • New lyrics API and synced lyrics feature is now stable
  • Track now contains cleanTitle property which removes junk from track titles.
New lyrics API
// other methods include .get() .getById() etc.
const results = await player.lyrics.search({ q: track }); // this is a lot better than genius, if you want to search by current track - use track.cleanTitle as the query and specify artistName as well in such situations
// player.lyrics also takes care of ratelimits so you will not get ratelimited
const lyrics= results[0];

if (!lyrics.syncedLyrics) {
  return // no synced lyrics available
}

// load lyrics
const syncedLyrics = queue.syncedLyrics(lyrics);

syncedLyrics.at(timestampInMilliseconds); // manually get a line at specific timestamp. Discord Player resolves closest timestamp

// Synchronize lyrics with the queue
syncedLyrics.onChange(async (lyrics, timestamp) => {
    // timestamp = timestamp in lyrics (not queue's time)
    // lyrics = line in that timestamp
    await interaction.channel?.send({
        content: `[${timestamp}]: ${lyrics}`
    });
});

const unsubscribe = syncedLyrics.subscribe(); // start watching the queue for live updates

unsubscribe(); // call this when you are done, discord-player does this automatically when track ends

What's Changed

New Contributors

Full Changelog: https://github.com/Androz2091/discord-player/compare/[email protected]@6.6.9

v6.6.8

Compare Source

New hooks api

Good to know: Previous hooks api is still valid and works as expected.

Previously, hooks required you to pass guild/id as an argument which is expressed as:

const queue = useQueue(interaction.guild.id);

With the new update, there is another method of using hooks, which does not require you to pass guild/id as an argument. In other words, the following code will automatically get the correct queue.

const queue = useQueue();

In order to use this method for hooks, you will need to update your command handler to execute your command with hooks context, which can be written as:

// assuming the following is our command to be executed
const command = getCommandToExecute();

// we would normally execute it as
await command.execute(interaction);

// instead, we have to use the following
const ctx = { guild: interaction.guild };
await player.context.provide(ctx, () => command.execute(interaction));

This would allow every command to use discord-player hooks without having to specify guild/id.

Why is this necessary?

Lets say you have a command and it calls utility function(s) and that utility function also requires access to discord-player data. You'd normally pass it down through arguments over and over again until it reaches the destination. But with this api, you do not need to pass it down via arguments. It will be directly available to the destination.

Changelog

New Contributors

Full Changelog: https://github.com/Androz2091/discord-player/compare/@discord-player/[email protected]@6.6.8

v6.6.7

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/Androz2091/discord-player/compare/[email protected]@6.6.7

v6.6.6

Compare Source

What's Changed

Full Changelog: https://github.com/Androz2091/discord-player/compare/@discord-player/[email protected]@6.6.6

v6.6.5

Compare Source

What's Changed

New Contributors

Full Changelog: https://github.com/Androz2091/discord-player/compare/@discord-player/[email protected]@6.6.5

v6.6.4

Compare Source

What's Changed

  • fix(QueryResolver): fix youtube playlists resolver
  • feat(GuildQueue): ability to properly disable filters
  • update Mirasaki Music Bot version by @​Mirasaki in #​1806
  • docs: update Mittelbot showcase version & description by @​Mittelblut9 in #​1807

Full Changelog: https://github.com/Androz2091/discord-player/compare/@discord-player/[email protected]@6.6.4

v6.6.3

Compare Source

What's Changed

  • [Docs] Mediaplex and discord-player singleton by @​febkosq8 in #​1798
  • feat: add experimental ip rotator
  • fix(DefaultVoiceStateHandler): fix random unpause due to pauseOnEmpty
  • feat: switch to discord-voip
  • feat(AudioFilters): add silenceremove filter
  • fix: #private property missing in querycache when making customquerycache #​1790
  • fix: only allow youtube bridge when youtube extractor is registered #​1789
  • lots of bug fixes and imrovements

Full Changelog: https://github.com/Androz2091/discord-player/compare/@discord-player/[email protected]@6.6.3


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/discord-player-6.x-lockfile branch from 36402c1 to 4add404 Compare October 25, 2025 07:28
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