Releases
1.6.0 Verified Release

AgentPlat 1.6.0 verified release

All 70 of 70 coordinated packages are published to npm at version 1.6.0 under latest. The protected publication and verification run 43266309287 (opens in a new tab) completed successfully from source commit e2fbca88 (opens in a new tab).

More LLM provider options

The existing @agentplat/model-openai-compatible adapter now includes Groq, Mistral, Azure OpenAI / Microsoft Foundry and Amazon Bedrock presets. They extend the existing typed chatModel, AgentPlat.ask and AgentPlat.configure contracts without introducing a new SDK dependency.

OpenAI, Google Gemini, Ollama and OpenRouter presets remain available, alongside the separate native Anthropic/Gemini adapters and OpenAI Agents SDK runner. See supported LLM providers for the full matrix, installation, credentials and endpoint examples.

Azure and Bedrock require an explicit API-root URL and bearer credentials. The Bedrock profile is Chat Completions, not Converse, InvokeModel or SigV4. Provider/model capabilities and parameter support vary.

Upgrade

npm install --save-exact @agentplat/framework@1.6.0 @agentplat/model-openai-compatible@1.6.0

Upgrade all selected @agentplat/* packages to the same exact coordinated version. The provider additions introduce no storage migration. Existing opt-in subsystem activation and migration requirements still apply; retain the 1.4 adoption and migration guidance when upgrading from older versions, and review the production guide (opens in a new tab).

The historical next tag can point to an older preview without these presets; install the stable version explicitly. See release channels.

What was verified

  • Full required CI, compatibility checks and clean packed consumers passed.
  • The approved 70 tarballs matched the dry-run artifacts byte-for-byte.
  • Registry verification passed integrity, ECDSA signatures, source/provenance fields, tags and clean consumers, including PostgreSQL and Node 22.
  • 42 provider contract tests and public declarations passed against the adapter installed from npm, with mocked HTTP responses.

A runner integration timeout passed on a CI job retry. npm initially accepted all publications while several versions were still processing; verification was rerun against the same immutable artifacts after all 70 became visible. No package was rebuilt or republished to repair that processing delay.

These checks establish package distribution and bounded integration behavior. They do not establish production-scale validation or live compatibility with every provider/model. Real provider calls require your own credentials, models and endpoint configuration; the joint smoke command is available for that next step.