v0.16.0

Important: 1 potentially breaking change below, indicated by ❗ BREAKING ❗

❗ BREAKING ❗

• Adds linter results to check commands - @david-castaneda, #1637

  rover graph check and rover subgraph check both include lint warnings and errors depending on your graph's configuration. The JSON output of checks command has changed in this version, so if your scripts depend on --format json and pipe to jq, they will need to be updated. Note: all Rover commands output a json_version field when running with --format json that your scripts should check before attempting to access specific fields. The check output json_version has been bumped from 1 to 2 as a part of this release. See the documentation for the new lint feature for more information.

• router.yaml files and supergraph.yaml files now fully support environment variable expansion - @dbanty, #1629 fixes #1552 and #1578

  Specifying environment variables in router.yaml or supergraph.yaml files (for rover dev and/or rover supergraph compose) is now supported for all strings defined in the YAML file. Rover will evaluate any existing values using the ${} syntax, which may cause errors with existing config.

🚀 Features

• New rover {sub}graph lint commands - @swcollard, #1620

  Rover now has two new commands: rover graph lint and rover subgraph lint. The options mirror their respective check commands and provides wonderfully formatted lint results in your terminal. See the documentation for the new lint feature for more information.

• Support for supergraph.yaml files in rover dev - @dbanty, #1627 fixes #1258

  The same file that you can pass to rover supergraph compose is now supported by the --supergraph-config argument in rover dev. This change should make it easier to run a local router with multiple subgraphs without needing to manage multiple terminal sessions.

---

This release was automatically created by CircleCI.

If you would like to verify that the binary you have downloaded was built from the source code in this repository, you can compute a checksum of the zipped tarball and compare it to the checksums that are included as release artifacts.

Binaries built for MacOS are signed, notarized, and automatically verified with Gatekeeper.