This seems like a new false positive:

/home/runner/work/typeshed/typeshed/stubs/icalendar/icalendar/__init__.pyi
  /home/runner/work/typeshed/typeshed/stubs/icalendar/icalendar/__init__.pyi:48:7 - error: "version" is declared as Final and cannot be reassigned (reportGeneralTypeIssues)
/home/runner/work/typeshed/typeshed/stubs/requests/requests/__init__.pyi
  /home/runner/work/typeshed/typeshed/stubs/requests/requests/__init__.pyi:2:7 - error: "__version__" is declared as Final and cannot be reassigned (reportGeneralTypeIssues)

Looking at the icalendar one:

• icalendar/version.pyi has __version__: Final[str]
• icalendar/__init__.pyi has from . version import __version__ as __version__
• pyright complains about reassignment of the Final name

Will see if I can reproduce this in a self-contained package and then report to pyright.

I think the problem are the following (simplified) statements:

from .version import version as version  # icalender
from .__version__ import __version__ as __version__  # requests

Technically speaking we're defining version twice in icalendar: The Final import from .version and then .version implicitly from the import. Still, considering that implicit imports are not supported in stub files (and are honestly an unfortunate design quirk at runtime), I'd rather wish we don't have to change our stubs.

microsoft/pyright#9992

New error:

  /home/runner/work/typeshed/typeshed/stdlib/@tests/test_cases/builtins/check_pow.py:50:13 - error: "assert_type" mismatch: expected "Fraction" but received 

(And a new setuptools stubtest error.)