feat: 0.11.0 — provider typespec parity + grok-4.20 catalog#33
Merged
chrisohalloran merged 2 commits intomainfrom Apr 21, 2026
Merged
feat: 0.11.0 — provider typespec parity + grok-4.20 catalog#33chrisohalloran merged 2 commits intomainfrom
chrisohalloran merged 2 commits intomainfrom
Conversation
Adds `@type config` and `@spec complete/3` + `@spec stream/4` to every provider that implements the `Alloy.Provider` behaviour, matching the pattern already in `Alloy.Provider.Codex`: - `Alloy.Provider.Anthropic` - `Alloy.Provider.Gemini` - `Alloy.Provider.OpenAI` - `Alloy.Provider.OpenAICompat` - `Alloy.Provider.XAI` Purely a tooling-visibility improvement — no runtime change. Users who run dialyzer now get type-checking at call sites for all six providers (previously only Codex). The config types faithfully track the options documented in each provider's moduledoc, so they double as machine-readable contracts. `Alloy.Provider.XAI.config/0` is aliased to `Alloy.Provider.OpenAI.config/0` since XAI is a thin wrapper that inherits the full OpenAI config surface. Bundles the already-merged grok-4.20 catalog entry (PR #32) and bumps the version to 0.11.0. Minor bump — the new typespecs are user-visible via dialyzer even though not breaking. Verified: `mix format --check-formatted`, `mix compile --warnings-as-errors`, `mix credo --strict`, `mix test` (569/569), `mix dialyzer` (0 errors).
- Version string in the opening example: 0.10.0 → 0.11.0 - Deps pin: `~> 0.10` → `~> 0.11` - Four xAI code examples now use `grok-4.20-0309-reasoning` (the current API frontier per docs.x.ai/developers/models, catalogued in this release) instead of `grok-4` - Providers table xAI row: add `grok-4.20-0309-reasoning` and `grok-4.20-multi-agent-0309` to the example models column
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
1 participant
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
Batches two changes into the `0.11.0` release:
The CHANGELOG and version bump reflect both.
Why 0.11.0 (minor, not patch)
The new typespecs are user-visible via dialyzer — consumers who type-check their config maps will now get errors at call sites for typos and shape mismatches on all six providers. That's not strictly breaking (invalid configs failed at runtime before), but it's visible enough to warrant a minor bump rather than a patch.
Provider typespec parity
Before this PR, only `Alloy.Provider.Codex` had typespecs on its public API:
After this PR, all six match:
Config types faithfully track the moduledoc
Each provider's `@type config` enumerates every option documented in its moduledoc, with proper types:
Test plan
Release flow
Merge this PR, then:
```
git tag v0.11.0
git push origin v0.11.0
```
That triggers `publish.yml` which tests and publishes to Hex.
🤖 Generated with Claude Code