Skip to content

fix(server-hono): require server-core schema factory release#1230

Closed
omeraplak wants to merge 1 commit into
mainfrom
fix/server-hono-core-release-floor
Closed

fix(server-hono): require server-core schema factory release#1230
omeraplak wants to merge 1 commit into
mainfrom
fix/server-hono-core-release-floor

Conversation

@omeraplak

@omeraplak omeraplak commented Apr 23, 2026

Copy link
Copy Markdown
Member

PR Checklist

Please check if your PR fulfills the following requirements:

Bugs / Features

What is the current behavior?

@voltagent/server-hono@2.0.12 imports createServerCoreSchemas from @voltagent/server-core, but its dependency range still allows installs to resolve a server-core version that does not publish that runtime export. That can produce:

The requested module @voltagent/server-core does not provide an export named createServerCoreSchemas

What is the new behavior?

Updates the existing hotfix changeset so both @voltagent/server-core and @voltagent/server-hono receive patch releases, and raises the server-hono dependency floor for @voltagent/server-core to ^2.1.15.

This makes the follow-up server-hono patch release resolve against a server-core release that provides createServerCoreSchemas.

fixes #1222

Notes for reviewers

This is a release metadata hotfix only; no runtime code changed in this PR, so no runtime tests were added.

Validation:

  • node -e "JSON.parse(require('fs').readFileSync('packages/server-hono/package.json','utf8'))"
  • pnpm exec prettier --check .changeset/silver-rules-report.md packages/server-hono/package.json

@changeset-bot

changeset-bot Bot commented Apr 23, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 8980f83

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 2 packages
Name Type
@voltagent/server-core Patch
@voltagent/server-hono Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Apr 23, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Updates the @voltagent/server-hono package dependency on @voltagent/server-core from ^2.1.14 to ^2.1.15. Adds @voltagent/server-hono to the changeset file and updates the narrative to reflect the dependency requirement for the createServerCoreSchemas runtime export.

Changes

Cohort / File(s) Summary
Changeset Update
.changeset/silver-rules-report.md
Added @voltagent/server-hono as a patched package alongside @voltagent/server-core; updated description to document that server-hono requires server-core release with createServerCoreSchemas export.
Dependency Version Bump
packages/server-hono/package.json
Bumped @voltagent/server-core dependency constraint from ^2.1.14 to ^2.1.15.

Possibly related PRs

Poem

🐰 A version dances up the line,
From 2.1.14 to 15 so fine,
Schemas exported, bright and true,
Dependencies aligned anew! ✨

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: raising server-hono's dependency floor to require a server-core release that provides the createServerCoreSchemas export.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description check ✅ Passed PR description fully addresses the template with all required sections completed: checklist items checked, current/new behavior explained, issue linked, and validation notes provided.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/server-hono-core-release-floor

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@ghost

This comment has been minimized.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
.changeset/silver-rules-report.md (1)

8-10: Consider clarifying the changeset narrative.

The phrase "Publishes the createServerCoreSchemas export" might suggest that server-core is adding the export in this changeset, when in fact the export already exists in server-core@2.1.15 and this PR only updates server-hono's dependency floor to require it.

✍️ Alternative wording for clarity
-Publishes the `createServerCoreSchemas` export used by `@voltagent/server-hono` to build Swagger
-schemas with the active Zod instance, and updates `server-hono` to require a `server-core` release
-that provides the runtime export.
+Updates `@voltagent/server-hono` to require `server-core@^2.1.15`, which provides the
+`createServerCoreSchemas` export needed to build Swagger schemas with the active Zod instance.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.changeset/silver-rules-report.md around lines 8 - 10, The changeset text is
ambiguous about where createServerCoreSchemas was introduced; update the
narrative to state that createServerCoreSchemas already exists in
server-core@2.1.15 and this PR only tightens server-hono's dependency to require
that release (i.e., “Bumps server-hono to require server-core@>=2.1.15 so it can
use the existing createServerCoreSchemas runtime export”), mentioning
createServerCoreSchemas, server-core@2.1.15, and server-hono to make the intent
explicit.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/server-hono/package.json`:
- Line 13: The package.json currently pins "@voltagent/server-core" to a
non-existent version "^2.1.15", which will break installs; update the dependency
entry for "@voltagent/server-core" to use the published version string "^2.1.14"
(or wait and change to "^2.1.15" only after that version is published) so that
the dependency resolves correctly and exports like createServerCoreSchemas
remain available.

---

Nitpick comments:
In @.changeset/silver-rules-report.md:
- Around line 8-10: The changeset text is ambiguous about where
createServerCoreSchemas was introduced; update the narrative to state that
createServerCoreSchemas already exists in server-core@2.1.15 and this PR only
tightens server-hono's dependency to require that release (i.e., “Bumps
server-hono to require server-core@>=2.1.15 so it can use the existing
createServerCoreSchemas runtime export”), mentioning createServerCoreSchemas,
server-core@2.1.15, and server-hono to make the intent explicit.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5480e556-f586-434d-aa33-8c2d86624161

📥 Commits

Reviewing files that changed from the base of the PR and between ba8d7e0 and 8980f83.

📒 Files selected for processing (2)
  • .changeset/silver-rules-report.md
  • packages/server-hono/package.json

"@voltagent/mcp-server": "^2.0.2",
"@voltagent/resumable-streams": "^2.0.1",
"@voltagent/server-core": "^2.1.14",
"@voltagent/server-core": "^2.1.15",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify server-core 2.1.15 exists and exports createServerCoreSchemas

# Check if version 2.1.15 is published
echo "=== Checking published versions of `@voltagent/server-core` ==="
npm view `@voltagent/server-core` versions --json | jq -r '.[]' | grep -E '^2\.1\.(14|15|16)$'

# Check package.json version in server-core
echo -e "\n=== Current server-core package version ==="
cat packages/server-core/package.json | jq -r '.version'

# Check if createServerCoreSchemas is exported from server-core
echo -e "\n=== Verifying createServerCoreSchemas export ==="
rg -n "export.*createServerCoreSchemas" packages/server-core/

# Check the schemas file that should export it
echo -e "\n=== Checking agent.schemas.ts export ==="
fd -t f "agent.schemas.ts" packages/server-core/ --exec cat {}

Repository: VoltAgent/voltagent

Length of output: 22029


Version 2.1.15 of @voltagent/server-core does not exist. Only version 2.1.14 is currently published. The dependency specification "^2.1.15" will fail to resolve during installation. Either downgrade to "^2.1.14" or ensure version 2.1.15 is published before merging (note: createServerCoreSchemas is correctly exported when the version is available).

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@packages/server-hono/package.json` at line 13, The package.json currently
pins "@voltagent/server-core" to a non-existent version "^2.1.15", which will
break installs; update the dependency entry for "@voltagent/server-core" to use
the published version string "^2.1.14" (or wait and change to "^2.1.15" only
after that version is published) so that the dependency resolves correctly and
exports like createServerCoreSchemas remain available.

@omeraplak omeraplak closed this Apr 23, 2026
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.

[BUG] swagger is empty

1 participant