Repository navigation
chore(examples): migrate to v3 authoring and lifecycle APIs - #3
Closed
zrosenbauer wants to merge 1 commit into
Closed
zrosenbauer wants to merge 1 commit into
zrosenbauer wants to merge 1 commit into
Conversation
This was referenced Oct 14, 2026
Owner
Author
|
Closing because this PR was mistakenly opened against the fork. Recreating it as a cross-fork draft against VoltAgent/voltagent:next; the source branch is preserved. |
Owner
Author
|
Replaced by the upstream draft: VoltAgent#1456 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Bugs / Features
What is the current behavior?
Examples and generators teach constructor-based authoring and implicit application startup, so newly scaffolded applications do not match the v3 API.
What is the new behavior?
Testing
Notes for reviewers
Layer 3 of 4, based on #2. Review and merge bottom-up: #1 → #2 → #3 → #4.
Documentation and rendered website snippets follow in #4. All PRs remain drafts in this fork.