discord-ops 0.14.1 → 0.14.2
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 +8 -0
- package/README.md +5 -5
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# discord-ops
|
|
2
2
|
|
|
3
|
+
## 0.14.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 9fb0d4b: Fix stale npx cache — use `discord-ops@latest` in MCP config
|
|
8
|
+
|
|
9
|
+
Without `@latest`, npx may serve a cached older version indefinitely, causing MCP clients to run stale code even after new releases are published. All MCP config examples in the README updated to use `discord-ops@latest`.
|
|
10
|
+
|
|
3
11
|
## 0.14.1
|
|
4
12
|
|
|
5
13
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -51,14 +51,14 @@ discord-ops serve --port 3000
|
|
|
51
51
|
|
|
52
52
|
## Claude Code Integration
|
|
53
53
|
|
|
54
|
-
Add to your project's `.mcp.json`. Use `npx`
|
|
54
|
+
Add to your project's `.mcp.json`. Use `npx` with `@latest` so every session automatically uses the latest published release — without it, npx may serve a stale cached version indefinitely:
|
|
55
55
|
|
|
56
56
|
```json
|
|
57
57
|
{
|
|
58
58
|
"mcpServers": {
|
|
59
59
|
"discord-ops": {
|
|
60
60
|
"command": "npx",
|
|
61
|
-
"args": ["-y", "discord-ops"],
|
|
61
|
+
"args": ["-y", "discord-ops@latest"],
|
|
62
62
|
"env": {
|
|
63
63
|
"DISCORD_TOKEN": "${DISCORD_TOKEN}"
|
|
64
64
|
}
|
|
@@ -78,7 +78,7 @@ When each project has its own bot, pass all token env vars and let `~/.discord-o
|
|
|
78
78
|
"mcpServers": {
|
|
79
79
|
"discord-ops": {
|
|
80
80
|
"command": "npx",
|
|
81
|
-
"args": ["-y", "discord-ops"],
|
|
81
|
+
"args": ["-y", "discord-ops@latest"],
|
|
82
82
|
"env": {
|
|
83
83
|
"ORG_A_DISCORD_TOKEN": "${ORG_A_DISCORD_TOKEN}",
|
|
84
84
|
"ORG_B_DISCORD_TOKEN": "${ORG_B_DISCORD_TOKEN}"
|
|
@@ -99,7 +99,7 @@ If all your projects share one bot, just pass that token:
|
|
|
99
99
|
"mcpServers": {
|
|
100
100
|
"discord-ops": {
|
|
101
101
|
"command": "npx",
|
|
102
|
-
"args": ["-y", "discord-ops"],
|
|
102
|
+
"args": ["-y", "discord-ops@latest"],
|
|
103
103
|
"env": {
|
|
104
104
|
"DISCORD_TOKEN": "${DISCORD_TOKEN}"
|
|
105
105
|
}
|
|
@@ -117,7 +117,7 @@ If another tool already claims `DISCORD_TOKEN`, use `DISCORD_OPS_TOKEN_ENV` to p
|
|
|
117
117
|
"mcpServers": {
|
|
118
118
|
"discord-ops": {
|
|
119
119
|
"command": "npx",
|
|
120
|
-
"args": ["-y", "discord-ops"],
|
|
120
|
+
"args": ["-y", "discord-ops@latest"],
|
|
121
121
|
"env": {
|
|
122
122
|
"DISCORD_OPS_TOKEN_ENV": "MY_BOT_TOKEN",
|
|
123
123
|
"MY_BOT_TOKEN": "${MY_BOT_TOKEN}"
|