chore: sync pnpm lockfile for mcp alpha.10 - #3104
Open
dajiaohuang wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
CI follow-up: the checks that exercise the changed The root Setup Verification failure is unchanged on base commit |
ruvnet
added a commit
that referenced
this pull request
Aug 28, 2026
…ockfile fix Per ruvnet's review on #3119: - weighted RRF fusion previously had undefined ranking semantics for malformed weights (NaN poisons the sort comparator, negative/Infinity invert or swamp the intended ordering). Each weight component now validates independently (finite, >= 0) and falls back to its own documented default otherwise, same degradation as an omitted weights field already had. - rrf ties now break deterministically by entry.id (explicit secondary sort key) instead of relying on Array.sort's stability plus Map insertion order as an undocumented side effect. - 4 new tests: 3 malformed-weight fallback cases + 1 genuine-tie (weights: {semantic:0, structured:0}) deterministic-order case. Also ports PR #3104's fix verbatim (v3/pnpm-lock.yaml: @claude-flow/mcp specifier ^3.0.0-alpha.9 -> 3.0.0-alpha.10, matching the CLI manifest's exact pin) to unblock the install-dependent CI gates this PR needs to actually execute (issue #3101, also flagged in the review). Root-level npm ETARGET (issue #3095, package-lock.json) is a separate, still-open, maintainer-flagged issue with no proposed fix yet -- not addressed here. Validated: `corepack pnpm install --frozen-lockfile --lockfile-only` and `--ignore-scripts` both succeed from v3/; full @claude-flow/memory suite 465/466 (same 1 pre-existing unrelated env failure); tsc --noEmit clean. Co-Authored-By: RuFlo <ruv@ruv.net> Claude-Session: https://claude.ai/code/session_01AjuAxfhZi6eZXnLbLC14Ay
ruvnet
added a commit
that referenced
this pull request
Aug 29, 2026
Ports the 1-line fix from PR #3104 (still open, unmerged): main's own tip is failing 6+ smoke/CI jobs (Static regression guards, memory stats legacy-DB smoke, Smoke no-better-sqlite3, neural-trader feature attribution smoke, CLI npx-install smoke, MCP paired-tool round-trip smoke, Windows init hooks smoke) with ERR_PNPM_OUTDATED_LOCKFILE because v3/pnpm-lock.yaml still records @claude-flow/mcp at ^3.0.0-alpha.9 while v3/@claude-flow/cli/package.json pins it at 3.0.0-alpha.10. Verified locally: `pnpm install --frozen-lockfile` now succeeds with only this one-line change. Not this PR's failure (confirmed identical on main's own latest CI run before this commit), but porting it unblocks this PR's own CI rather than waiting on #3104 to merge separately. Co-Authored-By: RuFlo <ruv@ruv.net> Claude-Session: https://claude.ai/code/session_019nSbi8hkZdmwK2kaBXRj5J
ruvnet
pushed a commit
that referenced
this pull request
Aug 30, 2026
… to 1 row, live benchmark receipt - Port PR #3104's v3/pnpm-lock.yaml specifier fix (accepted, open) so v3-pnpm CI jobs (Type Check V3, Test V3 Packages) install cleanly; root-npm side (issue #3095) left to maintainer per that issue's own text. - Trim LEDGER.md back to exactly one row for this run (2026-08-30); the 2026-08-20..29 backfill this branch had accumulated belongs to its own ledger-repair effort, not this candidate's row. - Replace the hardcoded "~1.9x-4.7x, recall@10 ~0.99" replacement claim (itself sourced from a doc that self-contradicts ~0.9 vs ~0.99) with a live re-run of scripts/benchmark-intelligence.mjs on this commit, and point generated CLAUDE.md at the reproducible command instead of any hardcoded multiplier so it cannot drift stale again.
This was referenced Aug 30, 2026
Draft
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
1 participant
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.
Summary
@claude-flow/mcplockfile specifier with the CLI manifest's exact3.0.0-alpha.10pinmainRoot cause
v3/@claude-flow/cli/package.jsonwas updated to3.0.0-alpha.10, while the corresponding importer inv3/pnpm-lock.yamlstill recorded^3.0.0-alpha.9.Validation
corepack pnpm install --frozen-lockfile --lockfile-onlycorepack pnpm install --frozen-lockfile --ignore-scriptsFixes #3101