content-accord-versioning
Développeurs de logiciels Develops API versioning for Laravel applications using the gaiatools/content-accord package. Activates when installing or configuring Content Accord; declaring versioned route groups with Route::apiVersion(); configuring version resolution strategies (URI path, request header, Accept header, query string); setting up version aliases or chained resolvers; marking API versions as deprecated with sunset dates and deprecation links; enforcing sunset dates with 410 Gone responses; listening to VersionNegotiated or DeprecatedVersionAccessed events; using PHP attributes (#[ApiVersion], #[MapToVersion], #[ApiDeprecate], #[ApiFallback], #[ApiNegotiate]); accessing the resolved version via apiVersion() or NegotiatedContext; writing versioned API tests with InteractsWithApiVersion; or running the api:versions Artisan command. Make sure to use this skill whenever the user works with API versioning, version deprecation, content negotiation, or multi-version route management in Laravel, even if they don't explicitly mentio
2026-03-22