lcobucci/content-negotiation-middleware

A PSR-15 middleware to handle content negotiation

content-negotiation-middleware's Issues

Bad fallback order

Given I have the following accepted formats:

• json, with mime json/application
• text with mimes: text/plain, and text/plain;version=0.0.4
  When i send a request with text/plain;version=0.0.5
  Then the response should be text.plain

What actually happens: we fall back on json.

It was not possible to parse your key, reason: error:0480006C:PEM routines::no start line

Good morning,

Can I get the configuration example using RS256 alg from:

$builder = new Builder();
$builder->sign(new \Lcobucci\JWT\Signer\Rsa\Sha256(), new Key('signkey.pem'));

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Use matchDepNames instead of matchPackageNames

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update PHPStan packages (phpstan/phpstan, phpstan/phpstan-phpunit, phpstan/phpstan-strict-rules)
• Update all non-major dependencies (actions/cache, codecov/codecov-action, infection/infection, jms/serializer, laminas/laminas-diactoros, middlewares/negotiation, twig/twig)
• Update dependency phpunit/phpunit to v10.5.20
• Update dependency phpunit/phpunit to v11
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

composer

composer.json

• php ~8.1.0 || ~8.2.0 || ~8.3.0
• fig/http-message-util ^1.1.5
• psr/http-factory ^1.0.2
• psr/http-message ^1.1 || ^2.0
• psr/http-server-middleware ^1.0.2
• infection/infection ^0.27
• jms/serializer ^3.26.0
• laminas/laminas-diactoros ^3.0.0
• lcobucci/coding-standard ^11.0
• league/plates ^3.5.0
• middlewares/negotiation ^2.1
• phpstan/extension-installer ^1.3.1
• phpstan/phpstan ^1.10.23
• phpstan/phpstan-deprecation-rules ^1.1.3
• phpstan/phpstan-phpunit ^1.3.13
• phpstan/phpstan-strict-rules ^1.5.1
• phpunit/phpunit ^10.4
• twig/twig ^3.6.1

github-actions

.github/workflows/coding-standards.yml

• actions/checkout v4
• shivammathur/setup-php v2
• actions/cache v4.0.0

.github/workflows/composer-json-lint.yml

• actions/checkout v4
• shivammathur/setup-php v2
• actions/cache v4.0.0

.github/workflows/mutation-tests.yml

• actions/checkout v4
• shivammathur/setup-php v2
• actions/cache v4.0.0
• codecov/codecov-action v4.0.0

.github/workflows/phpunit.yml

• actions/checkout v4
• shivammathur/setup-php v2
• actions/cache v4.0.0
• actions/checkout v4
• shivammathur/setup-php v2
• actions/cache v4.0.0

.github/workflows/release-on-milestone-closed.yml

• actions/checkout v4
• laminas/automatic-releases v1
• laminas/automatic-releases v1
• laminas/automatic-releases v1
• laminas/automatic-releases v1
• laminas/automatic-releases v1

.github/workflows/static-analysis.yml

• actions/checkout v4
• shivammathur/setup-php v2
• actions/cache v4.0.0

---

• Check this box to trigger a request for Renovate to run again on this repository

[PHP 7.4] Versioning of ext-json

Up to PHP 7.3, the json extension used to follow its own versioning.

Now, in PHP 7.4+, it is following the same as other extensions: PHP's version number:

• json: https://3v4l.org/1NjFH
• reflection: https://3v4l.org/ca9vS

For reference: php/php-src#4459

@lcobucci How can we solve this? Adding || ^7.4 or replacing it with * when declaring ext-json in the requirements of Composer?