switch from unmaintained pytest-watch to maintained pytest-watcher (this fix is untested because of my current containerization setup)
most of these changes are around sqlalchemy 1.x to sqlalchemy 2.x,
Things to check
For any logging statements, is there any chance that they could be logging sensitive data?
Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.
Security considerations
being up-to-date on dependencies reduces our exposure to known exploits. Getting sqlalchemy from 1.x to 2.x will also make it easier to stay up-to-date in the future
Changes proposed in this pull request:
pytest-watchto maintainedpytest-watcher(this fix is untested because of my current containerization setup)most of these changes are around sqlalchemy 1.x to sqlalchemy 2.x,
Things to check
INFOand debugging statements are written withlog.debugor similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.Security considerations
being up-to-date on dependencies reduces our exposure to known exploits. Getting sqlalchemy from 1.x to 2.x will also make it easier to stay up-to-date in the future