Fix in-memory sourcemap filename - #2161

Will try to review the other fixes soon as well, thanks for digging into this! I will try to do separate bug fix releases off the branches if they can be rebased against the latest release (but I can try to do this myself of course).

Ah, I didn't realise the releases had diverged from master. I'd suggest we reconcile that first as I do think it is important to keep master and releases in sync as it makes debugging and bisecting workflows much easier having a linear history, at least within major ranges.

That means I do another feature release without basically any content except for the ESM alias and some minor other changes?

I do not see an issue with releasing from a branch (as I did for 0.58.1 and 0.58.2) as it gives us much more flexibility to merge bigger PRs into master without releasing them right away. I would immediately merge into master after the release.

Also since the history is fully preserved, bisecting should not be any more difficult.

I.e. this is about giving as flexibility and quicker response time and fixing regressions within a patch of the release they were introduced without introducing new functionality that may again introduce new bugs.

Otherwise I would not want to release this and try to review all the other fixes first which, at my current review speed, feels more like next week, so that this is a proper release and people do not ask "why was this and that not included!?"

Definitely understood release branches allow a quicker process if there is too much to check on master. This is what NodeJS does as well, but there are a few things just to consider from a process perspective with this stuff.

It would also help to hear what on the master branch isn't release and for what reasons we're holding them back? Do you see this as a temporary thing for now, or is this the sort release process you'd like to set up for Rollup to allow fast-merges on master? Worth having these discussions definitely.