Repository navigation
Release 1.10.0: fix proxy geodata validation and refresh security dependencies - #46
Merged
Merged
Conversation
agentram
force-pushed
the
fix/proxy-geodata-validation
branch
from
October 6, 2026 14:28
dfba96d to
654ad5f
Compare
agentram
force-pushed
the
fix/proxy-geodata-validation
branch
from
October 6, 2026 15:03
fb70a54 to
cd34310
Compare
2 tasks done
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.
Release 1.10.0 fixes #44: local Xray validation now uses the CLI user's UID/GID so it can read owner-only geodata. File permissions and read-only mounts are preserved. Temporary configs are private and removed after validation; permission errors now identify filesystem access as the cause.
Includes Dependabot #39, #41 and #43, Go 1.27.1, updated dependencies, pinned Actions and runtime images. Xray remains on 26.7.28; gRPC remains on patched 1.83.2 because GO-2026-6443 lists 1.84.0 as affected.
Validation: unit tests, race, vet, lint, security scans and Linux Docker regression passed. The regression reproduces the original permission failure and verifies the fix with source files still at 0600. VERSION, CHANGELOG and README are updated; operator documentation includes a short verification command.