ci(publish-python): twine upload --verbose + tag guard#43
Merged
Conversation
The v3.2.0 release fails on the second wheel upload to PyPI with a generic 400 Bad Request. twine swallows the response body unless --verbose is set; this commit adds the flag so the next retry surfaces the actual reason from PyPI.
ZhiXiao-Lin
added a commit
that referenced
this pull request
May 29, 2026
Closes the coverage gaps surfaced by an adversarial coverage audit across the new orchestration layer. +21 unit tests, +4 real-LLM integration tests (all run green against .a3s/config.acl), plus a small fix and a de-flake. Unit: - combinators: empty inputs, zero concurrency_hint (\.max(1) clamp), first-stage None, resumable ignores checkpointed-but-dropped specs, and resumable re-runs all when the checkpoint is unreadable (future version). - store: FileSessionStore workflow-checkpoint round-trip, crash-atomic no-temp-leftovers, and future-version rejection through both stores. - schema coercion FAILURE path (previously untested): demote-to-failure with the marker, isolation from a sibling in a fan-out, and failed-run-skips-coercion. - #31 persisted-schema fuzz extended to AgentStepSpec / StepOutcome / WorkflowCheckpoint (round-trip stability + forward-compat unknown-field tolerance) — the cross-node-migration types were previously excluded. - Python SDK conversion helpers (py_to_step_spec / step_outcome_to_py) and the PythonPipelineStage bridge (None-stops, raise-fails-closed, snake_case ctx['previous']) — previously zero coverage. Real-LLM (#[ignore], .a3s/config.acl): pure parallel fan-out of distinct agents (order + per-branch sentinels), multi-item pipeline (no-barrier shape with >1 item), the actual RESUME path (completed step served from checkpoint, only the rest run live), and a nested/array output_schema. Fix: the resumable combinator now distinguishes Ok(None) from a load Err and logs a warning before re-running from scratch (was a silent swallow). De-flake: the pipeline real-LLM tests no longer assert on stage-2 output *content* (some models return an empty final turn for a one-word instruction); chaining is proven by reaching stage 2 + the deterministic mock test. Co-authored-by: Claude <claude@anthropic.com>
ZhiXiao-Lin
added a commit
that referenced
this pull request
May 30, 2026
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. Co-authored-by: Claude <claude@anthropic.com>
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.
Why
The v3.2.0 release (`release.yml` run #26338778339) fails on the second wheel upload to PyPI with a generic `400 Bad Request`. twine swallows the response body unless `--verbose` is set, so we currently can't see the actual reason.
Changes
Plan
After this PR merges to main, dispatch `publish-python.yml` manually from main against the v3.2.0 wheels, capture the verbose output, then iterate on the actual root cause.