Skip to content

ci(changesets): version packages - #1079

Merged
omeraplak merged 1 commit into
mainfrom
changeset-release/main
Feb 18, 2026
Merged

ci(changesets): version packages#1079
omeraplak merged 1 commit into
mainfrom
changeset-release/main

Conversation

@voltagent-bot

@voltagent-bot voltagent-bot commented Feb 18, 2026

Copy link
Copy Markdown
Member

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/core@2.4.3

Patch Changes

  • #1078 fbce8aa Thanks @omeraplak! - fix: persist workflow context mutations across steps and downstream agents/tools

    Workflows now consistently use the execution context map when building step state.
    This ensures context written in one step is visible in later steps and in andAgent calls.

    Also aligns workflow event/stream context payloads with the normalized runtime context.


Summary by cubic

Publish @voltagent/core 2.4.3 to fix workflow context persistence across steps and downstream agents/tools. Event and stream context payloads are now aligned with the normalized runtime context.

  • Dependencies
    • Update all example apps to use @voltagent/core ^2.4.3.
    • Refresh pnpm lockfile; rolldown packages upgraded to 1.0.0-rc.5.

Written for commit b94a985. Summary will update on new commits.

Summary by CodeRabbit

  • Bug Fixes

    • Fixed an issue where workflow context mutations were not persisting across steps and downstream agent/tool calls. Context changes made in one step are now correctly visible in subsequent steps.
  • Chores

    • Updated all example projects to the latest core package version.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Feb 18, 2026

Copy link
Copy Markdown

Deploying voltagent with  Cloudflare Pages  Cloudflare Pages

Latest commit: b94a985
Status: ✅  Deploy successful!
Preview URL: https://79d28128.voltagent.pages.dev
Branch Preview URL: https://changeset-release-main.voltagent.pages.dev

View logs

@ghost

This comment has been minimized.

@coderabbitai

coderabbitai Bot commented Feb 18, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Release of @voltagent/core v2.4.3 addressing workflow context persistence. Removes changeset file, bumps core package version, updates CHANGELOG, and updates dependency references across 60+ example projects.

Changes

Cohort / File(s) Summary
Changeset Removal
.changeset/neat-context-persist.md
Deletes the changeset file that documented the workflow context persistence fix.
Core Package Release
packages/core/package.json, packages/core/CHANGELOG.md
Bumps @voltagent/core version from 2.4.2 to 2.4.3 and adds CHANGELOG entry documenting the fix for context mutations persisting across steps and andAgent calls.
Example Dependencies
examples/*/package.json
Updates @voltagent/core dependency from ^2.4.2 to ^2.4.3 across 60+ example projects including base, github-repo-analyzer, next-js-chatbot-starter-template, with-agent-tool, with-auth, with-mcp, with-slack, with-workflow, and others.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~8 minutes

Possibly related PRs

Poem

🐰 Hoppy release day, version three-point-four!
Context mutations now flow through each door
Sixty examples updated with glee
v2.4.3 hops wild and free! 🚀✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'ci(changesets): version packages' accurately describes the main change—this is an automated version bump and release preparation PR generated by the Changesets action.
Description check ✅ Passed The description is complete and appropriate for an automated Changesets release PR. It explains the purpose, lists the releases with detailed patch notes, and includes auto-generated summary information.
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.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch changeset-release/main

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.

@cubic-dev-ai cubic-dev-ai 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.

No issues found across 82 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

@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.

🧹 Nitpick comments (1)
examples/with-nextjs-resumable-stream/package.json (1)

63-63: Pre-existing: stale repository.directory value.

Line 63 still points to "examples/with-nextjs-ai-elements" while the package name and all other metadata indicate the directory should be "examples/with-nextjs-resumable-stream". Since this is a private package the npm publish impact is nil, but correcting it keeps the monorepo metadata accurate.

🔧 Proposed fix
-    "directory": "examples/with-nextjs-ai-elements"
+    "directory": "examples/with-nextjs-resumable-stream"
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@examples/with-nextjs-resumable-stream/package.json` at line 63, The
package.json has a stale repository.directory value
("examples/with-nextjs-ai-elements"); update the repository.directory field to
"examples/with-nextjs-resumable-stream" so it matches the package name and
metadata in this package.json (look for the "repository" -> "directory" entry
and change its string value accordingly).
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@examples/with-nextjs-resumable-stream/package.json`:
- Line 63: The package.json has a stale repository.directory value
("examples/with-nextjs-ai-elements"); update the repository.directory field to
"examples/with-nextjs-resumable-stream" so it matches the package name and
metadata in this package.json (look for the "repository" -> "directory" entry
and change its string value accordingly).

@omeraplak
omeraplak merged commit de35e3c into main Feb 18, 2026
23 checks passed
@omeraplak
omeraplak deleted the changeset-release/main branch February 18, 2026 18:40
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.

2 participants