-
-
Notifications
You must be signed in to change notification settings - Fork 23
4.5.0 #712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.5.0 #712
Changes from all commits
63845bb
5977896
b05060a
f116a68
f7536a6
ce444a4
f774e65
ce0c28b
3571ca1
b8e43c6
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| '@walkeros/mcp': patch | ||
| '@walkeros/mcp-source-browser': patch | ||
| '@walkeros/cli': patch | ||
| '@walkeros/transformer-validate': patch | ||
| '@walkeros/server-transformer-fingerprint': patch | ||
| --- | ||
|
|
||
| Add package READMEs and npm keywords. The MCP packages now ship install | ||
| instructions for Claude Code, Cursor, and VS Code plus MCP registry metadata | ||
| (mcpName). |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,7 @@ | ||
| --- | ||
| '@walkeros/cli': patch | ||
| --- | ||
|
|
||
| A `path` entry in `config.bundle.packages` now counts as the package pin, so | ||
| bundling and setup use the local package instead of failing when steps still | ||
| declare conflicting inline versions of it. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| --- | ||
| '@walkeros/cli': minor | ||
| --- | ||
|
|
||
| `walkeros setup` now resolves a component's package the same way | ||
| `walkeros bundle` does: the flow's pinned version is downloaded from the | ||
| registry (sharing the bundle cache) and imported from there. Setup works via npx | ||
| without a local install; `path:` packages are supported for local development. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,13 @@ | ||
| --- | ||
| '@walkeros/server-source-express': minor | ||
| '@walkeros/core': minor | ||
| --- | ||
|
|
||
| The Express source's `async` option now resolves per HTTP method: a boolean | ||
| still applies to the whole source, and a record like `{ "GET": true }` or | ||
| `{ "POST": false }` overrides one method while the other keeps its default. The | ||
| default changed: GET is now synchronous, so a step such as the file transformer | ||
| or a cache can serve real content instead of the tracking GIF, while POST keeps | ||
| the fast respond-first acknowledgement. To restore respond-first GET set | ||
| `async: true` or `async: { "GET": true }`; configs that set `async: false` only | ||
| to fix asset serving can drop it. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,8 @@ | ||
| --- | ||
| '@walkeros/web-destination-gtag': minor | ||
| --- | ||
|
|
||
| The GTM destination no longer pushes the `gtm.js` start event into the dataLayer | ||
| unless it loads the container itself. Set `loadScript: true` to have walkerOS | ||
| install GTM, start event included. Without it, walkerOS only pushes your mapped | ||
| events, so an existing container's triggers are left alone. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| { | ||
| "name": "elbwalker", | ||
| "owner": { | ||
| "name": "elbwalker", | ||
| "url": "https://github.com/elbwalker" | ||
| }, | ||
| "description": "Claude Code plugins for walkerOS, the open-source event data collection platform.", | ||
| "plugins": [ | ||
| { | ||
| "name": "walkeros", | ||
| "source": "./", | ||
| "description": "Skills and MCP tools for walkerOS - build sources, destinations, transformers, and flows." | ||
| } | ||
| ] | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -168,6 +168,36 @@ walkerOS exposes a Model Context Protocol (MCP) interface. AI agents can read | |
| your event schema, suggest tracking definitions, and generate integration code - | ||
| making your event layer programmable, not just configurable. | ||
|
|
||
| In Claude Code, one plugin installs both MCP servers and the walkerOS skills: | ||
|
|
||
| ``` | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win Add language identifiers to all command fences.
🧰 Tools🪛 markdownlint-cli2 (0.23.2)[warning] 173-173: Fenced code blocks should have a language specified (MD040, fenced-code-language) 📍 Affects 3 files
🤖 Prompt for AI AgentsSource: Linters/SAST tools |
||
| /plugin marketplace add elbwalker/walkerOS | ||
| /plugin install walkeros@elbwalker | ||
| ``` | ||
|
|
||
| For any other MCP client, add the servers to its configuration: | ||
|
|
||
| ```json | ||
| { | ||
| "mcpServers": { | ||
| "walkeros-flow": { | ||
| "command": "npx", | ||
| "args": ["@walkeros/mcp"] | ||
| }, | ||
| "walkeros-source-browser": { | ||
| "command": "npx", | ||
| "args": ["@walkeros/mcp-source-browser"] | ||
| } | ||
| } | ||
| } | ||
| ``` | ||
|
|
||
| Loading a flow, validating it, and simulating an event all run locally, no | ||
| account needed. See the [MCP docs](https://www.walkeros.io/docs/apps/mcp). | ||
|
|
||
| Coming from Google Tag Manager? See | ||
| [walkerOS vs. GTM](https://www.walkeros.io/docs/comparisons/gtm). | ||
|
|
||
| ## Contributing | ||
|
|
||
| ⭐️ Help us grow and star us. See our | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Register the source-browser server in the plugin manifest.
The package READMEs and website documentation state that
walkeros@elbwalkerinstalls both MCP servers. The current manifest declares onlywalkeros-flow; it does not start@walkeros/mcp-source-browser. (raw.githubusercontent.com) Add the missing server entry, or remove the claim from the documentation. Otherwise, the documented plugin installation does not expose the source-browser tools.Suggested manifest addition
"walkeros-flow": { "command": "npx", "args": ["`@walkeros/mcp`"] }, + "walkeros-source-browser": { + "command": "npx", + "args": ["`@walkeros/mcp-source-browser`"] + }🤖 Prompt for AI Agents
Source: MCP tools