Skip to content

Spec v0.1.11

Latest
Latest

Choose a tag to compare

View all tags
@AI10x AI10x released this 17 Oct 01:07
v0.1.11
4cef2b7

Source release from dev fixing Optimize's Azure Responses endpoint handling. Release versions use Git tags; package manifests remain at 0.1.0.

Changes

  • Accept Azure gateway routing prefixes before /openai/v1 and /openai/v1/responses, preserving the prefix when constructing the request URL.
  • Retain resource-root endpoint support, Azure API-key authentication, HTTPS enforcement, credential/query/fragment rejection, and redirect prevention.
  • Cover prefixed base and full Responses URLs, trailing slashes, dotenv loading, and invalid endpoints with regression tests; update endpoint and release documentation.

The commit includes the requested wording:

Optimization Button fixed error in confusion of optimization spec filepath (convergence to upper-bound limiting)

The uploaded absolute-path handoff and dotenv credential loading remain unchanged from prior releases. The convergence algorithm is unchanged; a measured plateau is not proof of an upper bound or global optimum.

Validation

  • Polled the preceding spec build to terminal exit status 0.
  • Independently reran all 46 Python optimizer tests successfully.
  • Reviewed source, tests, and documentation with no blocking findings; diff whitespace checks passed.
  • Rust integration tests and backend rebuild were not run because Cargo is unavailable in this environment.
  • No live SSH/model-provider call or browser suite was run for this Python-only code change.

Rebuild and restart the backend to activate its updated embedded optimizer. Unrelated output logs, session artifacts, dotenv files, and Python caches are excluded. No binary assets are attached.

Full changes: v0.1.10...v0.1.11

Assets 2
Loading