@jurislm/woodpecker-ci-plugin 2.0.4 → 2.0.6

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "woodpecker-ci",
3
- "version": "2.0.4",
3
+ "version": "2.0.6",
4
4
  "description": "Manage Woodpecker CI through agent tools.",
5
5
  "author": {
6
6
  "name": "JurisLM",
package/README.md CHANGED
@@ -85,9 +85,28 @@ server process environment. A desktop app launched by macOS does not read your
85
85
  interactive shell configuration. Check the MCP child process, not the terminal,
86
86
  when diagnosing missing credentials.
87
87
 
88
- If an existing `~/.zshenv` exports the token, this local Codex configuration
89
- launches the MCP server through zsh without copying the token into Codex config
90
- or this repository. Replace the example URL with your Woodpecker API URL:
88
+ The bundled `mcp.json` and `.mcp.json` intentionally have no `env` defaults:
89
+ this plugin does not select a Woodpecker instance or store a token. The host
90
+ must provide both variables to the actual server child process; exporting them
91
+ in the host environment alone does not establish that they were forwarded to
92
+ a plugin-bundled process. Do not add empty
93
+ values or `${WOODPECKER_URL}` / `${WOODPECKER_API_TOKEN}` references to these
94
+ files: Codex's portable MCP parser only expands `${PLUGIN_ROOT}` and
95
+ `${PLUGIN_DATA}`, so ordinary environment references remain literal strings.
96
+
97
+ The `[mcp_servers.woodpecker-ci]` entry in `~/.codex/config.toml` configures a
98
+ user MCP registration. Reading that entry with `codex mcp get` does not prove
99
+ that a plugin-provided server received the same environment. Verify an
100
+ authenticated read through the tools registered in the target task.
101
+
102
+ For authenticated Codex use, configure the user MCP registration below and
103
+ disable the bundled server. Plugin installation alone provides tool discovery,
104
+ not a verified credential route. If an existing `~/.zshenv` exports the token,
105
+ this local Codex configuration
106
+ launches a user MCP registration through zsh without copying the token into
107
+ Codex config or this repository. Replace the example URL with your Woodpecker
108
+ API URL. The plugin-scoped policy below disables the bundled server while
109
+ keeping the guidance skill enabled:
91
110
 
92
111
  ```toml
93
112
  [mcp_servers.woodpecker-ci]
@@ -95,6 +114,9 @@ command = "/bin/zsh"
95
114
  args = ["-c", "exec /usr/bin/python3 -c 'import os; keys=(\"HOME\",\"PATH\",\"TMPDIR\",\"WOODPECKER_API_TOKEN\"); env={k:os.environ[k] for k in keys if k in os.environ}; env[\"WOODPECKER_URL\"]=\"https://ci.example.com/api\"; path=env[\"HOME\"]+\"/.bun/bin/bunx\"; os.execve(path,[path,\"-y\",\"@jurislm/woodpecker-ci-plugin@latest\"],env)'"]
96
115
  required = true
97
116
  startup_timeout_sec = 30
117
+
118
+ [plugins."woodpecker-ci@woodpecker-ci-marketplace".mcp_servers.woodpecker-ci]
119
+ enabled = false
98
120
  ```
99
121
 
100
122
  This example needs `/usr/bin/python3` and Bun at `$HOME/.bun/bin/bunx`; replace either absolute path if needed. Python passes the token through `execve` environment, never a command argument.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jurislm/woodpecker-ci-plugin",
3
- "version": "2.0.4",
3
+ "version": "2.0.6",
4
4
  "description": "Local stdio MCP server for Woodpecker CI",
5
5
  "type": "module",
6
6
  "bin": {
package/plugin.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
3
3
  "name": "woodpecker-ci",
4
- "version": "2.0.4",
4
+ "version": "2.0.6",
5
5
  "description": "Manage Woodpecker CI through agent tools.",
6
6
  "author": {
7
7
  "name": "JurisLM",