You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(channel): default insecure to false, warn on token+plaintext
- Flips `ClientOptions.insecure` default to `false` so TLS is used out of the box; plaintext requires explicit `insecure: true`.
- Logs a warning when `insecure: true` is combined with a bearer token, since the token would be transmitted in cleartext.
- Adds test coverage for the warning path and documents the breaking change in CHANGELOG.
Closes#43
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Copy file name to clipboardExpand all lines: CHANGELOG.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,16 @@ All notable changes to this project will be documented in this file.
4
4
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
6
6
7
+
## [Unreleased]
8
+
9
+
### Changed
10
+
11
+
-**Breaking:**`ClientOptions.insecure` now defaults to `false` (TLS). Previously defaulted to `true` (plaintext). Connections to TLS endpoints now work correctly out of the box; plaintext requires explicit `insecure: true`.
12
+
13
+
### Added
14
+
15
+
- Warning logged when `insecure: true` is set alongside a bearer token, since the token would be transmitted in cleartext.
0 commit comments