Hello! This issue is known, it should not be fixed in the runner-images anyhow but rather symlinks must be fixed in the actions/setup-python repository in the issue you mentioned (#11545) cc @dmitry-shibanov for awareness.

That's nonsense. Not everyone uses actions/setup-python. And you've fixed it in this repository before: 7ff71c8 -- and you've carried that support through a number of python releases.

This isn't just a problem w/ python, it's also a problem w/ go.

This is a fundamentally broken image, you're shipping a broken brew which when asked to upgrade dies.

https://github.com/jsoref/macos-brew-python/actions/runs/5252745538/jobs/9489182502#step:3:522

Here's the most recent thing I tripped on, note again that there's no actions/setup-python and there should be no requirement that people use that or some hypothetical version that has to be adapted to work around a bug in the basic runner image:
https://github.com/check-spelling/mgconsole/actions/runs/5260558139/workflow

Run brew update
...
==> Running `brew cleanup python@3.10`...
Removing: /usr/local/Cellar/python@3.10/3.10.11... (3,122 files, 56.9MB)
Removing: /Users/runner/Library/Caches/Homebrew/python@3.10--3.10.11... (14.6MB)
==> Upgrading python@3.11
  3.11.3 -> 3.11.4 

==> Pouring python@3.11--3.11.4.monterey.bottle.tar.gz
Error: The `brew link` step did not complete successfully
The formula built, but is not symlinked into /usr/local
Could not symlink bin/2to3
Target /usr/local/bin/2to3
already exists. You may want to remove it:
  rm '/usr/local/bin/2to3'

This is a fundamentally broken image, you're shipping a broken brew which when asked to upgrade dies.

I can confirm this. If one pushes a GitHub Actions config that just runs brew update, the Action fails.