Add ARM v7 architecture to Docker images

[jpauwels]

User description

Simply includes ARMv7 in the Docker image build on GitHub. I've been running this without problems on my device for months with multiple versions. It would be good to be able to pull from the official image.

---

PR Type

Enhancement

---

Description

• Add ARM v7 (32-bit) architecture support to Docker image builds

• Extends platform matrix from amd64 and arm64 to include linux/arm/v7

• Enables official Docker image availability for ARM v7 devices

---

Diagram Walkthrough

flowchart LR
  A["Docker Build Platforms"] -->|Previously| B["linux/amd64, linux/arm64"]
  A -->|Now| C["linux/amd64, linux/arm64, linux/arm/v7"]
  C -->|Enables| D["ARM v7 Device Support"]

Loading

File Walkthrough

	Relevant files
Configuration changes	docker-publish.yml Add ARM v7 platform to Docker build matrix                              .github/workflows/docker-publish.yml Updated Docker build platforms configuration to include linux/arm/v7 Extended multi-architecture support from 2 platforms to 3 platforms Maintains existing amd64 and arm64 architecture builds +1/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

No code suggestions found for the PR.

[sstidl]

@jpauwels thanks for the contribution