Upgrade @langchain packages to fix npm ci ERESOLVE failure

[Copilot]

CI fails at npm ci with ERESOLVE because @langchain/google-genai@1.0.3 requires peer @langchain/core@1.0.6 exactly, while other packages resolve to @langchain/core@1.1.x.

Changes

Updated package.json to align @langchain package versions:

• @langchain/anthropic: ^1.0.0 → ^1.1.0
• @langchain/core: ^1.0.3 → ^1.1.0
• @langchain/google-genai: ^1.0.0 → ^2.0.0 (1.1.x doesn't exist; 2.0.0 requires core@1.1.0)
• @langchain/langgraph: ^1.0.1 → ^1.0.2
• @langchain/openai: ^1.0.0 → ^1.1.0
• langchain: ^1.0.3 → ^1.1.0

All peer dependencies now compatible with @langchain/core@1.1.0.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com//advisories
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

Problem summary:
The CI job (56717663968) fails at npm ci with ERESOLVE due to a peerDependency conflict between @langchain packages. Logs show @langchain/google-genai@1.0.3 requires peer @langchain/core@1.0.6, while the project installs @langchain/core@1.1.x, causing npm to abort with ERESOLVE.

Goal (long-term, correct fix):
Upgrade all @langchain/* packages (and the top-level langchain package) in package.json to matching 1.1.x versions so peerDependency requirements are consistent with @langchain/core@1.1.0 already present in the resolved install. This fixes the root cause rather than using --legacy-peer-deps.

Files to change:

• package.json (update dependency versions for the following keys in the "dependencies" section):
  • @langchain/anthropic
  • @langchain/core
  • @langchain/google-genai
  • @langchain/langgraph
  • @langchain/openai
  • langchain

Proposed package.json dependency changes (apply these version bumps):

• "@langchain/anthropic": "^1.1.0",
• "@langchain/core": "^1.1.0",
• "@langchain/google-genai": "^1.1.0",
• "@langchain/langgraph": "^1.1.0",
• "@langchain/openai": "^1.1.0",
• "langchain": "^1.1.0",

Rationale:

• Aligning all @langchain packages (and langchain) to the same minor release (1.1.x) ensures peerDependencies are compatible and avoids ERESOLVE in npm ci. This is a long-term fix because it keeps the dependency set coherent.

What the pull request will do:

• Update package.json with the version changes above.
• Include a PR description explaining the CI failure and the verification steps.

Verification steps the PR will include:

1. CI should run npm ci successfully (no ERESOLVE). The GitHub Actions job that previously failed is .github/workflows/pr-analyzer.yml (job run ref: 4801862). Check that npm ci completes.
2. Build: npm run build should finish without errors.
3. Optional: Run any unit tests (npm test) or a smoke run of the action if applicable.

Notes and follow-up:

• If any langchain package does not have a 1.1.x release compatible with core@1.1.0, I'll adjust the PR to pin the minimal set required or coordinate upgrades across packages.
• The PR will not change lockfiles (package-lock.json) directly here; CI will regenerate the lockfile when installing, but if you prefer, we can also update package-lock.json in this PR after running npm install locally.

References:

• Failing job logs (npm ERESOLVE): job 56717663968
• Current package.json file in the repo: https://github.com/techdebtgpt/pr-agent/blob/4801862b02eea68cf054791394a59d6562630e61/package.json

Please confirm and I will open the pull request that applies the package.json version changes and a short PR description with verification steps.

This pull request was created as a result of the following prompt from Copilot chat.

Problem summary:
The CI job (56717663968) fails at npm ci with ERESOLVE due to a peerDependency conflict between @langchain packages. Logs show @langchain/google-genai@1.0.3 requires peer @langchain/core@1.0.6, while the project installs @langchain/core@1.1.x, causing npm to abort with ERESOLVE.

Goal (long-term, correct fix):
Upgrade all @langchain/* packages (and the top-level langchain package) in package.json to matching 1.1.x versions so peerDependency requirements are consistent with @langchain/core@1.1.0 already present in the resolved install. This fixes the root cause rather than using --legacy-peer-deps.

Files to change:

• package.json (update dependency versions for the following keys in the "dependencies" section):
  • @langchain/anthropic
  • @langchain/core
  • @langchain/google-genai
  • @langchain/langgraph
  • @langchain/openai
  • langchain

Proposed package.json dependency changes (apply these version bumps):

• "@langchain/anthropic": "^1.1.0",
• "@langchain/core": "^1.1.0",
• "@langchain/google-genai": "^1.1.0",
• "@langchain/langgraph": "^1.1.0",
• "@langchain/openai": "^1.1.0",
• "langchain": "^1.1.0",

Rationale:

• Aligning all @langchain packages (and langchain) to the same minor release (1.1.x) ensures peerDependencies are compatible and avoids ERESOLVE in npm ci. This is a long-term fix because it keeps the dependency set coherent.

What the pull request will do:

• Update package.json with the version changes above.
• Include a PR description explaining the CI failure and the verification steps.

Verification steps the PR will include:

1. CI should run npm ci successfully (no ERESOLVE). The GitHub Actions job that previously failed is .github/workflows/pr-analyzer.yml (job run ref: 4801862). Check that npm ci completes.
2. Build: npm run build should finish without errors.
3. Optional: Run any unit tests (npm test) or a smoke run of the action if applicable.

Notes and follow-up:

• If any langchain package does not have a 1.1.x release compatible with core@1.1.0, I'll adjust the PR to pin the minimal set required or coordinate upgrades across packages.
• The PR will not change lockfiles (package-lock.json) directly here; CI will regenerate the lockfile when installing, but if you prefer, we can also update package-lock.json in this PR after running npm install locally.

References:

• Failing job logs (npm ERESOLVE): job 56717663968
• Current package.json file in the repo: https://github.com/techdebtgpt/pr-agent/blob/4801862b02eea68cf054791394a59d6562630e61/package.json

Please confirm and I will open the pull request that applies the package.json version changes and a short PR description with verification steps.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.