discord-ops 0.15.0 → 0.16.0
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 +18 -0
- package/README.md +10 -9
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,23 @@
|
|
|
1
1
|
# discord-ops
|
|
2
2
|
|
|
3
|
+
## 0.16.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- b42d0fe: feat: add `run` CLI subcommand and inline JSON support for `DISCORD_OPS_CONFIG`
|
|
8
|
+
- `discord-ops run <tool> --args '<json>'` — execute any tool directly from shell, no AI/MCP required. Supports the full tool suite including `send_template`, `send_message`, `send_embed`, and all 46 tools.
|
|
9
|
+
- `DISCORD_OPS_CONFIG` now accepts an inline JSON string in addition to a file path — if the value starts with `{` it is parsed directly. Eliminates the need to write config files in CI environments.
|
|
10
|
+
- `release.yml` GitHub Actions workflow — automatically posts a rich Discord release notification to `#releases` after every successful npm publish via changesets.
|
|
11
|
+
- README — new CLI `run` docs with examples, CI/CD integration section with config shape, GitHub Actions example, and updated `DISCORD_OPS_CONFIG` env var description.
|
|
12
|
+
|
|
13
|
+
### Patch Changes
|
|
14
|
+
|
|
15
|
+
- b42d0fe: fix: add "alert" to NotificationType enum — global config with alert in notify_owners_on caused config parse failure and MCP startup crash
|
|
16
|
+
- b42d0fe: fix: clean up changelog formatting in Discord release notifications — section headers now render as bold text, commit hashes stripped from bullet lines
|
|
17
|
+
- b42d0fe: Fix stale npx cache — use `discord-ops@latest` in MCP config
|
|
18
|
+
|
|
19
|
+
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`.
|
|
20
|
+
|
|
3
21
|
## 0.15.0
|
|
4
22
|
|
|
5
23
|
### Minor Changes
|
package/README.md
CHANGED
|
@@ -466,16 +466,16 @@ Any tool name accepted by the MCP server works here — `send_message`, `send_te
|
|
|
466
466
|
|
|
467
467
|
## Environment Variables
|
|
468
468
|
|
|
469
|
-
| Variable | Required | Description
|
|
470
|
-
| ------------------------ | -------- |
|
|
471
|
-
| `DISCORD_TOKEN` | No\* | Default Discord bot token (\*required unless all projects have `token_env`)
|
|
472
|
-
| `DISCORD_OPS_TOKEN_ENV` | No | Override which env var holds the default token (default: `DISCORD_TOKEN`)
|
|
473
|
-
| `<PROJECT>_TOKEN` | No | Per-project bot tokens (configured via `token_env` in project config)
|
|
469
|
+
| Variable | Required | Description |
|
|
470
|
+
| ------------------------ | -------- | ---------------------------------------------------------------------------------- |
|
|
471
|
+
| `DISCORD_TOKEN` | No\* | Default Discord bot token (\*required unless all projects have `token_env`) |
|
|
472
|
+
| `DISCORD_OPS_TOKEN_ENV` | No | Override which env var holds the default token (default: `DISCORD_TOKEN`) |
|
|
473
|
+
| `<PROJECT>_TOKEN` | No | Per-project bot tokens (configured via `token_env` in project config) |
|
|
474
474
|
| `DISCORD_OPS_CONFIG` | No | Path to global config file, or inline JSON string (default: `~/.discord-ops.json`) |
|
|
475
|
-
| `DISCORD_OPS_LOG_LEVEL` | No | `debug`, `info`, `warn`, `error` (default: `info`)
|
|
476
|
-
| `DISCORD_OPS_DRY_RUN` | No | Enable dry-run mode (any truthy value)
|
|
477
|
-
| `DRY_RUN` | No | Enable dry-run mode (any truthy value, alias)
|
|
478
|
-
| `DISCORD_OPS_HTTP_TOKEN` | No | Bearer token for HTTP transport authentication (strongly recommended)
|
|
475
|
+
| `DISCORD_OPS_LOG_LEVEL` | No | `debug`, `info`, `warn`, `error` (default: `info`) |
|
|
476
|
+
| `DISCORD_OPS_DRY_RUN` | No | Enable dry-run mode (any truthy value) |
|
|
477
|
+
| `DRY_RUN` | No | Enable dry-run mode (any truthy value, alias) |
|
|
478
|
+
| `DISCORD_OPS_HTTP_TOKEN` | No | Bearer token for HTTP transport authentication (strongly recommended) |
|
|
479
479
|
|
|
480
480
|
### Token resolution
|
|
481
481
|
|
|
@@ -517,6 +517,7 @@ In CI you typically have one bot token and one project. Pass a minimal config as
|
|
|
517
517
|
### GitHub Actions example
|
|
518
518
|
|
|
519
519
|
Store two secrets in your repo:
|
|
520
|
+
|
|
520
521
|
- `BOOKED_DISCORD_BOT_TOKEN` — your bot token
|
|
521
522
|
- `DISCORD_OPS_CONFIG` — the config JSON **minified to a single line** (multiline strings break GitHub secrets)
|
|
522
523
|
|