Adrian Sampson

Indeed; it would be great to know when/how these writes happen… is there any chance it's a consequence of your configuration or plugins you're using? Understanding a bit more about...

It's sort of an open-ended recommendation, to be honest! In general, to understand how to proceed here, we will need to understand where those two writes are happening on your...

Hi, @anthonyabeo—I think that would be a good place to start! We would probably want to create a new, different primitive (to avoid conflicts with code that currently uses `std_slice`),...

Thank you! Just adding @Serene-Arc (who originally added this in #4949) to the thread here in case she would like to take a look.

Good point about the docs; I've added a note. Yes, a config option may be the only way here. That's what I was trying to avoid (it's such a hyper-specific...

Sure; it could definitely work! I'd suggest a name like `remove_top_dir` or similar, to convey exactly what it changes. But I don't object to such a config option!

Just checking: when you say `static_if_while` above, do you mean `static_if_with`?

Awesome!!! I love the idea of having this be as automated as possible. The high-level vision would be (a) move `release.py` into GitHub actions, so it's as easy as possible...

Agreed with @JOJ0 here: awesome that this works at all! IMO, we can move ahead with the simple "see elsewhere" changelogs on GitHub and revisit populating those in the future...

Yes, manual intervention to pick the version number seems perfectly good to me! FWIW, I find strict SemVer to be an awkward fit for end-user applications (like beets), as opposed...