Adrian Sampson

Thanks! Not sure how this one didn't get bumped when the other occurrences did. We have not previously had the workflow set up to append `-git` or similar to pre-release...

You've hit the nail on the head. It's an unfortunate naming collision—one that exists mainly for historical reasons. Namely, the `Item` and `Album` objects predate `dbcore`; we refactored the latter...

Thanks for getting in touch!! Can you please email the core team's Zulip instance at email.218c36e48d78cf125c0a6219a6c2a417.show-sender@streams.zulipchat.com? And thanks for the reminder about a `SECURITY.md`. We should indeed do that!

Thank you for the report. We've discussed this internally and have decided that the risk is sufficiently minimal that we feel comfortable talking about this bug in public. The gist...

I guess I'm not sure why this regex does `]*)*>` instead of just ``. Does it really matter whether the `` tag contains pairs of characters like that? I can't...

Here's the public URL for the blog post, FYI! https://beets.io/blog/walkthrough.html

Thanks for the suggestion! It would indeed be great to do a better job describing the project’s architecture as a “way in” to understanding how to contribute. The best we...

Ok, sounds intriguing! How would you propose to expose the "parent work" information? Would we just record the title, or other stuff too? Do you have ideas for the names...

OK, so just to summarize, you'd like to be able to access these fields in path templates, right? * `$work`: This would be the title of the directly associated work....

OK, thanks. But just to be clear, `$composer` already does what you want, right? If so, I'll make this ticket into a request to get the work title field. Then,...