Skip to content

Firebase/php-jwt conflicts with Roave/Security-advisories #244

@Lornz-

Description

@Lornz-

Hi! Thanks again for the awesome job you guys make to improve our experience with Wordpress and Gatsby.

I use composer to install and maintain all necessary plugins used in my current Wordpress instance. Lately, I made an update of all require dependencies and bumped to that one.

Problem

Current version of gatsby/wp-gatsby conflicts with roave/security-advisories dev-latest.

Problem 1
    - gatsbyjs/wp-gatsby[v2.3.0, ..., v2.3.3] require firebase/php-jwt ^5.2 -> satisfiable by firebase/php-jwt[v5.2.0, ..., v5.5.1].
    - roave/security-advisories dev-latest conflicts with firebase/php-jwt v5.5.1.
    - roave/security-advisories dev-latest conflicts with firebase/php-jwt v5.5.0.
    - roave/security-advisories dev-latest conflicts with firebase/php-jwt v5.4.0.
    - roave/security-advisories dev-latest conflicts with firebase/php-jwt v5.3.0.
    - roave/security-advisories dev-latest conflicts with firebase/php-jwt v5.2.1.
    - roave/security-advisories dev-latest conflicts with firebase/php-jwt v5.2.0.
    - Root composer.json requires roave/security-advisories dev-latest -> satisfiable by roave/security-advisories[dev-latest].
    - Root composer.json requires gatsbyjs/wp-gatsby ^2.3 -> satisfiable by gatsbyjs/wp-gatsby[v2.3.0, v2.3.1, v2.3.2, v2.3.3].

Steps to reproduce

composer update --with-dependencies

Proposed resolution

Update to the latest stable version of firebase/php-jwt which does not address multiple security vulnerabilities.
👉 https://github.com/gatsbyjs/wp-gatsby/blob/master/composer.json#LL33C6-L33C14

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions