-
Notifications
You must be signed in to change notification settings - Fork 94
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
v0.1.1 - non-federated graph errors for previously functioning subgraph checks #553
Labels
Comments
Some further info from my local machine
Update rover from v0.1.0 to v0.1.1
Run same
|
hi @setchy ! Thanks so much for the report. Are you able to run this command with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Since the release of @rover 0.1.1 today, we've had errors for any new
rover subgraph check
commands as executed via Bitbucket Pipelines. These commands have been working fine without error on many previous versions of rover and are identical to the steps documented under Rover Bitbucket PipelinesSteps to reproduce
Run a
rover subgraph check {graph-name}@{variant-name} --name {subgraph-name} --schema {schema-path}
Expected result
Actual result
Environment
Run
rover info
and paste the results hereIf you can't run
rover info
for some reason, please provide as much of the following info as possible:rover --help
): 0.1.1The text was updated successfully, but these errors were encountered: