chore(release): cut 0.1.36 - #504
Merged
Merged
Conversation
Finalizes the 0.1.36 release section, bumps the project version, and re-locks uv.lock. Also repairs a changelog defect introduced when #491 was rebased: the `conductor mcp serve` Added/Changed entries had landed inside the already-published [0.1.34] section, and the `mcp>=1.28.1,<2` Fixed entry inside [0.1.31]. Both are relocated verbatim into [0.1.36], where the work actually ships. 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.36 (previous tag:
v0.1.35).Commit audit
1 commit in
v0.1.35..main, fully audited:4e1ea0aconductor mcp serve— expose workflows as MCP tools (#432)Changelog
The audit found a defect: #491 was rebased onto a newer
mainand its changeloghunks landed inside already-published version sections rather than
[Unreleased], which was left empty:### Added(conductor mcp serve,workflow.mcp:block) and### Changed(
conductor status/conductor fleet listnow list recently-completed runs)had landed inside
## [0.1.34].### Fixed(mcp>=1.28.1,<2SDK bound) had landed inside## [0.1.31].Neither of those releases contains this work. All three blocks are moved
verbatim into the new
## [0.1.36]section — no wording changed, nothingadded or dropped — and the two released sections are restored to their
pre-#491 contents.
[0.1.34]no longer carries a duplicate### Added/### Changedpair.[Unreleased]is re-created empty, pointing atv0.1.36...HEAD.Release diff
Only the three release files:
CHANGELOG.md— 0.1.36 section finalized, misplacement repairedpyproject.toml—version = "0.1.36"uv.lock— re-locked withuv lock; the only change is theconductor-cliproject version (no dependency movement)Validation
All run against this branch and passing:
make check— ruff check, ruff format --check,ty check— all cleanmake test— 8194 passed, 58 skipped, 14 deselectedmake validate-examples— all examples valid (run because the release rangetouched
config/schema.pyand addedexamples/mcp-serve.yaml)git diff --check— cleanAfter merge
Merging this PR will be followed by tagging the merge commit
v0.1.36andpushing it, which triggers
.github/workflows/release.ymlto build and publishthe GitHub Release with its artifacts. The release is not created manually.