chore: bump version to 0.4.0#34
Merged
Merged
Conversation
Contributor
Author
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.

Context
Bumps
outfitter-dispatchto0.4.0after the stable refs / flat CLI work landed onmainvia PR #33.What changed
pyproject.tomlfrom0.3.0to0.4.0.uv.lockto match.How to test
uv run dispatch --version->dispatch 0.4.0just check->190 passed, 9 deselected, build and package contents check passed, anddist/outfitter_dispatch-0.4.0.*was built.DISPATCH_HOME:dispatch newcreated a real managed Codex thread ongpt-5.3-codex-spark.UV_CACHE_DIR=/tmp/dispatch-smoke-uv-cache uv run dispatch --versionand observeddispatch 0.4.0.dispatch schema sendincludesref,id,title, andmanagedin the output schema.dispatch sendfollow-up returned the identity-richActionAck, and the worker replied viadispatch tail.Risks / notes
uv runbecause UV needed a writable cache, then fell back to the older globally installeddispatch 0.2.1. The successful smoke usedworkspace-writeonly to permit a temp UV cache; no repo files were changed by the smoke worker.