chore(release): v0.5.41 - #128
Merged
Merged
Conversation
Ships the projects-write fix merged in #127. Until this release the fix is on main and nowhere else: jobd-deploy resolves releases/latest, so the broker keeps running 0.5.40 -- the release that INTRODUCED the crash, cut at 080dc11. Every `job projects set` against a foldable name traceback until this deploys. Pure release commit: version bump plus the changelog roll, no source changes. The bump touches five files (pyproject.toml, server.json x3, CITATION.cff, uv.lock, CHANGELOG.md). tests/test_cli_projects_write.py also contains the string 0.5.40 and is deliberately NOT bumped -- it is prose in a module docstring naming the release whose fold introduced the bug. 1246 passed, 9 skipped. Claude-Session: https://claude.ai/code/session_01GL72BtcPf4cmENDLFXy5xi
musharna
marked this pull request as ready for review
August 31, 2026 16:58
musharna
added a commit
that referenced
this pull request
Sep 2, 2026
Ships the projects-write fix merged in #127. Until this release the fix is on main and nowhere else: jobd-deploy resolves releases/latest, so the broker keeps running 0.5.40 -- the release that INTRODUCED the crash, cut at 080dc11. Every `job projects set` against a foldable name traceback until this deploys. Pure release commit: version bump plus the changelog roll, no source changes. The bump touches five files (pyproject.toml, server.json x3, CITATION.cff, uv.lock, CHANGELOG.md). tests/test_cli_projects_write.py also contains the string 0.5.40 and is deliberately NOT bumped -- it is prose in a module docstring naming the release whose fold introduced the bug. 1246 passed, 9 skipped.
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
1 participant
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.
Ships the projects-write fix from #127.
Until this release the fix is on main and nowhere else —
jobd-deployresolvesreleases/latest, so the broker keeps running 0.5.40, the release that introduced the crash. Everyjob projects setagainst a foldable name tracebacks until this deploys.Pure release commit: version bump + changelog roll, no source changes.
tests/test_cli_projects_write.pystill contains the string0.5.40and is deliberately not bumped — it is prose naming the release whose fold introduced the bug.1246 passed, 9 skipped.
https://claude.ai/code/session_01GL72BtcPf4cmENDLFXy5xi