Skip to content

[settings] add gateway settings support#206

Open
capcom6 wants to merge 3 commits intomasterfrom
settings/add-gateway-settings-support
Open

[settings] add gateway settings support#206
capcom6 wants to merge 3 commits intomasterfrom
settings/add-gateway-settings-support

Conversation

@capcom6
Copy link
Member

@capcom6 capcom6 commented Feb 17, 2026

Summary by CodeRabbit

  • New Features

    • Added a notification channel configuration option for gateway settings.
  • Chores

    • Updated SMS gateway client library to a newer version.
    • Updated test deployment images and normalized compose restart syntax.

@coderabbitai
Copy link

coderabbitai bot commented Feb 17, 2026

No actionable comments were generated in the recent review. 🎉


Walkthrough

Updated a client-go dependency, added a new settings field (gateway.notification_channel) to validation maps, added nolint directives in two internal packages, and adjusted service image tags and restart syntax in the e2e docker-compose file.

Changes

Cohort / File(s) Summary
Dependency Update
go.mod
Bumped github.com/android-sms-gateway/client-go from v1.9.6-... to v1.10.1-.... No other dependency edits.
Settings Validation Rules
internal/sms-gateway/modules/settings/utils.go
Added gateway.notification_channel as a string entry to both internal rules and rulesPublic maps (validation/merge metadata).
Linter Directives
internal/sms-gateway/modules/metrics/module.go, internal/version/version.go
Inserted //nolint:revive to ignore package-name lint warnings; no functional changes.
E2E Docker Compose
test/e2e/docker-compose.yml
Updated service image references to explicit tags (android-sms-gateway/server:public and :private) and normalized restart policy quoting/formatting.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title '[settings] add gateway settings support' clearly refers to the main change in the PR which adds gateway.notification_channel to the settings validation rules, supporting new gateway settings functionality.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
go.mod (1)

7-7: Pseudo-version dependency — consider pinning to a tagged release before merging.

v1.10.1-0.20260217004820-83d276545735 is a pseudo-version pointing to an unreleased commit. This is fine during development, but ideally this should be updated to a proper tagged release (e.g., v1.10.1) before shipping, to ensure reproducibility and clearer dependency tracking.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@go.mod` at line 7, The go.mod entry for module
github.com/android-sms-gateway/client-go currently uses a pseudo-version
(v1.10.1-0.20260217004820-83d276545735); replace that pseudo-version with a
proper tagged release (for example v1.10.1 or the latest stable tag) in go.mod
and then refresh the module metadata (update go.sum / tidy modules) so the
project references a reproducible, tagged dependency.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@go.mod`:
- Line 7: The go.mod entry for module github.com/android-sms-gateway/client-go
currently uses a pseudo-version (v1.10.1-0.20260217004820-83d276545735); replace
that pseudo-version with a proper tagged release (for example v1.10.1 or the
latest stable tag) in go.mod and then refresh the module metadata (update go.sum
/ tidy modules) so the project references a reproducible, tagged dependency.

@github-actions
Copy link

🤖 Pull request artifacts

Platform File
🐳 Docker GitHub Container Registry
🍎 Darwin arm64 server_Darwin_arm64.tar.gz
🍎 Darwin x86_64 server_Darwin_x86_64.tar.gz
🐧 Linux arm64 server_Linux_arm64.tar.gz
🐧 Linux i386 server_Linux_i386.tar.gz
🐧 Linux x86_64 server_Linux_x86_64.tar.gz
🪟 Windows arm64 server_Windows_arm64.zip
🪟 Windows i386 server_Windows_i386.zip
🪟 Windows x86_64 server_Windows_x86_64.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant