v0.9.0-alpha.7

please see the latest release candidate

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.

v0.9.0-alpha.6

please see the latest release candidate

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.

v0.9.0-alpha.5

please see the latest release candidate

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.

v0.9.0-alpha.4

please see the latest release candidate

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.

v0.9.0-alpha.2

please see the latest release candidate

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.

v0.9.0-alpha.1

please see the latest release candidate

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.

v0.9.0-alpha.0

please see the latest release candidate

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.

v0.8.1

🐛 Fixes

• Fixes superfluous output in npm installer - @EverlastingBugstopper, #1200 fixes #1197 and #1198

  In 0.8.0, we released a fix for our npm installer that makes it compatible with yarn workspaces by reinstalling Rover if it doesn't exist. Unfortunately, that means that steps that rely on printing to stdout contained information about the installs in those invocations. This has been fixed.

📚 Documentation

• Adds documentation for the async checks feature introduced in 0.8.1 - @EverlastingBugstopper, #1193

---

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.

v0.8.0

🚀 Features

• Add new commands to use asynchronous checks API - @Y-Guo, #1139

  If you want to kick off a check without waiting for it to complete you can provide the --background flag to rover graph check or rover subgraph check. This will start the check in Apollo Studio. If your GitHub repo integrates with the Apollo Studio GitHub App, the check status will be updated on your GitHub branch. Using this flag can save you time and money with your CI provider.

• Improved error messages and logs for filesysten read/write - @EverlastingBugstopper, #1183

  Start using the saucer create for file system read/writes. This will provide better errors than the ones provided by std::fs e.g. permission denied os error (2) by providing context about which file rover is trying to read/write to. Every read/write/other filesystem operation will now be included in the --log info output.

🐛 Fixes

• Install rover before run if missing in npm package - @trevor-scheer, #1184 fixes #1178

• Don't retry 400 Bad Request errors - @EverlastingBugstopper, #1166

🛠 Maintenance

• Refactor command line argument parsing - @EverlastingBugstopper, #1155

• Improve schema downloading for codegen, when building rover - @EverlastingBugstopper, #1166

• Update rover to clap v3 - @EverlastingBugstopper, #1170 fixes #1165

• Add Apollo Studio integration tests - @EverlastingBugstopper, #1188

  We now run integration tests against Apollo Studio's platform API as part of our release pipeline.

📚 Documentation

• Update help message for rover subgraph introspect - @EverlastingBugstopper, #1169

  Previously the help message for rover subgraph introspect claimed to introspect from Apollo Studio Registry but it really introspects from a running subgraph endpoint.

• Add Jenkins CI/CD Documentation - @StephenBarlow, #1151

• Update, restructure, and add missing docs for existing rover commands - @StephenBarlow, #1154, #1157

• Update rover version in CI/CD docs - @rajington, #1177

• Fix broken anchors for fetching schema - @tchupp, #1176

v0.7.0

🚀 Features

• Adds readme fetch and readme publish - @cy, #1128, #1141

  Adds support for fetching and publishing Apollo Studio graph variant READMEs with rover readme publish and rover readme fetch commands. Usage for these commands can be found by running rover readme --help and documentation can be found on our docs site.

🐛 Fixes

• Fix the endpoint rover-client uses to fetch Apollo Studio's GraphQL schema- @EverlastingBugstopper, #1126

  As of v0.6.0, Rover sends all Apollo Studio requests to the new public platform API. When this change was introduced, we changed where we issued our GraphQL requests, but did not update the build step that fetches the schema which could lead to mismatched types. This is now fixed, fields in the public platform API match codegen.

• Fix typo in the environment variable rover-client uses to fetch Apollo Studio's GraphQL schema - @EverlastingBugstopper, #1125
  s/APOLLO_GPAPHQL_SCHEMA_URL/APOLLO_GRAPHQL_SCHEMA_URL

📚 Documentation

• Schema checks are now free - @StephenBarlow, #1131

  Update the documentation to remove references to schema checks being a paid feature, since they are now free!

• Update ARCHITECTURE.md - @cy #1129

  Update and clarify a few points in ARCHITECTURE.md.

---

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.