Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix PHP Gherkin->Messages dependency #1943

Merged
merged 1 commit into from Mar 31, 2022

Conversation

ciaranmcnulty
Copy link
Contributor

When messages 18.0.0 was released, the constraint in gherkin/php/composer.json was changed to dev-main||^17.0,^18.0. This is incorrect because , is AND. It should have been dev-main||^17.0||^18.0

Pre-release of gherkin 23.0.0 removed the dev-main and left it as ^17.0,^18.0. Despite visual inspection by me this was approved and released. It is currently uninstallable as a result.

This removes the script that got rid of 'dev-main', fixes the constraint by removing ^17.0 as there is no php tag for that, and updates the messages script that adds new versions. Fixing this will require a 23.0.1 tag :/

The other issue was builds on main failing. This is because the local 'path repository' that makes gherkin install messages from local filesystem is unable to tell what version the checkout is. It's now forced to be 18.0.0 and only needs updating when gherkin breaks backward support for messages

When messages 18.0.0 was released, the constraint in gherkin/php/composer.json was changed to `dev-main||^17.0,^18.0`. This is incorrect because `,` is AND. It should have been `dev-main||^17.0||^18.0`

Pre-release of gherkin 23.0.0 removed the dev-main and left it as `^17.0,^18.0`. Despite visual inspection by me this was approved and released. It is currently uninstallable.

This removes the script that got rid of 'dev-main', fixes the constraint by removing `^17.0` as there is no php tag for that, and updates the messages script that adds new versions. Fixing this will require a `23.0.1` tag :/

The other issue was builds on main failing. This is because the local 'path repository' that makes gherkin install messages from local filesystem is unable to tell what version the checkout is. It's now forced to be 18.0.0 and only needs updating when gherkin breaks backward support for messages
@aurelien-reeves aurelien-reeves merged commit 9f3e4f5 into main Mar 31, 2022
@aurelien-reeves aurelien-reeves deleted the fix-php-gherkin-to-messages-constraints branch March 31, 2022 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants