chore(engine): upgrade vbare 0.0.4

[NathanFlurry]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivetkit-serverless	Error			Nov 21, 2025 1:28am

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-cloud	Ignored			Nov 21, 2025 1:28am
rivet-inspector	Ignored			Nov 21, 2025 1:28am
rivet-site	Ignored			Nov 21, 2025 1:28am

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• chore(pegboard-runner): log runner messages #3514
• fix(runner-protocol): fix decoding gateway & req id from req id instead of message id #3513
• fix(runner-protocol): add noop converters for v1 -> v3 #3512
• chore(engine): upgrade vbare 0.0.4 #3511 👈 (View in Graphite)
• chore: remove msg id parts from protocol, move id utils to runner protocol crate #3508
• docs: runner lifecycle #3510
• chore(rivetkit): buffer outbound tunnel messages #3509
• fix(engine): ensure first keepalive tick is not skipped to prevent timeout on ws hibernation #3507
• chore(examples): add counter-next-js example #3506
• feat(cloudflare-workers): add createInlineClient #3466
• fix(rivetkit): uri encode actor ids to fix cloudflare workers actor id with generation #3504
• chore(rivetkit): fix lockfile #3503
• chore(rivetkit): make action cancelled error more descriptive #3500
• fix(gateway): prevent gc from removing hibernating in flight req, check actor started after sub when hibernating #3505
• fix(pb): add ability to timeout force resceduling pending state #3502
• fix(pb): stop actors from destroying on goingaway #3501
• fix(pegboard-gateway): ping hibernating requests both during open hws connections and during hibernation #3498 : 1 other dependent PR (#3499 )
• fix(rivetkit): fix graceful runner shutdown #3497
• fix(pegboard-gateway): write hws immediately on socket hibernate #3496
• chore(rivetkit): fix hibernation implementation #3494
• fix(tunnel): implement ping pong #3491 : 1 other dependent PR (#3475 )
• chore(pegboard-gateway): add new message id format & add deprecated tunnel ack #3492
• chore(pegboard-gateway): remove TunnelAck #3488
• chore(engine-runner): remove echo close on ToClientWebSocketClose #3487
• chore(rivetkit): implement new hibernating ws protocol #3464 : 1 other dependent PR (#3452 )
• fix(actor-kv): fix listing keys #3484
• fix(guard): handle actor stopped during ws/req #3481
• chore: rename retry -> hibernate in runner protocol #3473
• fix(udb): update backoff algo #3469
• chore: write/update docs #3468
• chore: add debug scripts #3467
• main

---

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]

PR Review: vbare 0.0.4 Upgrade

Summary

This PR upgrades the vbare library from a git dependency to the published crate version 0.0.4, along with upgrading vbare-compiler from 0.0.2 to 0.0.4. It also adds RUST_BACKTRACE=full to development scripts.

✅ Positive Observations

1. Dependency Management: Moving from a git dependency to a published crate version is a best practice that improves:

   • Build reproducibility
   • Dependency resolution speed
   • Stability (published versions are immutable)

2. Synchronized Versions: Both vbare and vbare-compiler are upgraded to 0.0.4, maintaining version alignment which is important for schema compilation tools.

3. Development Experience: Adding RUST_BACKTRACE=full to the development scripts will provide better debugging information during local development.

4. Follows Conventions: Changes align with CLAUDE.md guidelines for workspace dependency management using .workspace = true pattern.

🔍 Areas for Consideration

1. Missing Context: The PR description is empty. Consider adding:

   • What changed in vbare 0.0.4 that prompted this upgrade
   • Whether this is a breaking change or bugfix
   • Any migration steps or behavioral changes developers should be aware of

2. Testing: Since vbare is used extensively (41 files reference it) for versioned data serialization in critical systems (Pegboard, protocols, etc.):

   • ✅ Have all tests passed?
   • ✅ Has this been tested with the dev environment (docker/dev)?
   • Consider running integration tests, especially around:
     • Protocol versioning (ups-protocol, runner-protocol, epoxy-protocol)
     • Pegboard state management
     • Message chunking in UniversalPubSub

3. Changelog/Release Notes: For a library upgrade affecting core serialization:

   • Review the vbare 0.0.4 release notes/changelog
   • Verify compatibility with existing serialized data
   • Confirm no schema breaking changes

4. Script Changes: The RUST_BACKTRACE=full additions are helpful but:

   • Consider documenting this in CLAUDE.md if it's a standard practice
   • Ensure this doesn't negatively impact performance in dev (though unlikely)

🎯 Recommendations

Before Merging:

1. Add a brief PR description explaining the upgrade motivation
2. Confirm all CI checks pass
3. Run the dev environment with both engine-postgres and engine-rocksdb scripts
4. Verify backward compatibility with existing serialized data

Nice to Have:

1. Update CLAUDE.md if RUST_BACKTRACE=full should be standard for dev scripts
2. Link to vbare 0.0.4 release notes/changelog in the PR description

📊 Code Quality Assessment

• Style: ✅ Follows Cargo.toml workspace conventions
• Security: ✅ No security concerns identified (moving to published crate reduces supply chain risk)
• Performance: ⚠️ Need to verify vbare 0.0.4 doesn't introduce performance regressions in serialization paths
• Maintainability: ✅ Improved by using published version

Overall Assessment

This is a clean, low-risk upgrade that follows best practices. The main gaps are around testing verification and documentation. Once CI passes and integration testing is confirmed, this should be safe to merge.

Recommendation: ✅ Approve pending CI and integration testing confirmation

[graphite-app]

Merge activity

• Nov 21, 2:40 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
• Nov 21, 2:42 AM UTC: CI is running for this pull request on a draft pull request (#3515) due to your merge queue CI optimization settings.
• Nov 21, 2:43 AM UTC: Merged by the Graphite merge queue via draft PR: #3515.