Repository navigation
📖 Update kubestellar-mcp docs to v0.9.19 - #7440
Conversation
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
|
/lgtm |
|
@clubanderson: you cannot LGTM your own PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
kubestellar-prow
Bot
added
the
dco-signoff: yes
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clubanderson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: clubanderson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubestellar-prow
Bot
added
approved
✅ Deploy Preview for kubestellar-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
kubestellar-prow
Bot
added
the
size/S
hivecommons-hive
Bot
added
author/clanker
There was a problem hiding this comment.
🟢 Approval recommended
The version metadata is consistent across all three files, with no unresolved findings.
No open issues 🎉
What changed in this PR
Updates the documentation version metadata for KubeStellar MCP v0.9.19.
Changes:
- Sets v0.9.19 as the current and latest release.
- Preserves v0.9.18 as a selectable historical version.
- Synchronizes shared configuration and its timestamp.
| File | Description |
|---|---|
| src/config/versions/lookup.ts | Sets the current version to 0.9.19. |
| src/config/versions/data/kubestellar-mcp.ts | Updates latest and retains v0.9.18. |
| public/config/shared.json | Mirrors version changes and refreshes the timestamp. |
Review effort: Balanced
hivecommons-hive
Bot
added
stage/072-returned-to-contributor
|
@clubanderson this PR is back in your court ( Failing checks:
Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path. Queued in your relay fix queue (1 waiting): fixes are handed out before new work as soon as you have capacity. |
|
Triage note (quality agent): the Fix: update this PR's branch against 🐝 Hive Agent: — hive: agent=quality backend=copilot model=claude-opus-4.7 copilot=1.0.88 |
![hivecommons-hive[bot]](https://avatars.githubusercontent.com/in/3568013?s=60&v=4){kind=small}
There was a problem hiding this comment.
Read the full diff against the tree at the reviewed head (3acede3). This is a correct, internally consistent v0.9.18 → v0.9.19 bump:
public/config/shared.json—latestlabel/branch updated,0.9.18archived into the version map,currentVersionbumped.src/config/versions/data/kubestellar-mcp.ts— same change mirrored inKUBESTELLAR_MCP_VERSIONS(latest → 0.9.19,0.9.18added as a non-default entry).src/config/versions/lookup.ts:56—currentVersion: "0.9.19"matches both.
I verified the target branch docs/kubestellar-mcp/0.9.19 exists (head f888315), so the new latest dropdown entry resolves. Looks correct to me.
The red check is not this PR's fault. pull-kubestellar-docs-test failed with ReferenceError: Iterator is not defined thrown from node_modules/jsdom/lib/jsdom/living/helpers/dom-tree.js:75 while spawning the worker for src/__tests__/PlaygroundPage.test.tsx — the prow runner's Node is older than the Iterator global that this jsdom version requires (Node ≥ 22). The run itself reports 105 files / 1298 tests, all passed; the exit-1 comes from 74 worker-startup errors, not test failures. The GitHub Actions "Run unit tests" job on the same head is green. A maintainer should bump Node in the prow job image (or pin jsdom) — this PR only edits version-config files and cannot trigger or fix that.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88
|
@clubanderson the hive has adopted this PR ( |
hivecommons-hive
Bot
added
stage/074-adopted-by-hive
|
hive/awaiting-ci: 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5 copilot=1.0.88 |
… processes (#7445) The polyfill from #7443 fixed the worker-global Iterator but left two failure modes that the prow presubmit (which never ran on #7443's scripts-only diff) exposed on the next PR (#7440): 1. jsdom >= 30 creates each window as a fresh vm context and reads every JS global out of it with vm.runInContext(name, window). The fresh context on Node 20 has no Iterator, so window creation throws "ReferenceError: Iterator is not defined" and every jsdom-environment test file fails to start. The polyfill now wraps vm.createContext to mirror the polyfilled Iterator into each new context. 2. NODE_OPTIONS carried a cwd-relative --require path, which each child node process resolves against ITS cwd. Script tests that spawn node with a tmpdir cwd (check-leaderboard-regression, release-version, ci-observability reporter — 30 failing tests) died at startup with MODULE_NOT_FOUND / exit 1. The polyfill now rewrites NODE_OPTIONS to its own absolute path so inherited environments work from any cwd. Signed-off-by: scanner <scanner@hive.kubestellar.io> Co-authored-by: scanner <scanner@hive.kubestellar.io> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Read the full diff against the tree at head 680274e. This looks correct to me:
- The bump is consistent across all three places that encode the current version:
public/config/shared.json(latest label/branch +currentVersion),src/config/versions/data/kubestellar-mcp.ts(KUBESTELLAR_MCP_VERSIONS), andsrc/config/versions/lookup.ts:56(currentVersion: "0.9.19"). - The previous latest (0.9.18) is correctly re-added as an archived dropdown entry in both
shared.jsonandkubestellar-mcp.ts, matching the pattern used for 0.9.17 and earlier. - The referenced branch
docs/kubestellar-mcp/0.9.19exists in this repo, so the dropdown entry will resolve.
On the red check: pull-kubestellar-docs-test is an infrastructure failure, not this PR. The prow log shows every failing file dies at vitest worker startup with ReferenceError: Iterator is not defined raised from jsdom/lib/jsdom/browser/Window.js:62 — the prow job's Node runtime predates the Iterator global that current jsdom requires. The GitHub Actions "Run unit tests" job on the same head passed (1268/1298 pass even on prow; the 30 failures are all the worker-startup error). This diff touches only version strings in config and could not cause it.
Tide is waiting on an lgtm label — flagging for a maintainer: this is a routine automated release bump and appears safe to label and let tide merge.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88
|
/retest 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5 copilot=1.0.88 |
|
hive/awaiting-ci: pull-kubestellar-docs-test re-triggered via /retest after the Iterator-polyfill fix (#7445) merged; CI pending — sweep will merge when green. 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5 copilot=1.0.88 |
Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com>
kubestellar-prow
Bot
added
the
dco-signoff: yes
hivecommons-hive
Bot
removed
the
dco-signoff: yes
There was a problem hiding this comment.
Read all three files at head 944ff61 against the tree — this looks correct to me.
public/config/shared.json,src/config/versions/data/kubestellar-mcp.ts, andsrc/config/versions/lookup.ts:56are mutually consistent (latest → v0.9.19, branchdocs/kubestellar-mcp/0.9.19, prior 0.9.18 archived).- Each file follows its own existing ordering convention: shared.json appends
0.9.18at the end of its ascending historical list; the TS map inserts it above0.9.17in its descending list — both match the surrounding entries. - The branch
docs/kubestellar-mcp/0.9.19exists on the repo, so the dropdown target resolves.
The one red check, pull-kubestellar-docs-test, is infrastructure, not this diff: the prow log shows all 1298/1298 tests passed, but 74 worker-startup errors from TypeError: Promise.withResolvers is not a function in jsdom .../Document-impl.js:574 — the prow runner's Node is older than jsdom now requires. The same vitest suite passed on the GitHub-hosted "Run unit tests" check. A retest after the runner's Node is bumped should go green; nothing in this PR can fix it.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88
|
pull-kubestellar-docs-test failure is CI infrastructure, not this diff: all 1298 vitest tests passed, but 74 unhandled 🐝 Hive Agent: — hive: agent=architect backend=copilot model=claude-opus-4.7 copilot=1.0.88 |
|
/retest 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5 copilot=1.0.88 |
|
hive/awaiting-ci: pull-kubestellar-docs-test failed on a pre-#7445 main; fix merged 2026-10-18, /retest issued. Tide merges when green. 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5 copilot=1.0.88 |
kubestellar-prow
Bot
added
the
dco-signoff: yes
hivecommons-hive
Bot
removed
the
dco-signoff: yes
There was a problem hiding this comment.
Verified this automated bump — looks correct to me.
- The three files change consistently:
public/config/shared.json,src/config/versions/data/kubestellar-mcp.ts, andsrc/config/versions/lookup.tsall move latest to v0.9.19 and demote v0.9.18 into the archived version list (both JSON and TS copies, so dropdown and runtime config stay in sync). - Both referenced branches exist in this repo:
docs/kubestellar-mcp/0.9.19(f888315) anddocs/kubestellar-mcp/0.9.18. - Netlify deploy-preview, build, verify, link check, TypeScript/ESLint, and the GHA unit tests are all green.
The one red check, pull-kubestellar-docs-test (prow), is infrastructure, not this diff: the log shows 1298/1298 tests passed but 74 worker-startup errors — TypeError: Promise.withResolvers is not a function thrown from jsdom .../Document-impl.js:574 when vitest forks workers. Promise.withResolvers requires Node ≥22; the prow runner image is on an older Node, while the GHA "Run unit tests" job (newer Node) passes the identical suite. Fix belongs in the prow job's Node image, not in this PR. A retest after that image bump should go green with no code change.
— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88
kubestellar-prow
Bot
added
the
dco-signoff: yes
hivecommons-hive
Bot
removed
dco-signoff: yes
|
Ready for a human merge: verdict approved @1a749d1, 12/12 checks green, DCO yes, soak 30m0s elapsed. Blocked only by The hive never approves on your behalf: |
hivecommons-hive
Bot
added
stage/090-ready-for-human-merge
|
Thank you for your contribution! Your PR has been merged. Check out what's new:
Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey |
Summary
Automated update for kubestellar-mcp release v0.9.19.
docs/kubestellar-mcp/0.9.19Checklist
🤖 Generated automatically on release