Skip to content

bumped beets to 2.10#321

Merged
pSpitzner merged 5 commits into
release/2.0.0from
beets_2_10_0
Jun 16, 2026
Merged

bumped beets to 2.10#321
pSpitzner merged 5 commits into
release/2.0.0from
beets_2_10_0

Conversation

@pSpitzner

Copy link
Copy Markdown
Owner

No description provided.

@pSpitzner

Copy link
Copy Markdown
Owner Author

hey @btc08gh,

this is the PR I mentioned, where we bump beets to 2.10.
With the fixes from 2.9 this was pretty straightforward.

For our databases, we did not need to fix any beets-flask code to get the relative paths to work.
This should now all be handled by beets. I guess your issue simply came from running a newer beets database with an older beets version!

Feel free to check the latest v2 rc (or wait a bit, final v2 should land soon).

best,
p

@pSpitzner pSpitzner merged commit fe6ae5d into release/2.0.0 Jun 16, 2026
2 checks passed
@pSpitzner pSpitzner deleted the beets_2_10_0 branch June 16, 2026 19:06
@pSpitzner pSpitzner restored the beets_2_10_0 branch June 16, 2026 19:06
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.

2 participants