- What can I build with helgesverre/mistral in a Laravel application?
- It is a Laravel wrapper for the Mistral AI API that lets you send chat completions, generate embeddings, and stream responses through an expressive PHP interface. It includes configurable models and facades so you can integrate Mistral into Laravel services without hand-rolling HTTP calls. Check the README for the exact endpoint surface and DTOs before designing around it.
- How do I install helgesverre/mistral with Composer?
- Install it with Composer using composer require helgesverre/mistral and let Laravel auto-discover the service provider. Publish the package configuration, set your Mistral API credentials in the environment, and review the README for any required facade aliases. Confirm the Laravel and PHP constraints in composer.json before adding it to an existing application.
- How do I configure models and API credentials for helgesverre/mistral?
- The package provides publishable configuration and configurable models, so model names and credentials should be set through config and environment variables rather than hard-coded. Publish the config file and follow the README for the exact key names and supported model options. This keeps chat, embedding, and streaming calls consistent across environments.
- Which Laravel and PHP versions does helgesverre/mistral v3 support?
- The v3 release notes do not state the exact Laravel and PHP version matrix, so confirm the constraints in the package's composer.json and README. Match those constraints against your platform before committing to a rollout window, especially if you are upgrading from v2. The package is a standard Laravel service-provider package, but the supported matrix is authoritative only in its metadata.
- How do I upgrade helgesverre/mistral from v2 to v3?
- Treat v3 as a hard major upgrade because it moves the underlying Saloon dependency from ^3.x to ^4.0. Upgrade saloonphp/saloon and saloonphp/laravel-plugin to ^4.0 first, resolve Composer conflicts in isolation, then bump helgesverre/mistral to ^3.0. Include the fixture rename and full test-suite run in the same atomic pull request so lockfile changes and test fixes land together.
- How do I fix failing Mistral tests after upgrading to helgesverre/mistral v3?
- The v3 release changes Saloon fixture names from dot-separated to slash-separated paths, for example MockResponse::fixture('chat.create') becomes MockResponse::fixture('chat/create'). Search the repository for fixture calls and update them repo-wide, including any dynamically assembled fixture paths. Re-run the full suite and smoke-test against a sandbox endpoint so test-layer failures are not misread as API integration failures.
- Can I use helgesverre/mistral v3 if another package requires Saloon 3?
- No, Saloon v3 and v4 cannot coexist in one Composer install, so any package pinning saloonphp/* to ^3.x blocks the upgrade until it moves. Inventory Saloon usage across your applications and composer.lock files before scheduling the change. If a partial rollout is unavoidable, gate the package version with an environment-specific Composer constraint rather than trying to mix Saloon majors.
- Is helgesverre/mistral suitable for production chat and embedding workloads?
- Yes, it is designed for chat completions, embeddings, and streaming through a typed, testable Saloon connector layer. Saloon is per-request client code, so this release has no runtime scaling implications; capacity concerns remain outbound request volume and rate limits against the Mistral API. Add operational monitoring for retries, auth failures, and upstream rate limits before customer-facing rollout.
- What are alternatives to helgesverre/mistral for calling Mistral AI from Laravel?
- Alternatives include calling the Mistral HTTP API directly with Laravel's HTTP client, using another PHP SDK or Saloon connector, or building a small custom connector tailored to your endpoints. Choose based on how much Laravel integration you need, such as facades, publishable config, and fixture-based testing. Also check the alternative's Saloon major constraint if your application already depends on saloonphp/*.
- How should I plan maintenance for helgesverre/mistral?
- Expect to track Saloon majors because this package wraps a foundational HTTP connector, so plan a recurring upgrade cadence rather than a one-off migration. Add a standing dependency-review checkpoint for saloonphp/* and this package so the next bump is anticipated. Document the slash-separated fixture convention in onboarding and test-scaffolding templates to prevent new tests from reintroducing the old dot convention.