chore(release): v3.4.0 — programmable orchestration#60
Merged
Conversation
Programmable orchestration (AgentExecutor seam, parallel/pipeline/resumable combinators, WorkflowCheckpoint, Node + Python SDK grammar) + the #31/#32/#43 hardening since v3.3.0. Backward-compatible feature additions → minor bump. Bumps the full version-sync surface (core/sdk Cargo.toml + core-dep pins, package.json + optionalDeps, pyproject + bootstrap __version__, Cargo.lock, npm lockfiles); scripts/check_release_versions.sh passes at 3.4.0. Adds the [3.4.0] CHANGELOG entry. No source changes — prep only.
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
2 participants
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.
Release prep for v3.4.0 (minor — backward-compatible feature additions). Version bump + CHANGELOG only; no tag is pushed by this PR — tagging
v3.4.0(which firesrelease.yml→ crates.io / npm / PyPI / GH Release) is a deliberate follow-up after this is merged.What ships in v3.4.0 (11 commits since v3.3.0)
AgentExecutorseam (framework/书安OS boundary),execute_steps_parallel/execute_pipeline/execute_steps_parallel_resumable, schema-forced step output, migratableWorkflowCheckpoint, and the Node + Python SDK grammar (parallel/pipeline/parallelResumable).LoopCheckpoint::ensure_loadable()(future-version rejection at the store layer).All backward-compatible (new types/methods, new optional fields, new
SessionStoremethods with default no-ops).Version-sync surface bumped 3.3.0 → 3.4.0
core/Cargo.toml,sdk/node/Cargo.toml(+ core-dep pin),sdk/python/Cargo.toml(+ core-dep pin),sdk/node/package.json(+ 6@a3s-lab/code-*optionalDeps),sdk/python/pyproject.toml,sdk/python-bootstrap/pyproject.toml+_bootstrap.py __version__,Cargo.lock, both npm lockfiles.scripts/check_release_versions.shpasses at 3.4.0. No source changes.After merge (the release steps, on your go)
Tag
v3.4.0at the merge commit and push it →release.ymlruns CI → publishes. (For v3.3.0 we hit a stale-test gate in the bootstrap publish; that's since fixed, and the full release pipeline went green.)