Detailed Changes: v1.1.5…v1.1.6
Keep SMTP login values out of the logs
deps: Move to python-tools v2.0.0 and mysql-connector-python 26.7
deps: Updated several downstream dependencies, including mysql connector to solve reported vulnerabilities.
Bump pre-commit ruff hook to v0.17.2 to match uv.lock
deps: Bump mypy, cx-freeze, types-pywin32 and pre-commit
deps: Bump ruff to 0.17.2
deps: Bump uv to 0.13.5 and virtualenv to 21.14.13
deps: Pin python-tools v2.0.2, drop uv from dev extras, check mypy as win32
Detailed Changes: v1.1.4…v1.1.5
Detailed Changes: v1.1.3…v1.1.4
Make reportqueue importable as a package
Redact SQL/SMTP credentials from log output
Resolve ReportJob via a proper relative import
Strip CRLF from title/email_from to prevent header injection
ci: Bundle mysql.connector.plugins in frozen exe build
Detailed Changes: v1.1.2…v1.1.3
ci: Pin GitPython below 3.1.60 to fix semantic-release crash
mypy: Return bool from reportqueuehasreportidcolumn
Detect reportqueue.reportid at runtime instead of trusting PRODUCT
Adjust the ready jobs query to pass in null for the reportid column when product=itrackpro
Detailed Changes: v1.1.1…v1.1.2
Detailed Changes: v1.1.0…v1.1.1
Document silent/headless update behavior for ReportQueueSetup.exe
Minor linting fixes
Pre-populate installer config dialog from existing config.ini
Run VC++ redistributables fully quiet on silent installer runs
Skip ODBC and Report Commander sub-installers on silent install runs
Detailed Changes: v1.0.12…v1.1.0
All printers are now built into a map of outcomes so that a single operation is performed for each printer. This will avoid any 'noise' in the logs from them getting marked as online then offline again for any offline printers.
To avoid max packet size issues, if the number of printer names we're examining in a single pass is 1000 or more, just pull the entire printer list down.
When updating the list of outdated printers, all currently online printers will now be examined, instead of only unhidden ones. In addition, the loop that updates the reportqueueprinter status of datelastseen will attempt to only run an UPDATE if the row already existed, as using INSERT … ON DUPLICATE KEY UPDATE was causing AUTO_INCREMENT to grow very large.
Detailed Changes: v1.0.11…v1.0.12
Detailed Changes: v1.0.10…v1.0.11
Detailed Changes: v1.0.9…v1.0.10