Repository navigation
chore(deps): update Go dependencies - #151
Merged
Merged
Conversation
- Update direct and indirect Go dependencies to their latest versions - Refresh module checksums and remove unused requirements
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.
Summary
Update direct and indirect dependencies listed in go.mod to the latest versions for their current module paths, then tidy module metadata. Preserve Go 1.26.10 and the separately pinned go.tools.mod toolchain. All 22 retained requirements were checked individually with
go list -m -u; none reported an update on 2026-11-08.Related issues
N/A — no GitHub or Jira issue was supplied.
AI authorship
go.mod,go.sum.Change classification
Core — runtime dependencies affect the plugin's CI operations. Request two reviewers including the module owner.
Plan reference
Update existing module paths, resolve compatibility failures, validate, and open one focused dependency PR per repository. Cross-major import/API migrations are outside this update.
Verification
Checkout
chore/update-go-dependenciesinappleboy/drone-telegramand run from the repository root. Prerequisites: Go 1.26.10, a C compiler for race tests, Git, Make, and network access for module downloads. Local checks ran on macOS arm64; SSH/SCP tests ran in isolated Linux Alpine containers.go mod verifymake lintmake fmt-checkgo vet ./...go build -o /tmp/drone-telegram-review .git diff --checkandgit diff --cached --checkgo test -race -count=1 -v ./...Not run: seven live Telegram integration tests were skipped by existing guards because TELEGRAM_TOKEN and TELEGRAM_TO were absent. They require an authorized test bot/chat; the proxy test additionally requires SOCKS5. No real messages were sent.
Dependency freshness scenario
go mod edit -jsonand take eachRequire[].Path.go list -m -u <module-path>for each. Expected: no[new-version]suffix at the time of this update. Passed: every retained direct/indirect go.mod requirement was checked, including dependencies introduced during the update.This scope is the requirements in go.mod, not every upstream module's own test dependencies appearing in
go list -m all. Go 1.27 and remote CI jobs were not run locally; review GitHub checks before merging. Cleanup: remove the/tmp/review binary if created.Evidence
Web screenshots: N/A — no UI changes.
Performance: N/A — no performance claim; correctness and race checks are the relevant evidence.
Security check
No credentials or secrets are included in the diff. This dependency update is not a security audit. Review changed runtime libraries and any API adaptations before merging.
Risk and rollback
Dependency behavior may change despite unchanged module paths, especially v0 SDKs. Roll back by reverting this PR's commit and rebuilding with the prior module files; no persistent data migration is involved.
Reviewer guide
Review runtime dependency versions and any source/config changes first; go.sum is generated metadata. Two reviewers including the module owner should review the AI-authored change. Observe the stated integration-test gaps and wait for CI checks. No human line-by-line review has been performed.