chore(ci): update pkg.pr.new for shared packages #3786

NathanFlurry · 2026-01-07T23:42:58Z

No description provided.

railway-app · 2026-01-07T23:43:06Z

🚅 Deployed to the rivet-pr-3786 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
frontend-cloud-prod	😴 Sleeping (View Logs)	Web	Jan 8, 2026 at 12:08 am
frontend-cloud-staging	😴 Sleeping (View Logs)	Web	Jan 8, 2026 at 12:08 am
frontend-inspector	😴 Sleeping (View Logs)	Web	Jan 8, 2026 at 12:06 am
website	❌ Build Failed (View Logs)	Web	Jan 7, 2026 at 11:59 pm

🚅 Deployed to the rivet-pr-3786 environment in rivet-frontend-website-preview

Service	Status	Web	Updated (UTC)
website	❌ Build Failed (View Logs)	Web	Jan 7, 2026 at 11:43 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Jan 7, 2026 at 11:43 pm

NathanFlurry · 2026-01-07T23:43:17Z

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

_{An organization admin has enabled the Graphite Merge Queue in this repository.} _{Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.}

This stack of pull requests is managed by Graphite. Learn more about stacking.

claude · 2026-01-07T23:44:18Z

PR Review: chore(ci): update pkg.pr.new for shared packages

Summary

This PR updates the pkg.pr.new CI workflow to include shared TypeScript packages and upgrades Next.js from 15.4.10 to 16.1.1 in example projects. The changes are focused on improving the package publishing process and keeping dependencies current.

Code Quality & Best Practices ✅

Positive aspects:

The CI workflow changes are well-targeted and follow the existing pattern
Proper exclusion of @rivetkit/example-registry from the build step to avoid unnecessary builds
Next.js upgrade follows semantic versioning appropriately
Lock file updates are consistent with the package.json changes

Changes Breakdown

1. CI Workflow Updates (.github/workflows/pkg-pr-new.yaml)

- pnpm build -F '@rivetkit/*'
+ pnpm build -F '@rivetkit/*' -F '!@rivetkit/example-registry'

- pnpm dlx pkg-pr-new publish 'engine/sdks/typescript/runner/' ...
+ pnpm dlx pkg-pr-new publish 'shared/typescript/*' 'engine/sdks/typescript/runner/' ...

Analysis:

✅ Adding shared/typescript/* to the publish list makes sense since there's a @rivetkit/virtual-websocket package there
✅ Excluding @rivetkit/example-registry from build is a good optimization
✅ The workflow will now properly publish shared packages that can be used between engine and rivetkit

2. Next.js Version Bump (15.4.10 → 16.1.1)

Analysis:

⚠️ Breaking Change Alert: Next.js 16 is a major version upgrade that includes breaking changes
⚠️ Node.js Requirement: Next.js 16 requires Node.js >=20.9.0 (up from >=18.18.0)
The examples should be tested to ensure they work with Next.js 16

3. Lock File Changes (pnpm-lock.yaml)

Observations:

Standard lock file updates for the dependency changes
All Next.js platform-specific binaries updated consistently
Website dependencies also updated to use Next.js 16

Potential Issues & Concerns

⚠️ Testing Concerns

No test evidence: There's no indication that the examples have been tested with Next.js 16
Breaking changes: Next.js 16 includes significant changes that could affect:
- App Router behavior
- Server Components
- Caching behavior
- Middleware

Recommendation: Run the example projects locally to verify they still work:

cd examples/chat-room-next-js && pnpm dev
cd examples/next-js && pnpm dev

⚠️ Version File Updates

The OpenAPI and AsyncAPI version bumps (2.0.32 → 2.0.33) suggest there were API changes, but this PR is labeled as a chore. The massive additions to rivetkit-openapi/openapi.json (+445 lines) include new error handling schemas.

Questions:

Are these API changes intentional for this PR, or did they leak in from another branch?
Should this be labeled as a feature/fix rather than a chore given the API changes?

Performance Considerations ✅

Excluding @rivetkit/example-registry from build should improve CI performance
No other performance concerns identified

Security Considerations ✅

The new error schemas in the OpenAPI spec include proper structured error handling
Next.js 16 includes the latest security patches
No security concerns identified

Test Coverage ⚠️

No tests were added or modified
The PR should ideally include verification that:
- Examples build successfully with Next.js 16
- The pkg.pr.new workflow publishes shared packages correctly
- The published packages can be installed and used

Recommendations

Test the examples with Next.js 16 before merging
Clarify the scope: If the OpenAPI changes are intentional, consider updating the PR description to mention them
Consider splitting: If the OpenAPI changes aren't related to the CI/dependency updates, they should be in a separate PR
CI verification: Ensure this PR's CI run successfully publishes all expected packages including @rivetkit/virtual-websocket

Verdict

Status: ⚠️ Approve with recommendations

The core changes are sound, but testing is needed to ensure Next.js 16 compatibility. The OpenAPI schema changes should be clarified as they seem significant for a "chore" PR.

Review generated by Claude Code

pkg-pr-new · 2026-01-07T23:45:16Z

More templates

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@3786

@rivetkit/db

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/db@3786

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@3786

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@3786

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@3786

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@3786

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@3786

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@3786

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@3786

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@3786

commit: 936d34d

graphite-app · 2026-01-08T21:33:52Z

Merge activity

Jan 8, 9:33 PM UTC: NathanFlurry added this pull request to the Graphite merge queue.
Jan 8, 9:34 PM UTC: CI is running for this pull request on a draft pull request (#3795) due to your merge queue CI optimization settings.
Jan 8, 9:34 PM UTC: Merged by the Graphite merge queue via draft PR: #3795.

railway-app bot temporarily deployed to rivet-frontend-website-preview / rivet-pr-3786 January 7, 2026 23:43 Destroyed

railway-app bot temporarily deployed to rivet-frontend / rivet-pr-3786 January 7, 2026 23:43 Destroyed

chore(ci): update pkg.pr.new for shared packages

936d34d

NathanFlurry force-pushed the 01-07-chore_ci_update_pkg.pr.new_for_shared_packages branch from 4d1a4d5 to 936d34d Compare January 7, 2026 23:57

railway-app bot temporarily deployed to rivet-frontend / rivet-pr-3786 January 7, 2026 23:57 Destroyed

NathanFlurry marked this pull request as ready for review January 8, 2026 00:01

This was referenced Jan 8, 2026

fix(rivetkit): bind handler to Registry in serve #3787

Closed

fix(rivetkit): fix default logic for serveManager & advertiseEndpoint #3789

Closed

graphite-app bot pushed a commit that referenced this pull request Jan 8, 2026

chore(ci): update pkg.pr.new for shared packages (#3786)

a7d9195

graphite-app bot closed this Jan 8, 2026

graphite-app bot deleted the 01-07-chore_ci_update_pkg.pr.new_for_shared_packages branch January 8, 2026 21:34

claude bot mentioned this pull request Jan 8, 2026

[Graphite MQ] Draft PR GROUP:spec_3b92cd (PRs 3786, 3787, 3789) #3795

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(ci): update pkg.pr.new for shared packages #3786

chore(ci): update pkg.pr.new for shared packages #3786

Uh oh!

NathanFlurry commented Jan 7, 2026

Uh oh!

railway-app bot commented Jan 7, 2026 •

edited

Loading

Uh oh!

NathanFlurry commented Jan 7, 2026 •

edited

Loading

Uh oh!

claude bot commented Jan 7, 2026 •

edited

Loading

Uh oh!

pkg-pr-new bot commented Jan 7, 2026 •

edited

Loading

Uh oh!

graphite-app bot commented Jan 8, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

chore(ci): update pkg.pr.new for shared packages #3786

chore(ci): update pkg.pr.new for shared packages #3786

Uh oh!

Conversation

NathanFlurry commented Jan 7, 2026

Uh oh!

railway-app bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

NathanFlurry commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

How to use the Graphite Merge Queue

Uh oh!

claude bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Review: chore(ci): update pkg.pr.new for shared packages

Summary

Code Quality & Best Practices ✅

Changes Breakdown

1. CI Workflow Updates (.github/workflows/pkg-pr-new.yaml)

2. Next.js Version Bump (15.4.10 → 16.1.1)

3. Lock File Changes (pnpm-lock.yaml)

Potential Issues & Concerns

⚠️ Testing Concerns

⚠️ Version File Updates

Performance Considerations ✅

Security Considerations ✅

Test Coverage ⚠️

Recommendations

Verdict

Uh oh!

pkg-pr-new bot commented Jan 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

graphite-app bot commented Jan 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Merge activity

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

railway-app bot commented Jan 7, 2026 •

edited

Loading

NathanFlurry commented Jan 7, 2026 •

edited

Loading

claude bot commented Jan 7, 2026 •

edited

Loading

pkg-pr-new bot commented Jan 7, 2026 •

edited

Loading

graphite-app bot commented Jan 8, 2026 •

edited

Loading