Backport Trixie changes to Community (#1953)

Resolves tiny-pilot/tinypilot-pro#1765

This PR mostly backports our recent migration to Trixie, from Pro into
Community, and any lingering changes that should have been backported.

### Notes

- I followed a mostly manual process of:
  1. Copying the Pro `.git` directory in the Community repo
  1. Using VSCode to accept/reject Pro changes into the Community repo
  1. Restoring the Community `.git` directory
  1. Using AI to spot check the changes
  1. Commit and push changes
  1. Installing the bundle on a Voyager 2a device
     - keyboard, video, mouse, and audio streaming works
- Most of the file changes came from the updated prettier version
reformatting JS files (i.e., adding trailing `,`):
   - tiny-pilot/tinypilot-pro#1883
- As noted in the parent issue, this PR also removes all static IP
scripts:
-
tiny-pilot/tinypilot-pro#1765 (comment)
- Merging this PR should generate an empty diff when merging back into
Pro

<a data-ca-tag
href="https://codeapprove.com/pr/tiny-pilot/tinypilot/1953"><img
src="https://codeapprove.com/external/github-tag-allbg.png" alt="Review
on CodeApprove" /></a>

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: jdeanwallace

.circleci/config.yml

@@ -5,13 +5,16 @@ executors:
       - image: cimg/base:2024.02
   ubuntu-machine:
     machine:
-      image: ubuntu-2204:2024.01.2
+      image: ubuntu-2404:2025.09.1
+  debian:
+    docker:
+      - image: debian:trixie-20260421-slim
   python:
     docker:
-      - image: cimg/python:3.9.17
+      - image: cimg/python:3.13.12
   node:
     docker:
-      - image: cimg/node:18.16.1
+      - image: cimg/node:24.13.1
 commands:
   check_project_env_vars:
     steps:
@@ -182,12 +185,12 @@ jobs:
     docker:
       # To run tests against the dev server, Playwright needs a CircleCI image
       # with Python, Node, and a browser. While the check_python and
-      # check_javascript steps use python-3.9.17 and node-18.16.1 respectively,
+      # check_javascript steps use python-3.13.12 and node-24.13.1 respectively,
       # the CircleCI image with *both* python and node in the closest versions
-      # is python:3.9.17-browsers. It has python-3.9.17 and node-18.16.0.
+      # is python:3.13.12-browsers. It has python-3.13.12 and node-24.13.0.
       #
       # See: https://circleci.com/developer/images/image/cimg/python#tagging-scheme
-      - image: cimg/python:3.9.17-browsers
+      - image: cimg/python:3.13.12-browsers
     environment:
       NODE_ENV: development
     steps:
@@ -228,7 +231,7 @@ jobs:
           name: Build Debian package
           command: |
             ./dev-scripts/build-debian-pkg \
-              --build-targets linux/arm/v7
+              --build-targets linux/arm64
       - run:
           name: Print Debian package contents
           command: dpkg --contents debian-pkg/releases/tinypilot*.deb
@@ -237,17 +240,20 @@ jobs:
           paths:
             - "*.deb"
   check_debian_package:
-    executor: ubuntu
+    executor: debian
     steps:
       - checkout
       - attach_workspace:
           at: ./
-      - run:
-          name: Update apt packages
-          command: sudo apt-get update
       - run:
           name: Install lintian
-          command: sudo apt-get install -y lintian=2.114.0ubuntu1
+          command: |
+            set -eux
+            # Add a snapshot source so that the lintian version can be pinned.
+            echo 'deb https://snapshot.debian.org/archive/debian/20250329T031528Z/ trixie main' \
+              > /etc/apt/sources.list.d/snapshot.list
+            apt-get update
+            apt-get install --yes lintian=2.122.0
       - run:
           name: Print lintian version
           command: lintian --version

.dockerignore

@@ -1,6 +1,7 @@
 # Auto-generated files/folders.
 **/__pycache__
 **/*.py[cod]
+**/venv/
 
 # Test files.
 **/*_test.py

.eslintrc.cjs

@@ -14,10 +14,6 @@ extended-description-is-empty
 # https://github.com/tiny-pilot/tinypilot/issues/1196
 recursive-privilege-change
 
-# Our copyright notice isn't in the correct format.
-# https://lintian.debian.org/tags/copyright-without-copyright-notice
-copyright-without-copyright-notice
-
 # Apparently the Target and WantedBy fields we specify are atypical, so suppress
 # warnings until we can find the right field values.
 # https://github.com/tiny-pilot/tinypilot/issues/1207

.lintianignore

@@ -112,7 +112,7 @@ docstring-min-length=60
 [STRING]
 check-quote-consistency=no
 
-[ELIF]
+[REFACTORING]
 
 # Maximum number of nested blocks for function / method body
 max-nested-blocks=5
@@ -177,6 +177,10 @@ init-import=no
 # not used).
 dummy-variables-rgx=(_+[a-zA-Z0-9_]*?$)|dummy
 
+# Argument names that match this expression will be ignored. Default to name
+# with leading underscore
+ignored-argument-names=_.*
+
 [CLASSES]
 
 # List of method names used to declare (i.e. assign) instance attributes.
@@ -197,10 +201,6 @@ exclude-protected=_asdict,_fields,_replace,_source,_make
 # Maximum number of arguments for function / method
 max-args=10
 
-# Argument names that match this expression will be ignored. Default to name
-# with leading underscore
-ignored-argument-names=_.*
-
 # Maximum number of locals for function / method body
 max-locals=30
 
@@ -236,4 +236,4 @@ analyse-fallback-blocks=no
 
 # Exceptions that will emit a warning when being caught. Defaults to
 # "Exception"
-overgeneral-exceptions=Exception
+overgeneral-exceptions=builtins.Exception

.pylintrc

@@ -1,7 +1,7 @@
 src = ["app"]
 
-# Assume Python 3.9.
-target-version = "py39"
+# Assume Python 3.13.
+target-version = "py313"
 
 [lint]
 select = [

.ruff.toml

@@ -8,8 +8,8 @@ The steps below show you how to quickly set up a development environment for Tin
 
 ### Requirements
 
-- Python 3.9 or higher
-- Node.js 18.16.1 or higher
+- Python 3.13 or higher
+- Node.js 24.13.1 or higher
 - [shellcheck](https://github.com/koalaman/shellcheck#installing)
 - [bats](https://bats-core.readthedocs.io/en/stable/installation.html)
 - Docker 20.10.x or higher
@@ -146,7 +146,18 @@ By the way, for flashing the ready-made disk images of TinyPilot Pro, we recomme
 
 ### Initialize system on Voyager hardware
 
-If you want to initialize a new system on Voyager hardware, you first need to set some configuration in place to make TinyPilot work with Voyager’s video capture chip.
+If you want to initialize a new system on Voyager hardware using the bundle installer, you first need to set some configuration in place so that it knows what hardware it runs on.
+
+#### Voyager 3
+
+```bash
+# Create hardware/product identifiers.
+mkdir -p /etc/tinypilot
+echo 'voyager' > /etc/tinypilot/product-family
+echo '3' > /etc/tinypilot/product-model
+```
+
+#### Voyager 2 / 2a
 
 ```bash
 # Create tinypilot system user and group.
@@ -159,7 +170,7 @@ adduser \
     tinypilot
 
 # Add uStreamer configuration.
-echo "dtoverlay=tc358743" | sudo tee --append /boot/config.txt
+echo "dtoverlay=tc358743" | sudo tee --append /boot/firmware/config.txt
 ```
 
 ### Install from source
@@ -204,7 +215,7 @@ curl \
 
 ### Build a uStreamer Debian package
 
-CircleCI builds the uStreamer Debian package for the `armhf` architecture on every commit to the [`ustreamer-debian` repo](https://github.com/tiny-pilot/ustreamer-debian), which is stored as a CircleCI artifact.
+CircleCI builds the uStreamer Debian package for the `arm64` architecture on every commit to the [`ustreamer-debian` repo](https://github.com/tiny-pilot/ustreamer-debian), which is stored as a CircleCI artifact.
 
 Follow these steps:
 
@@ -214,16 +225,14 @@ Follow these steps:
 1. Click the `build_debian_package` job.
    - If the [`build_debian_package` CircleCI job](https://github.com/tiny-pilot/ustreamer-debian/blob/2ace4a1d22a3c9108f5285e3dff0290c60e5b1cf/.circleci/config.yml#L25) fails for some reason, you can manually debug the code in CircleCI by clicking "rerun job with SSH" in the CircleCI dashboard and following their SSH instructions. Remember to cancel the CircleCI job once you're done debugging, in order to reduce CI costs.
 1. When the job completes, go to the "Artifacts" tab of the `build_debian_package` job on CircleCI to find the uStreamer Debian packages.
-
-   - We use `armhf`-based builds on physical devices and for testing in CircleCI.
+   - We use `arm64`-based builds on physical devices and for testing in CircleCI.
    - [Docker platform names don't match Debian architecture names:](https://github.com/tiny-pilot/ustreamer-debian/blob/2ace4a1d22a3c9108f5285e3dff0290c60e5b1cf/Dockerfile#L46C1-L48)
 
      > Docker's platform names don't match Debian's platform names, so we translate
      > the platform name from the Docker version to the Debian version...
 
      Which means that when Docker's target platform is:
-
-     - `linux/arm/v7`, CircleCI creates a `armhf` Debian package
+     - `linux/arm64`, CircleCI creates a `arm64` Debian package
 
 ### Install a uStreamer Debian package
 
@@ -280,18 +289,18 @@ We don't use any Python package management tools because we want to limit comple
 
 We don't track indirect dependencies for our dev dependencies (in `requirements_dev.txt`), so you can update those by simply changing the version number for any package.
 
-### Building an ARMv7 bundle on a dev system
+### Building an ARM64 bundle on a dev system
 
 To build a TinyPilot install bundle on your dev system, you first need to configure a Docker builder for multi-architecture builds using QEMU. You only need to perform this step once per system:
 
 ```bash
 ./dev-scripts/enable-multiarch-docker
 ```
 
-Once your dev system is configured for multi-architecture Docker builds, you can build install ARMv7 TinyPilot bundles with the following commands:
+Once your dev system is configured for multi-architecture Docker builds, you can build install ARM64 TinyPilot bundles with the following commands:
 
 ```bash
-TARGET_PLATFORM='linux/arm/v7'
+TARGET_PLATFORM='linux/arm64'
 
 (rm debian-pkg/releases/tinypilot*.deb || true) && \
   ./dev-scripts/build-debian-pkg --build-targets "${TARGET_PLATFORM}" && \
@@ -538,10 +547,10 @@ const confirmCreateButton = document.querySelector("#confirm-create-btn");
 const confirmDeleteButton = document.querySelector("#confirm-delete-btn");
 
 const confirmCreateButtonContainer = document.querySelector(
-  "#create .btn-container"
+  "#create .btn-container",
 );
 const confirmDeleteButtonContainer = document.querySelector(
-  "#delete .btn-container"
+  "#delete .btn-container",
 );
 ```