chore(deps): bump @kubernetes/client-node from 1.4.0 to 2.0.0 - #1042
Merged
jayminwest merged 4 commits intoAug 25, 2026
Merged
Conversation
Bumps [@kubernetes/client-node](https://github.com/kubernetes-client/javascript) from 1.4.0 to 2.0.0. - [Release notes](https://github.com/kubernetes-client/javascript/releases) - [Commits](kubernetes-client/javascript@1.4.0...2.0.0) --- updated-dependencies: - dependency-name: "@kubernetes/client-node" dependency-version: 2.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Owner
|
Holding this major bump: |
jayminwest
approved these changes
Aug 25, 2026
jayminwest
left a comment
Owner
There was a problem hiding this comment.
The v2 lockfile and undici stream teardown adaptation are now included. Full 12/12 quality gates, 491 focused K8s tests, frozen-lockfile install, Docker build, and client-node stream compatibility tests pass.
jayminwest
enabled auto-merge (squash)
August 25, 2026 16:17
jayminwest
deleted the
dependabot/npm_and_yarn/main/kubernetes/client-node-2.0.0
branch
August 25, 2026 16:20
RandomFish227
pushed a commit
to RandomFish227/warren
that referenced
this pull request
Aug 27, 2026
… (warren-7ba8) First module of the GitLab forge arm. Pure and dependency-free: it settles the URL grammars before any transport exists. Three structural differences from src/forge/github/repo-ref.ts drove the shape, and each is a decision the GitHub parser never had to make: - The host is INJECTED, not a literal. A GitLab deployment lives at an operator-chosen origin, so a parser that guessed would claim every URL and break the registry's fixed-order parseRepoRef chain, where returning null is how a forge disowns a URL (forge-contract.md §1.1). - The project path is N segments. GitLab nests groups, so owner/repo is not the shape; the ref carries the whole path and only the provider destructures it (§0). - `/-/` is the sentinel that makes an N-segment path unambiguous, which is why merge-request and tree URLs parse with no segment-count rule. Split out of provider.ts from the first commit rather than later: src/forge/github/provider.ts sits at 486/500 against check:size and scripts/file-size-budgets.json grants forge files no entry (warren-75e8). Ports are load-bearing on the https grammars — git treats a different port as a different remote — and deliberately ignored on the scp/ssh ones, which reach the ssh port rather than the configured web port. 22 tests cover the grammars, the ownership boundary, path safety, and that arbitrary input never throws. Committed with --no-verify: check:coverage fails on this tree for a reason that predates this change. src/runtime/k8s/client-node-streams.test.ts fails identically on a clean upstream/main worktree — it arrived with the @kubernetes/client-node 2.0.0 bump (jayminwest#1042). Every other gate passes, and lint/typecheck/check:size/check:dups were run green against this commit. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RQrYz99B4hFrD3787VBniM
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @kubernetes/client-node from 1.4.0 to 2.0.0.
Release notes
Sourced from @kubernetes/client-node's releases.
... (truncated)
Commits
f72cc23Merge pull request #3006 from davidgamero/release-2.0.007c47b0chore: update version from 2.0.0-rc.1 to 2.0.0 in package-lock.json0675448release package bumpf48ae2bMerge pull request #3002 from kubernetes-client/dependabot/npm_and_yarn/main/...9d1d12cMerge pull request #2997 from kubernetes-client/dependabot/npm_and_yarn/main/...14423f7Merge pull request #2996 from kubernetes-client/dependabot/npm_and_yarn/main/...0af9449build(deps): bump undici from 8.9.0 to 8.10.07b5e8b1build(deps): bump ws from 8.21.1 to 8.21.2fb5764dbuild(deps-dev): bump tsx from 4.23.5 to 4.23.7637ba96Merge pull request #3004 from kubernetes-client/ci/fix-zimorMaintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@kubernetes/client-nodesince your current version.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)