Skip to content

Conversation

@Qard
Copy link
Contributor

@Qard Qard commented Oct 30, 2018

CI is failing right now because express-graphql 0.7.x was released and, while the tav ranges tried to test against them, the patch range did not apply the patch, resulting in test failures.

@Qard Qard self-assigned this Oct 30, 2018
@Qard Qard requested a review from watson October 30, 2018 00:48
Copy link
Contributor

@watson watson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The existing tav tests for 0.6, should just be locked to ^0.6.12 (as per my 4 suggestions).

Then we should add a new set of tav tests to test the >=0.7.0 range below. There should be 3 groups, one for each of the peer dependencies graphql@^0.12.0, graphql@^0.13.0, and graphql@^14.0.0 which are the ones supported by the >=0.7.0 range.

@Qard Qard force-pushed the update-express-graphql branch from 0482ee9 to 3cc0b5d Compare October 30, 2018 19:17
Copy link
Contributor

@watson watson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume v0.7.0 is excluded from the tav tests because it's broken.

@watson watson merged commit 3958964 into elastic:master Oct 31, 2018
@Qard Qard deleted the update-express-graphql branch October 31, 2018 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants