Product Decisions This Supports

Build vs. buy: Supports buying/adopting saade/cep-php rather than building and maintaining multi-provider Brazilian CEP lookup in-house. v2.0.0 reduces dependency surface by removing Saloon and standardizing on Guzzle.
Security and compliance roadmap: v2 clears security advisories tied to Saloon 3 and sets a minimum Guzzle version. This is primarily a maintenance/security release, not a feature release, so it helps dependency-scanning and procurement reviews.
Checkout/address-capture roadmap: Core behavior is unchanged for Cep::get(), Cep::race(), and provider-level get(), so existing product flows depending on CEP lookup do not need functional redesign.
Upgrade planning: Standard usage is low-effort to upgrade, but custom providers and test suites need migration work. PM should budget for engineering time if internal providers extend the package.
Testing and QA strategy: Saloon’s MockClient no longer intercepts requests; teams should move to Provider::useClient() with Guzzle test clients. This affects test infrastructure, not end-user behavior.
Operational flexibility: Provider::useClient() enables proxies, retries, and custom Guzzle configuration, which can support corporate network requirements or regional routing.

When to Consider This Package

Consider it when a Laravel/PHP product needs Brazilian CEP lookup with multiple providers, fallback/race behavior, and a simple DTO response without requiring provider API keys.
Consider upgrading from v1.2.0 when the app uses only Cep::get(), Cep::race(), or standard provider get() calls and can update Guzzle to ^7.15.2|^8.0.1.
Consider it when direct Guzzle usage is acceptable and the team does not need Saloon’s ecosystem, request classes, or connector abstractions.
Look elsewhere if the product needs official Correios/SIGEP authentication, address normalization or validation beyond CEP lookup, geocoding, non-Brazil postal-code support, contractual SLAs, or vendor support.
Be cautious if the app depends on Saloon transitively through this package, relies on removed Saade\Cep\Requests\* or RaceConnector, has custom providers built on Saloon request classes, or cannot upgrade Guzzle due to platform constraints.
Re-evaluate if provider reliability, terms of use, or compliance requirements become material; the package simplifies access but does not guarantee upstream provider correctness or availability.

To executives: v2.0.0 is a security and maintenance release, not a feature release. It removes Saloon, drops a dependency, and clears published security advisories. Core CEP lookup behavior is unchanged, so product risk is limited if we are on standard usage.
To engineering: Plan for Guzzle ^7.15.2|^8.0.1, migrate custom providers to request(), handleErrors(), and toDTO(), replace Saloon MockClient fakes with Provider::useClient(), and note that async methods no longer accept a connector. Use Provider::useClient() for proxies, retries, or test fakes.
Recommendation: Approve the upgrade for standard usage after updating Guzzle and migrating tests; treat custom-provider migration as scoped engineering work. Keep the package for CEP lookup, but reassess if custom provider complexity, compliance needs, or support requirements grow.