Version Packages#139
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
0c89243 to
5467be3
Compare
5467be3 to
7785f7e
Compare
7785f7e to
e7ec3bf
Compare
e7ec3bf to
c24818e
Compare
c24818e to
883ccef
Compare
883ccef to
529b9ac
Compare
529b9ac to
e06c69d
Compare
e06c69d to
e4555b8
Compare
e4555b8 to
bfeacee
Compare
bfeacee to
74dc246
Compare
74dc246 to
de36e54
Compare
de36e54 to
2819f25
Compare
2819f25 to
a710aca
Compare
a710aca to
4cd6828
Compare
4cd6828 to
ed78ae2
Compare
02c5e0c to
916a0ca
Compare
916a0ca to
9b0875e
Compare
9b0875e to
de812ee
Compare
de812ee to
81caf9d
Compare
81caf9d to
a04b561
Compare
a04b561 to
2f4ce32
Compare
2f4ce32 to
b5736c1
Compare
b5736c1 to
d7d3216
Compare
d7d3216 to
71f1730
Compare
71f1730 to
49360f8
Compare
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.
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
@dawn-ai/langchain@1.0.0
Major Changes
@langchain/core(0.3 → 1.x),@langchain/langgraph(0.2 → 1.x),@langchain/openai(0.3 → 1.x), andzod(3 → 4). Removes the dual-zod-version cast workaround intool-converter.ts;DynamicStructuredToolnow accepts Standard Schema directly. Downstream consumers must align on the new peer ranges (@langchain/core >=1.1.0).Minor Changes
34e615b: Add the first phase-3 harness capability: planning. A
plan.mdfile in a route directory now opts the agent into a built-inwrite_todostool, atodosstate channel, a Dawn-locked planning prompt fragment, and aplan_updateSSE event. IntroducesCapabilityMarkerandapplyCapabilitiesin@dawn-ai/core— the autowiring spine that all later phase-3 capabilities (skills, subagents, etc.) will reuse.affeb46: Capability tools can now mutate state channels via a Dawn-native
{result, state}wrapped return shape —resultbecomes the agent-visible ToolMessage;stateis a partial channel update applied via reducers. The langchain bridge translates this into a LangGraphCommand({update})internally; capability authors don't import from@langchain/langgraph. Plain tool returns (anything not matching the strict wrapper shape) work unchanged.Planning's
write_todosadopts the new shape, fixing the previously-documented re-emission loop: thetodosstate channel now actually reflects the agent's writes between turns, so the agent stops re-callingwrite_todoswith the same content. Theplan_updatestream transformer also reads defensively from both legacy and Command-shaped tool outputs so the SSE event keeps firing.1005b3a: Add provider-aware agent materialization. Agent configs can now carry an optional
provider, and the LangChain runtime infers providers for known model families or lazy-loads the explicit provider integration package for built-in provider IDs.e8462db:
agent({...})now accepts an optionalreasoning: { effort }field. Maps to OpenAI'sreasoningEffortparameter (none | minimal | low | medium | high | xhigh). Non-reasoning models silently ignore it. Useful for tool-use-heavy agents that aren't following directives at the default reasoning depth.Patch Changes
dawn buildagent deployment entry generation.@dawn-ai/cli@1.0.0
Minor Changes
ad17e85: Upgrade
@langchain/core(0.3 → 1.x),@langchain/langgraph(0.2 → 1.x),@langchain/openai(0.3 → 1.x), andzod(3 → 4). Removes the dual-zod-version cast workaround intool-converter.ts;DynamicStructuredToolnow accepts Standard Schema directly. Downstream consumers must align on the new peer ranges (@langchain/core >=1.1.0).dd242ac: Add the
agents-mdbuilt-in capability: Dawn now auto-injects<workspace>/AGENTS.mdinto every agent's system prompt under a# Memoryheading on every model turn. Always-on (no opt-in marker). Preserves the feedback loop — the agent updates its memory viawriteFileand the next turn sees the change automatically. Re-reads the file each turn (64 KiB cap; oversize, empty, or unreadable files render empty or a one-line notice).34e615b: Add the first phase-3 harness capability: planning. A
plan.mdfile in a route directory now opts the agent into a built-inwrite_todostool, atodosstate channel, a Dawn-locked planning prompt fragment, and aplan_updateSSE event. IntroducesCapabilityMarkerandapplyCapabilitiesin@dawn-ai/core— the autowiring spine that all later phase-3 capabilities (skills, subagents, etc.) will reuse.2ba0773: Add the phase-3 skills capability. A route with
src/app/<route>/skills/<name>/SKILL.mdfiles now exposes them to the agent via:# Skillssection in the system prompt listing each skill's name + descriptionreadSkill({ name })tool the agent calls to load a skill's full body on demandEach
SKILL.mdrequires YAML frontmatter withdescription;namedefaults to the directory name and can be overridden. The body lives in conversation history afterreadSkillreturns it (not re-injected each turn) — matches the deepagents / Claude Code convention. Typegen includesreadSkillinRouteToolswhen a route has skills. The chat example ships two seeded skills (workspace-conventions,recover-from-failure).Patch Changes
dawn buildagent deployment entry generation.toSseEventused to emitdata: {"data": <value>}for the built-inchunkevent and for capability-contributed events likeplan_update, when it should emitdata: <value>directly. The shaped events (tool_call,tool_result,done) are unchanged.langgraph.jsonartifact format is unchanged.@dawn-ai/core@1.0.0
Minor Changes
dd242ac: Add the
agents-mdbuilt-in capability: Dawn now auto-injects<workspace>/AGENTS.mdinto every agent's system prompt under a# Memoryheading on every model turn. Always-on (no opt-in marker). Preserves the feedback loop — the agent updates its memory viawriteFileand the next turn sees the change automatically. Re-reads the file each turn (64 KiB cap; oversize, empty, or unreadable files render empty or a one-line notice).34e615b: Add the first phase-3 harness capability: planning. A
plan.mdfile in a route directory now opts the agent into a built-inwrite_todostool, atodosstate channel, a Dawn-locked planning prompt fragment, and aplan_updateSSE event. IntroducesCapabilityMarkerandapplyCapabilitiesin@dawn-ai/core— the autowiring spine that all later phase-3 capabilities (skills, subagents, etc.) will reuse.2ba0773: Add the phase-3 skills capability. A route with
src/app/<route>/skills/<name>/SKILL.mdfiles now exposes them to the agent via:# Skillssection in the system prompt listing each skill's name + descriptionreadSkill({ name })tool the agent calls to load a skill's full body on demandEach
SKILL.mdrequires YAML frontmatter withdescription;namedefaults to the directory name and can be overridden. The body lives in conversation history afterreadSkillreturns it (not re-injected each turn) — matches the deepagents / Claude Code convention. Typegen includesreadSkillinRouteToolswhen a route has skills. The chat example ships two seeded skills (workspace-conventions,recover-from-failure).affeb46: Capability tools can now mutate state channels via a Dawn-native
{result, state}wrapped return shape —resultbecomes the agent-visible ToolMessage;stateis a partial channel update applied via reducers. The langchain bridge translates this into a LangGraphCommand({update})internally; capability authors don't import from@langchain/langgraph. Plain tool returns (anything not matching the strict wrapper shape) work unchanged.Planning's
write_todosadopts the new shape, fixing the previously-documented re-emission loop: thetodosstate channel now actually reflects the agent's writes between turns, so the agent stops re-callingwrite_todoswith the same content. Theplan_updatestream transformer also reads defensively from both legacy and Command-shaped tool outputs so the SSE event keeps firing.Patch Changes
82dd52f: Correct package README links and CLI/runtime examples, export the SDK reasoning type, and fix
dawn buildagent deployment entry generation.12ee95f: Two fixes surfaced by live LLM smoke testing the chat example end-to-end:
write_todosnow declares a real zod schema. Previously the tool'sschemafield was undefined; the LangChain bridge fell back toz.record(z.string(), z.unknown()), which produced JSON Schema withoutproperties. OpenAI strict-mode tool calling rejected the tool with400 Invalid schema for function 'write_todos': object schema missing properties. Now the planning marker exports an explicit zod schema for{ todos: Array<{ content, status }> }. Addszodas a runtime dependency of@dawn-ai/core.# Memoryblock now includes orientation text. The agents-md prompt fragment used to inject# Memory\n\n<content>only. With both planning and memory loaded, the model often calledlistDirandreadFileto look at AGENTS.md even though Dawn had already injected its contents. The fragment now opens with a short paragraph telling the agent the block IS the memory file, re-rendered each turn, and that the way to update it iswriteFile. Existing unit tests still pass — the# Memoryheading and content substrings are unchanged.Updated dependencies [82dd52f]
Updated dependencies [1005b3a]
Updated dependencies [e8462db]
@dawn-ai/sdk@1.0.0
Minor Changes
provider, and the LangChain runtime infers providers for known model families or lazy-loads the explicit provider integration package for built-in provider IDs.agent({...})now accepts an optionalreasoning: { effort }field. Maps to OpenAI'sreasoningEffortparameter (none | minimal | low | medium | high | xhigh). Non-reasoning models silently ignore it. Useful for tool-use-heavy agents that aren't following directives at the default reasoning depth.Patch Changes
dawn buildagent deployment entry generation.@dawn-ai/vite-plugin@1.0.0
Minor Changes
@langchain/core(0.3 → 1.x),@langchain/langgraph(0.2 → 1.x),@langchain/openai(0.3 → 1.x), andzod(3 → 4). Removes the dual-zod-version cast workaround intool-converter.ts;DynamicStructuredToolnow accepts Standard Schema directly. Downstream consumers must align on the new peer ranges (@langchain/core >=1.1.0).Patch Changes
dawn buildagent deployment entry generation.@dawn-ai/config-biome@1.0.0
Patch Changes
dawn buildagent deployment entry generation.@dawn-ai/config-typescript@1.0.0
Patch Changes
dawn buildagent deployment entry generation.create-dawn-ai-app@1.0.0
Patch Changes
dawn buildagent deployment entry generation.@dawn-ai/devkit@1.0.0
Patch Changes
dawn buildagent deployment entry generation.@dawn-ai/langgraph@1.0.0
Patch Changes
dawn buildagent deployment entry generation.@dawn-example/chat-server@0.0.1
Patch Changes