Robert

It's a `pip` issue, actually. `pipx` has nothing to do with these files. This problem also occurs if a user manually installs `ranger` via pip into a `venv` that resides...

I think this is an okay quick fix (potentially for the next release so we're not blocked by this?). What I don't like about this is that the release artifacts...

> I understand. What alternative do you suggest? My idea would be to transfer the release-related jobs from the `tests` workflow to a new `release` workflow with a `workflow_dispatch` event,...

> Where would you specify the version to release in a workflow_dispatch? From one of our deployment workflows at work: 

> There is one complication which requires a bit more discussion. If we want to stick with opening a pull request every release to update the changelog, how can the...

Will you work on this soon @chrysle? If not I'd suggest we create a release soon with the current setup. There's a pretty good amount of bug fixes and new...

While your current solution works, what about giving this changelog PR a specific label and run the release via pipeline when a PR with that label is merged? Label is...

> This isn't quite that easy, as it turns out.. After trial and error for a while I finally managed to get my workflow to trigger on a merged pull...

Hello @pure-blue, thanks for raising this. Your brew upgrade issue might be fixable with some of the solutions mentioned [here](https://github.com/Homebrew/brew/issues/14516). Could you try installing pipx via `pip install --user pipx`...

Will close this as we don't seem to be getting more information and @whchi has provided a potential fix.