Github Client Laravel Package

Product Decisions This Supports

• Build vs. buy for GitHub integrations: v3.1.0 adds GitHub App authentication, which is typically costly to build correctly (JWT signing, installation tokens, permission scopes, token refresh/error states). This package can reduce custom auth work and security risk for teams adding GitHub App-based integrations.
• Roadmap readiness: Laravel 13 support lowers platform-upgrade risk and helps decide whether GitHub App support can ship in an upcoming release rather than being deferred.
• Feature prioritization: Use this release to evaluate GitHub App use cases such as organization/repository integrations, automated workflows, and enterprise/security-conscious customer requirements.
• Support-cost reduction: Improved connector authentication status and error guidance for strategy-based auth should reduce support triage and engineering escalations when GitHub App auth fails.
• Engineering onboarding: The new docs/ARCHITECTURE.md supports build-vs-buy review, code review, and onboarding for teams adopting or extending the package.
• Dependency governance: Saloon ^4.3 and php-jwt ^7 constraints should be checked against the product’s dependency policy and upgrade calendar before adoption.

When to Consider This Package

• Consider it when the product needs GitHub App authentication inside a Laravel application, especially if the team is already using or willing to use Saloon for HTTP integrations.
• Consider it when Laravel 13 compatibility is on the roadmap and the team wants to avoid maintaining custom GitHub App auth logic.
• Consider it when strategy-based connector authentication, clearer auth status, and better error guidance would materially reduce support burden.
• Look elsewhere if the product only needs simple OAuth or personal access token flows, if it is not Laravel-based, if it requires a broad multi-provider Git abstraction, or if the team cannot accept the Saloon/php-jwt dependency constraints.
• Validate before committing if the product requires vendor SLA support, long-term support guarantees, or compatibility with Laravel/Saloon/php-jwt versions outside the stated constraints.

How to Pitch It (Stakeholders)

• Executives: This release makes secure GitHub App integrations more practical in Laravel and reduces the need to build and maintain complex authentication flows internally. It also aligns with Laravel 13 and should lower integration support overhead.
• Engineering: v3.1.0 adds GitHub App auth, modernizes dependency support with Saloon ^4.3 and php-jwt ^7, fixes connector authentication status/error guidance for strategy-based auth, and adds architecture documentation. No breaking changes are called out in the release notes, but dependency compatibility should still be verified.
• Product managers: Treat this as a candidate for the integrations roadmap, especially where GitHub App support is a customer or enterprise requirement. Run a focused compatibility spike or pilot before broad adoption, then decide whether to adopt, wrap, or continue building in-house.