feat(release): v0.1.2 — deterministic provider failures and two validation regimes #9
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/v0.1.2-release"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
MEDIUM:
Api config -> raw api strings no mapping
Centralise floating config variable, don't leave it floating mid-script.
@ -4,2 +4,3 @@"example-model": {"model": "openai/ggml-org/GLM-4.7-Flash-GGUF:Q8_0","model": "ggml-org/GLM-4.7-Flash-GGUF:Q8_0","api": "openai-compatible",api config becomes the regular api prefix (not openai-compatible just 'openai/' or 'openai')
@ -73,2 +79,4 @@)# How much of the last model reply rides an exhausted AgentReplyError message.REPLY_EXCERPT_CHARS = 500Floating config var, needs to be centralised somwehere
Not quite. Create a constants module for the ngen-weave-core library where values like this are defined and import it here. Do the same for the cli as a placeholder, and add a 'design' doc and add a line to the PRD under decisions.
@ -14,2 +14,4 @@from ngen_weave.errors import ConfigError, DataError, InfraError, ProviderErrorfrom ngen_weave.models.provider import CompletionAPI_PREFIXES = {"openai-compatible": "openai/"}Remove mapping, leave api config variable as raw api prefix. The most we'll do is check that it ends in '/' ('openai' is ok, just add on the '/' if missing).
Review feedback on PR 9: - models.json api is now the litellm prefix itself ('openai' or 'openai/'); the API_PREFIXES dialect mapping is gone and validation only rejects non-string/empty values. - Group REPLY_EXCERPT_CHARS with the other module constants in runner.py instead of leaving it floating after the imports. - Bump root pyproject to 0.1.2 (missed in C1).MEDIUM:
See reply to 'floating variable comment'