nightly-a6af177b-ls259

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-a6af177b-ls259/index.html

LinuxServer Changes:

No changes

Remote Changes:

Make sure labels can be added to PRs

nightly-657a3a2e-ls259

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-657a3a2e-ls259/index.html

LinuxServer Changes:

No changes

Remote Changes:

fix(deezer): use artist ID to detect Various Artists releases (#6499)

Fixes #4956

The Deezer API apparently uses IP geolocation to return a localized
“Various Artists” name (e.g. “Verschiedene Interpreten” in German),
causing VA releases to match poorly and display the wrong artist name.

This implements the approach suggested by @sampsyo in
beetbox/beets#4956:
detect VA releases using Deezer’s (hopefully) stable various artists ID
(5080) instead of a string comparison, then replace the localized name
with the user’s configured va_name, mirroring what the MusicBrainz
plugin already does with its own VARIOUS_ARTISTS_ID.

nightly-506b45f3-ls259

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-506b45f3-ls259/index.html

LinuxServer Changes:

No changes

Remote Changes:

Label issues/prs case-insensitively (#6505)

Make PR label patterns case-insensitive

All label-matching patterns in .github/labeler.yaml are updated to use
the /pattern/i regex syntax, enabling case-insensitive matching.

Before: 'fetchart'
After: '/fetchart/i'

This ensures PRs are correctly labelled regardless of capitalisation in
commit messages or PR titles (e.g., FetchArt, FETCHART, fetchart
all match).

See github/issue-labeler#15

nightly-29d5fac9-ls259

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-29d5fac9-ls259/index.html

LinuxServer Changes:

Full Changelog: nightly-131768b7-ls258...nightly-29d5fac9-ls259

Remote Changes:

feat(chroma): add chromasearch command (#6486)

Add a new command to the chroma plugin: chromasearch.

This command lets user search the database by chromaprint fingerprint
similarity.
Database item fingerprints are computed on the fly if needed. This is
useful for example to check if an unknown / untagged audio file already
exists in the database.

Will update changelog and doc once naming & co are sorted.

nightly-20acca65-ls259

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-20acca65-ls259/index.html

LinuxServer Changes:

No changes

Remote Changes:

fix(replaygain): clear conflicting tags on write (#6498)

There are two ways to store replay gain data on music files: RG_ and
R128_ (opus).
Before this change the beets replaygain plugin simply set the right tag
based on file format and r128 config value. there are case, however,
when for example an opus files comes with RG_ tags already set. After
beet write its replaingain tags the files will contain both RG_ and
R128_ tags with possibly conflicting values.

For example, Navidrome currently always prefers RG_ tags over R128_
regardless of format, leading tags set by beets to be ignored.
https://github.com/navidrome/navidrome/blob/23f3556371321faf199866989b906f2ef06a8034/model/metadata/map_mediafile.go#L111

As per RFC 7845: Ogg Encapsulation for the Opus Audio Codec
https://datatracker.ietf.org/doc/html/rfc7845#section-5.2.1

To avoid confusion with multiple normalization schemes, an Opus
comment header SHOULD NOT contain any of the REPLAYGAIN_TRACK_GAIN,
REPLAYGAIN_TRACK_PEAK, REPLAYGAIN_ALBUM_GAIN, or
REPLAYGAIN_ALBUM_PEAK tags, unless they are only to be used in some
context where there is guaranteed to be no such confusion.

Since the replaygain plugin does not support setting both RG_ and R128_
at the same time it doesn't make much sense to keep conflicting tags
when writing. These tags are also easy to recalculate if needed either
with beets itself (with a different configuration), or by running
replaygain commands by hand. no valuable information is lost.

This change makes it so the replagain plugin now deletes conflicting
tags when processing library items:

• RG_ are deleted if we set R128_
• R128_ are deleted if we set RG_

nightly-06512c9b-ls259

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-06512c9b-ls259/index.html

LinuxServer Changes:

No changes

Remote Changes:

Use multi value remixers, composers, lyricists and arrangers (#6487)

Migrate artist-credit fields to multi-value lists

Fixes: #5698
Supersedes: #5847

This converts remixer, lyricist, composer, and arranger into
proper multi-value fields: remixers, lyricists, composers, and
arrangers.

What changed

• Data model (beets/library/models.py): replaces the legacy
  single-string remixer, lyricist, composer, and arranger fields
  with multi-value list fields.
• Migrations (beets/library/migrations.py,
  beets/library/library.py): extracts a reusable
  MultiValueFieldMigration base class and adds field-specific migrations
  for remixers, lyricists, composers, and arrangers.
• Metadata compatibility (beets/autotag/hooks.py): centralizes
  legacy singular-to-plural compatibility in Info / TrackInfo, so old
  assignments like info.remixer = "..." still work and populate the new
  list fields.
• MusicBrainz (beetsplug/musicbrainz.py): now preserves these
  credits as lists instead of comma-joined strings.
• Follow-up updates: adjusts tests, docs, and related field mappings
  (aura, bpd) to use the plural multi-value fields, and bumps the
  minimum mediafile version to 0.16.0.

Impact

• Existing libraries are migrated automatically on first run.
• Older code assigning singular string fields continues to work via the
  compatibility shim, but emits DeprecationWarnings.
• These metadata fields now behave consistently with other multi-value
  fields like genres.

2.8.0-ls322

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/2.8.0-ls322/index.html

LinuxServer Changes:

Full Changelog: 2.8.0-ls321...2.8.0-ls322

Remote Changes:

Updating PIP version of beets to 2.8.0

nightly-e5365145-ls258

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-e5365145-ls258/index.html

LinuxServer Changes:

Full Changelog: nightly-ad20cc71-ls257...nightly-e5365145-ls258

Remote Changes:

autobpm: Add --force and --quiet options; Deprecate overwrite (#6481)

Description

Reveal the overwrite config setting to the CLI and at the same time
deprecate the option name. It should be named force to streamline with
other beets configs of the same kind.

Add a quiet CLI flag and config option that leaves out output
pointing to already existing BPM values

nightly-e5365145-ls257

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-e5365145-ls257/index.html

LinuxServer Changes:

No changes

Remote Changes:

autobpm: Add --force and --quiet options; Deprecate overwrite (#6481)

Description

Reveal the overwrite config setting to the CLI and at the same time
deprecate the option name. It should be named force to streamline with
other beets configs of the same kind.

Add a quiet CLI flag and config option that leaves out output
pointing to already existing BPM values

nightly-ad20cc71-ls257

CI Report:

https://ci-tests.linuxserver.io/linuxserver/beets/nightly-ad20cc71-ls257/index.html

LinuxServer Changes:

Full Changelog: nightly-712bada6-ls256...nightly-ad20cc71-ls257

Remote Changes:

Add filename extension for music files with no extension during import (#6457)

Fixes #4881.

When user imports files with no extension, ffprobe is used to check the
format of the file. If its in a music format, a copy of the file is
created with the detected extension and that file is imported instead of
the original. If it is not a music format, it change nothing (I believe
non-music files are already filtered out somewhere else in the import
pipeline). If there is a file in the same directory with the same name
and has the same extension as the detected format, import that file
instead.