Bump mypy from 1.10.1 to 1.13.0 in /backend

[dependabot]

Bumps mypy from 1.10.1 to 1.13.0.

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next release

Mypy 1.13

We’ve just uploaded mypy 1.13 to the Python Package Index (PyPI). Mypy is a static type checker for Python. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Note that unlike typical releases, Mypy 1.13 does not have any changes to type checking semantics from 1.12.1.

Improved performance

Mypy 1.13 contains several performance improvements. Users can expect mypy to be 5-20% faster. In environments with long search paths (such as environments using many editable installs), mypy can be significantly faster, e.g. 2.2x faster in the use case targeted by these improvements.

Mypy 1.13 allows use of the orjson library for handling the cache instead of the stdlib json, for improved performance. You can ensure the presence of orjson using the faster-cache extra:

python3 -m pip install -U mypy[faster-cache]

Mypy may depend on orjson by default in the future.

These improvements were contributed by Shantanu.

List of changes:

• Significantly speed up file handling error paths (Shantanu, PR 17920)
• Use fast path in modulefinder more often (Shantanu, PR 17950)
• Let mypyc optimise os.path.join (Shantanu, PR 17949)
• Make is_sub_path faster (Shantanu, PR 17962)
• Speed up stubs suggestions (Shantanu, PR 17965)
• Use sha1 for hashing (Shantanu, PR 17953)
• Use orjson instead of json, when available (Shantanu, PR 17955)
• Add faster-cache extra, test in CI (Shantanu, PR 17978)

Acknowledgements

Thanks to all mypy contributors who contributed to this release:

• Shantanu Jain
• Jukka Lehtosalo

Mypy 1.12

We’ve just uploaded mypy 1.12 to the Python Package Index (PyPI). Mypy is a static type

... (truncated)

Commits

• eb31034 Bump version to 1.13.0
• 2eeb588 Update changelog for 1.12.1 (#17999)
• bc0386b Changelog for 1.13 (#18000)
• 5c4d2db Add faster-cache extra, test in CI (#17978)
• 854ad18 Make is_sub_path faster (#17962)
• 50aa4ca Speed up stubs suggestions (#17965)
• 7c27808 Use orjson instead of json, when available (#17955)
• 2cd2406 Use fast path in modulefinder more often (#17950)
• e20aaee Let mypyc optimise os.path.join (#17949)
• 159974c Use sha1 for hashing (#17953)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
capy-life	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Oct 28, 2024 5:29pm

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
pypi/opentelemetry-util-http@0.41b0	environment, eval, network	0	31.5 kB	LeightonC, opentelemetry
pypi/packaging@23.1	environment, eval, filesystem, shell	0	2.34 MB	brettcannon, dstufft, pf_moore, ...1 more
pypi/pathspec@0.11.1	filesystem	0	186 kB	cpburnz
pypi/picologging@0.9.2	filesystem, network, unsafe	0	548 kB	anthonypjshaw, microsoft

🚮 Removed packages: pypi/mypy@1.10.1

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Shell access	pypi/packaging@23.1	Location: Package overview	backend/poetry.lock	🚫
Shell access	pypi/packaging@23.1	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/opentelemetry-util-http@0.41b0	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/opentelemetry-util-http@0.41b0	Location: Package overview	backend/poetry.lock	🚫
AI-detected potential code anomaly	pypi/picologging@0.9.2	Notes: The code contains multiple potential security risks, including unauthorized file writes, command injection, information leakage, and code injection. It should be reviewed and modified to ensure proper input validation, sanitization, and secure handling of user input. The presence of 'eval' raises concerns about the safety and security of the code. Confidence: 0.80 Severity: 0.70	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫
Network access	pypi/picologging@0.9.2	Location: Package overview	backend/poetry.lock	🚫

View full report↗︎

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is an AI-detected potential code anomaly?

AI has identified unusual behaviors that may pose a security risk.

An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore pypi/packaging@23.1
• @SocketSecurity ignore pypi/opentelemetry-util-http@0.41b0
• @SocketSecurity ignore pypi/picologging@0.9.2