Repository navigation
Release 0.6.1: discover relevance, InsufficientBalanceError, footprint default 25 - #50
Merged
Merged
Conversation
The platform now decides consensus itself and no longer runs AI result enhancement, so both discover request fields are ignored. The regenerated DiscoverParams drops them; passing either still sends it and raises a DeprecationWarning, scoped to discover so contacts consensus is untouched. CLI help for --consensus, --enhanced and --variance says what the server does now.
The dev spec's ProspectingRunResponse gained question, the ProspectingOpenQuestion a needs_input run waits on; without it the contract check against dev fails for every PR.
…us-enhanced Soft-deprecate discover consensus and enhanced
…equest only asks to top up
InsufficientBalanceError for 403 INSUFFICIENT_BALANCE
The API is replacing variance with relevance: three stop points picked by estimated ICP fit (MAX_RELEVANCE, BALANCED, MAX_COVERAGE) instead of six fit-percentage tiers, and no automatic stop when it is left unset. Variance stays accepted and the API maps its old values onto relevance. DiscoverParams gains relevance, sent only when set so the SDK still works against an API that has not deployed it. Variance leaves the model the way consensus and enhanced did: passing it still sends it and raises a DeprecationWarning naming relevance. The CLI adds --relevance to discover and bulk companies and keeps --variance for existing scripts, with help that points at --relevance. The generated request file is edited by hand ahead of the platform deploy; regenerate it from the production spec once relevance is live.
…t default 25 Bump the SDK and CLI to 0.6.1, date the changelog section and add the API's new min_digital_footprint default of 25. The platform release is live, so request models are regenerated from the production spec: relevance no longer needs the hand edit, and question_seq leaves PENDING_PROPERTIES. gen_requests.py --check and check_contract.py are clean against prod.
Release 0.6.1
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.
relevancereplaces the deprecatedvariance;consensusandenhancedare deprecated on discover.InsufficientBalanceErrorfor 403 INSUFFICIENT_BALANCE.min_digital_footprintdefault of 25; request models regenerated from the production spec.
The PR appears safe to merge; no actionable issues were found.Summary
Releases SDK and CLI version 0.6.1.
No actionable issues found. PR #48's callers remain compatible. Tests were inspected, not run.
Reviews (1) · Last reviewed commit: "Add the discover consensus and enhanced ..." · Reviewed by Greptile