chore(release): cut 0.1.27 - #370
Merged
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
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 0.1.27
Prepares the
v0.1.27release. Previous tag:v0.1.26(2026-07-27).Commit audit
All 19 commits in
v0.1.26..mainwere audited and given an explicit disposition — no subset, no silent omissions.capabilities.skillsin validate (#351)working_dir(#348)ensure_ascii=Falsein grader prompts (#356)SKILL.mdvalidation, injection bounds (#350)9 new changelog entries were written; the pre-existing
[Unreleased]entries were reviewed and kept as-is.The most significant gap: #215 landed the base
skills:feature (runtime.skills, per-agentskills:, the bundledconductorskill,capabilities.skills) with no changelog entry at all. Every existing skills entry — discovery, path entries, injection bounds, native loading — described refinements of a feature that had never been announced. That entry now leads theAddedsection.Changelog summary
Added — the
skills:feature and its bundledconductorknowledge base; skill discovery from installed personal/project/plugin locations; filesystem paths inskills:;runtime.skill_injectionbudgets;claude-agent-sdkMCP-server andworking_dirsupport; conservative scalar-wrapper unwrapping, recoverable non-object JSON, and theagent_parse_recoveryevent; dashboard sub-workflow nodes expandable before they run.Fixed — nested
arrayitem schemas now enforced inoutput:; MCP connections closed by their owning task; non-ASCII output no longer over-truncated before semantic validation; inline sub-workflow expansion follows the live run across loop-backs; every historical sub-workflow iteration reachable from the dashboard; no more tracebacks on handled fail-open paths; malformedSKILL.mdno longer fails silently; several parse-recovery fixes.Changed — the
claudeprovider now runs through Pydantic AI (adds a requiredpydantic-ai>=1.44.0dependency, andclaudenow streams);claude-agent-sdkloads skills natively and no longer inherits ambient MCP config;claude-agent-sdk>=0.2.82floor.Two entries carry explicit behavior-change callouts: nested array validation now fails workflows that were silently violating their own declared schema, and
claude-agent-sdkagents stop inheriting ambientCLAUDE.md/ settings / hooks.Validation
make check(ruff check + format + ty)make testmake validate-examplesLockfile note
uv lockre-resolution normalized away a redundant marker onsecretstorage's own dependency edges (cryptography/jeepneylostsys_platform != 'win32'). This is a no-op for the resolved install set:secretstorageis only reachable viakeyringundermarker = "sys_platform == 'linux'", where!= 'win32'is always true. Verified thatuv lockon unmodifiedmainis a no-op, so this surfaces only on re-resolution and is not a dependency change. Otherwiseuv.lockcontains only the project-version bump.Diff scope
Only
CHANGELOG.md,pyproject.toml, anduv.lock.Next step
Merging this PR will be followed by tagging the merge commit
v0.1.27and pushing it, which triggers.github/workflows/release.ymlto build and publish the GitHub Release.