v0.3.1: cluster-scoped events recipe, get_recent_events cluster filter - #26
Conversation
…filter; v0.3.1 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 41419849c1
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| { | ||
| "name": "agent-plugin", | ||
| "version": "0.3.0", | ||
| "version": "0.3.1", |
There was a problem hiding this comment.
With this bump, both version fields in package-lock.json remain at 0.3.0. Once dependencies are installed, npm run validate rejects this package because scripts/validate.mjs requires both packageLock.version and packageLock.packages[""].version to match plugin.json, so the validation and release workflows cannot pass until the lockfile is updated to 0.3.1.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Fixed in 2131779: package-lock.json root and packages[""] versions are 0.3.1; the release verifier test (lockVersion must match portableVersion) passes again, 40/40.
…e current version v0.3.1 is stated as pending until it is verified against production, which keeps this PR red on purpose until the backend release with the cluster filter is deployed and the check is run. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2 participants
Pairs with the backend PR adding a
clusterfilter (exactclusterID) toget_recent_eventsandclusterID/clusterNameon event rows (the multi-cluster scoping graph-api had since ANY-1855).(clusterID, ts)index; measured 0.2 s vs 5 s and a capped page for the unscoped call on a large tenant.clusteronget_recent_events.Tag
v0.3.1after merge once the backend release carrying the filter is deployed.🤖 Generated with Claude Code