ci(changesets): version packages

[voltagent-bot]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@voltagent/server-elysia@2.0.2

Patch Changes

• #993 48cc93f Thanks @Artist-MOBAI! - fix(server-elysia): Add Node.js compatibility and VoltOps Console support

---

Summary by cubic

Release @voltagent/server-elysia 2.0.2 with Node.js runtime compatibility and VoltOps Console support. This patch lets the Elysia server run on Node and be used from the VoltOps Console.

^{Written for commit b0ba6b7. Summary will update on new commits.}

Summary by CodeRabbit

Release Notes

• Bug Fixes
  • Improved Node.js compatibility
  • Added VoltOps Console support

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	b0ba6b7
Status:	✅  Deploy successful!
Preview URL:	https://0763babd.voltagent.pages.dev
Branch Preview URL:	https://changeset-release-main.voltagent.pages.dev

View logs

[coderabbitai]

📝 Walkthrough

Walkthrough

Release version 2.0.2 of @voltagent/server-elysia with Node.js compatibility and VoltOps Console support. The changeset entry is consumed, CHANGELOG is updated with the new release section, and package version is incremented from 2.0.1 to 2.0.2.

Changes

Cohort / File(s)	Summary
Version Bump packages/server-elysia/package.json	Version field updated from 2.0.1 to 2.0.2
Release Documentation .changeset/wicked-worms-wash.md, packages/server-elysia/CHANGELOG.md	Changeset entry consumed and removed; new 2.0.2 section added to CHANGELOG documenting Node.js compatibility and VoltOps Console support fix (PR #993)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Suggested reviewers

• omeraplak

Poem

🐰 Hop hop, the version grows,
From 2.0.1 to 2.0.2 it goes!
Changelog written, changeset blessed,
Node compatibility passed the test. 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description does not follow the provided template and lacks required sections like 'What is the current behavior?' and 'What is the new behavior?', though it provides auto-generated Changesets content.	This is an auto-generated Changesets release PR. Consider whether the template should apply to bot-generated PRs or if a separate template is needed for automated releases.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'ci(changesets): version packages' accurately describes the PR's purpose—it's an automated release PR that versions packages via the Changesets action.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[cubic-dev-ai]

No issues found across 3 files