Skip to content

fix(graphile-llm): bump graphile-search peer to ^2; document Node 22 floor - #1822

Merged
pyramation merged 1 commit into
mainfrom
feat/graphile-llm-search-peer-node22
Sep 9, 2026
Merged

fix(graphile-llm): bump graphile-search peer to ^2; document Node 22 floor#1822
pyramation merged 1 commit into
mainfrom
feat/graphile-llm-search-peer-node22

Conversation

@pyramation

Copy link
Copy Markdown
Contributor

Summary

Fixes the peer-dependency conflict a fresh npm install pgpm@5.30.5 reports:

npm warn Conflicting peer dependency: postgraphile@5.0.3
npm warn   peer postgraphile@"5.0.3" from graphile-search@1.21.6
npm warn     peerOptional graphile-search@"^1.18.0" from graphile-llm@1.15.8

Root cause: graphile-llm still declared peerDependencies["graphile-search"] = "^1.18.0" while the workspace (and graphile-settings) ship graphile-search@2.14.6. npm satisfies the stale optional peer by hoisting the last 1.x (1.21.6, which pins exact peers postgraphile@5.0.3, graphile-build@5.0.2, …) next to the 2.14.6 the rest of the tree uses — an extraneous second copy with peers a minor behind. graphile-llm is already built and tested against the workspace 2.x via its devDependencies, so the pin was simply never bumped.

- "graphile-search": "^1.18.0",
+ "graphile-search": "^2.0.0",

Only stale internal peer in the repo (checked every peerDependencies entry naming a workspace package against that package's current version).

Also: constructive-monorepo-setup skill said "Node.js 20+"; the root engines and postgraphile/grafast/@dataplan/pg all declare node >=22 (and grafast needs Promise.withResolvers), so the skill now says 22+. Companion doc fixes: constructive.io prerequisites page and constructive-platform README.

Link to Devin session: https://app.devin.ai/sessions/6d533da4fa5a48399ad2c7508dffa32b
Open in Devin Desktop: https://app.devin.ai/desktop/session/6d533da4fa5a48399ad2c7508dffa32b?variant=devin
Requested by: @pyramation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@tenki-reviewer

tenki-reviewer Bot commented Sep 9, 2026

Copy link
Copy Markdown

Review complete. No issues found — approved ✅.


This PR makes two small, coherent changes: it raises the graphile-search peerDependency from ^1.18.0 to ^2.0.0 in graphile/graphile-llm/package.json, and it updates the constructive-monorepo-setup skill to require Node.js 22+ instead of 20+. The peer bump aligns with the already-published graphile-search 2.x line and the imports in the package's tests, and the Node floor is a documentation-only change with no code impact. No contradictory constraints or version disagreements were found.

Files Change
graphile/graphile-llm/package.json Raises the graphile-search peerDependency to ^2.0.0, aligning the manifest with the 2.x API the package already uses.
.agents/skills/constructive-monorepo-setup/SKILL.md Updates the documented Node.js requirement from 20+ to 22+.

Reviewed commit: 8bd86ea

@pyramation
pyramation merged commit e008e93 into main Sep 9, 2026
21 checks passed
@pyramation
pyramation deleted the feat/graphile-llm-search-peer-node22 branch September 9, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant