Repository navigation
Release 0.1.61: reject oversized Home Assistant image IDs - #64
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authenticated Home Assistant image requests with IDs above PostgreSQL's positive integer range returned HTTP 503. Validate the range before binding the image query so these requests return an empty, private/no-store HTTP 404 response.
Add a regression test that reproduces the prior 503, coverage for the largest valid ID, real PostgreSQL checks across supported upgrade fixtures, and production-browser HTTP checks. Existing authentication, camera scope, expiry, revocation, and read-only permissions remain enforced. No SQL migrations are added.
Prepare Community 0.1.61, User Guide 3.29, release notes, and current install/update documentation.
Validation: the regression reproduced HTTP 503 before the fix, then passed after it. All 1,375 local application tests passed (9 platform skips), along with typecheck, lint, production build, and Community sanitation. The five-fixture PostgreSQL upgrade matrix and production Edge browser/iframe tests passed. A freshly built Linux production image passed the full scoped Home Assistant HTTP security matrix and restart persistence checks, including the corrected 404 response. GitHub Linux checks, dependency security, and native Windows validation passed, including installer/update construction, CPU model probes, real PostgreSQL ingestion, and Linux-to-Windows restore. PR CI and all main-branch CI, security, and health checks passed. Exact-tag stable Windows packaging passed lifecycle, PostgreSQL, and cross-platform restore checks. All 3,361 update ZIP files match the verified package manifest; installer/update metadata, SQL sources, Linux scripts, PDF, and uploaded GitHub asset digests match the tagged release source. Published Community 0.1.61: https://github.com/prsmith777/ALPR-Database-Community/releases/tag/v0.1.61