v0.0.26: provider profiles and capability-aware reasoning - #43
Merged
Conversation
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.
Summary
docs/and move implementation-only material out of the published docs treev0.0.26Compatibility fixes
tool_choicefor DeepSeek V4 thinking requests and keep tool-call assistant content non-nullgpt-5-proreasoning effort tohighValidation
pnpm release:preflightpnpm peers checkpnpm lintpnpm deps:checkpnpm check:i18npnpm test(46 tasks; web 533, store 719, runtime 860, server 716)pnpm --filter @covel/desktop build(web/main/preload build, server staging, native addon rebuild, and staged server smoke tests)pnpm exec prettier --check ...git diff --checkRelease plan
After this PR and the
mainCI run pass, merge it and tag the merge commit asv0.0.26. The tag triggers theBuild Desktopworkflow and publishes the GitHub release artifacts.The current release workflow intentionally produces unsigned macOS and Windows artifacts because signing and notarization secrets are not configured.