@theokit/gateway-telegram 0.2.2 → 0.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +15 -0
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,20 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.2.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 7c422d9: A unit test no longer calls the real Telegram API.
|
|
8
|
+
|
|
9
|
+
`EC-I: connect() with bad token resolves to false` produced its failure by sending a bogus token to
|
|
10
|
+
`api.telegram.org` and waiting for the 401. That made the suite depend on the network: it failed
|
|
11
|
+
when the network was slow and passed when a proxy answered.
|
|
12
|
+
|
|
13
|
+
The contract worth covering is `init() rejects → connect() returns false, never throws`, and a bogus
|
|
14
|
+
token was only a way to produce the rejection. Producing it directly is the same assertion in
|
|
15
|
+
milliseconds, and covers the failures a bad token never reaches — a DNS failure, a 5xx, a socket
|
|
16
|
+
reset.
|
|
17
|
+
|
|
3
18
|
## 0.2.2
|
|
4
19
|
|
|
5
20
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@theokit/gateway-telegram",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.3",
|
|
4
4
|
"description": "Telegram (grammy) platform adapter for @theokit/gateway. ADR D171.",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"repository": {
|
|
@@ -44,7 +44,7 @@
|
|
|
44
44
|
"typescript": "^5.8.0",
|
|
45
45
|
"vitest": "^4.1.8",
|
|
46
46
|
"zod": "^4.0.0",
|
|
47
|
-
"@theokit/gateway": "0.
|
|
47
|
+
"@theokit/gateway": "0.8.0"
|
|
48
48
|
},
|
|
49
49
|
"publishConfig": {
|
|
50
50
|
"access": "public",
|