chore(release): cut 0.1.35 - #500
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 preparation for v0.1.35 (previous release: v0.1.34, 2026-08-24).
Commit audit
All 4 commits in
v0.1.34..mainwere audited; every one has an explicit disposition.6cdbabb9760b72conductor doctorglyphs resolved per console encodingd3c43a1c363ee7~against the passed-in home, not the environmentCommit 4 is deliberately not in the changelog: it has no user-visible behaviour change in production (
homeis alwaysPath.home(), which is whatexpanduseralready resolved to). It was an internal correctness fix that unbroke the red Windows CI onmain.Changelog corrections
Two entries were misfiled into the already-released
[0.1.34]section and have been moved into[0.1.35]:### Removedheading under[0.1.34], but PR refactor(engine): remove dead workflow lifecycle hooks (#476) #480 merged 2026-08-25 — after v0.1.34 was published on 2026-08-24. Verified against the tag:HooksConfigstill exists atv0.1.34and is removed only onmain.conductor doctorcp1252 fix (conductor doctor table output dies part-written on a cp1252 console (hardcoded glyphs) #401) had been appended to[0.1.34]'s### Fixed, but PR fix(cli): resolve doctor's glyph set per console encoding (#401) #469 merged 2026-08-27. Verified:_resolve_glyphsdoes not exist atv0.1.34at all.Both entries claimed shipped-in-0.1.34 behaviour that v0.1.34 users do not have. The
[0.1.34]section now accurately reflects that tag's contents.The plugin-flavor entry (#497) was already correctly under
[Unreleased].Release section
[0.1.35]contains Removed (lifecycle hooks) and Fixed (doctor glyphs, plugin flavor). A fresh empty[Unreleased]compare link was added above it.Validation
All run against this branch, rebased on
c363ee7:make check— ruff check, ruff format,ty checkall passmake test— 7745 passed, 58 skippedmake validate-examples— pass (schema changed in the release range)git diff --check— cleanDiff scope
Only the three release files:
CHANGELOG.md,pyproject.toml,uv.lock. The lockfile change is theconductor-cliproject version only (1 line); no dependencies moved.Next step
Merging this PR will be followed by pushing the
v0.1.35tag at the merge commit, which triggers.github/workflows/release.ymlto build and publish the GitHub Release with its artifacts.