build(historian): update server dependencies to 8.0.0-420053

[zhangxin511]

Description

Updates Historian base's Fluid server dependencies from 8.0.0-396786 to 8.0.0-420053 and refreshes the lockfile with the matching transitive dependency graph.

Validated with pnpm install --frozen-lockfile and pnpm run test (100 passing).

Reviewer Guidance

The review process is outlined in the pull request guidelines.

The lockfile includes expected transitive updates from the new server packages, including the MongoDB 6 dependency chain.

[Copilot]

Pull request overview

Updates the server/historian workspace to consume a newer set of Fluid server packages, and refreshes the pnpm lockfile to match the resulting transitive dependency graph (including the MongoDB 6.x chain).

Changes:

• Bump @fluidframework/*server* dependencies used by @fluidframework/historian-base from 8.0.0-396786 to 8.0.0-420053.
• Regenerate server/historian/pnpm-lock.yaml to reflect the new dependency graph and updated transitive versions.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.

File	Description
server/historian/packages/historian-base/package.json	Updates Historian base’s pinned Fluid server dependencies to 8.0.0-420053.
server/historian/pnpm-lock.yaml	Refreshes the lockfile to match the updated Historian base dependencies and transitive changes (including MongoDB-related packages).

Files not reviewed (1)

• server/historian/pnpm-lock.yaml: Generated file

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (401 lines, 3 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[github-actions]

Fleet Review — In progress

Running reviewers: correctness, security, api-compatibility, performance, testing

View run