Skip to content

Releases: apollographql/rover

v0.6.0

03 May 21:04
Compare
Choose a tag to compare

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

❗ BREAKING ❗

  • Use Apollo's Platform API - @pcarrier, #1074

    Rover now uses Apollo's Platform API instead of the old Studio API. The breaking change is that the hostname is now api.apollographql.com where it used to be graphql.api.apollographql.com, you may need to update your firewall rules. Other behavior should remain unchanged.

πŸ› Fixes

  • Fixes Input Value Definition block string encoding for descriptions. - @lrlna, #1116 fixes #1088

    Input values are now multilined when a description is present to allow for a more readable generated SDL.

πŸ›  Maintenance

  • Removes upper bound on Node engines for npm installer - @EverlastingBugstopper, #1120 fixes #1119

    Previously, Rover required that your node engine was between v14 and v17. We have removed the upper bound on this limit so you can now use Node 18 and any future versions.

  • Adds cargo xtask docs - @EverlastingBugstopper, #1118

    Developers of the Rover project can now run cargo xtask docs to spin up a local netlify server with your local docset. After running the command, you can navigate to http://localhost:8000/rover in your browser and changes you make to ./docs/source/**.md files will be updated automatically on save.

  • Updates dependencies - @renovate-bot, #1117

    node 16.14.2 -> 16.15.0
    npm 8.7.0 -> 8.8.0
    os_info 3.2 -> 3.3

  • Removes unused dependencies - @EverlastingBugstopper, #1113

  • Separate Studio client code from generalized GraphQL client code - @Geal, #1061

    Introduces the launchpad workspace crate which contains operations not specific to Apollo Studio such as:

    • launching GraphQL queries using reqwest
    • running an introspection query on a graph
    • transforming a JSON SDL to a schema

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.5.4

26 Apr 22:41
Compare
Choose a tag to compare

πŸš€ Features

  • Default rover supergraph compose to Federation 2 if a @link directive is found in a subgraph schema - @EverlastingBugstopper, #1097 fixes #1090

    When running rover supergraph compose, if supergraph.yaml refers to a subgraph that contains an @link directive and you haven't set the federation_version key, then Rover will use Federation 2 composition by default.

  • Output Federation version information when running rover supergraph compose - @EverlastingBugstopper, #1102

    When running rover supergraph compose, Rover will print the Federation version number that it is using. You can access this version string programatically by running the command with the --output json argument and accessing the federation_version field.

  • Accept - as valid supergraph.yaml to read config from stdin - @EverlastingBugstopper, #1092 fixes #525

    You can now run commands like cat supergraph.yaml | rover supergraph compose --config - much like you've always been able to do with the --schema argument in other Rover commands.

πŸ› Fixes

  • Really fixes v0.5.2/v0.5.3 broken npm installs - @EverlastingBugstopper

    It turns out that it's hard to test changes to npm installers without actually publishing to npm. In order to save burning another patch version I released v0.5.4-rc.0 to ensure that my changes would actually fix things.

  • Hides rover-fed2 from rover --help - @EverlastingBugstopper, #1091 fixes #1085

πŸ›  Maintenance

πŸ“š Documentation


note: the release notes for 0.5.2 have been copied here because 0.5.2 and 0.5.3 were both broken on npm


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.5.4-rc.0

26 Apr 22:13
Compare
Choose a tag to compare
v0.5.4-rc.0 Pre-release
Pre-release

This was a test release. Please refer to v0.5.4.

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.5.3

26 Apr 20:50
Compare
Choose a tag to compare

Sorry! This release did not work on npm. Please refer to v0.5.4. You can still download these binaries, they are functionally equivalent to v0.5.2 and v0.5.4.


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.5.2

26 Apr 20:12
Compare
Choose a tag to compare

Sorry! This release did not work on npm. Please refer to v0.5.4. You can still download these binaries, they are functionally equivalent to v0.5.3 and v0.5.4.


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.5.1

11 Apr 21:10
Compare
Choose a tag to compare

πŸ› Fixes

  • Return a hard error in CI when the ELv2 license is not accepted instead of hanging for eternity - @EverlastingBugstopper, #1082 fixes #1081

    If you ran rover supergraph compose with federation_version: 2 in CI - it would prompt you to accept the ELv2 license and hang waiting for the input for eternity. This is no longer the case and you will get a helpful error message detailing exactly what you need to do to never see the error again. For more details on the license, see our FAQ.

  • Removes extraneous debug statement - @EverlastingBugstopper, #1079

    In my rush this morning I missed the removal of an eprintln statement. It's gone now.


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.5.0

11 Apr 15:59
Compare
Choose a tag to compare

Important: X breaking changes below, indicated by ❗ BREAKING ❗

❗ BREAKING ❗

  • rover-fed2 has been deprecated - @EverlastingBugstopper, #1058

    rover fed2 supergraph compose has been deprecated. You should instead set federation_version: 2 in your supergraph.yaml to use Federation 2 with the rover supergraph compose command.

πŸš€ Features

  • rover supergraph compose optionally updates automatically - @EverlastingBugstopper, #1058 fixes #2046

    When running rover supergraph compose, Rover will automatically download the correct version of composition to use. In your supergraph.yaml files, you can specify federation_version: 1 or federation_version: 2 to always get the latest updates. You can pass the --skip-update flag to skip checking for an update. You can also specify an exact version if you'd like to pin your federation version, like so: federation_version: =2.0.0.

    Additionally, you can run rover install --plugin supergraph@latest-2 or rover install --plugin [email protected] to install a plugin ahead of time, which may be helpful in CI. For Federation 2, you'll have to accept the ELv2 license one time per machine. You likely want to set APOLLO_ELV2_LICENSE=accept in CI if you are using Federation 2.

  • Adds --insecure-unmask-key to rover config whoami - @EverlastingBugstopper, #1043 fixes #1023

    Previously, running rover config whoami would output your entire API key to the terminal. This is not the documented behavior, and it is insecure because someone could be sharing their screen while trying to debug and accidentally leak their API key.

    Now, rover config whoami will mask your API key when it prints to the terminal. You can override this behavior by passing the --insecure-unmask-key flag.

  • Retry on timeouts and connection errors - @ptondereau, #1014 fixes #790

    Rover will now automatically retry HTTP requests that fail due to timeouts or initial connection errors.

  • Define an HTTP agent for non-studio requests - @ptondereau, #1075 fixes #961

    Rover now sends a User-Agent header along with all requests, not just requests to Apollo Studio.

  • Adds support for HTTP(S) proxies in npm installer - @farawaysouthwest, #1067 fixes #899

    You can now install Rover from npm if you are behind a proxy.

πŸ› Fixes

πŸ›  Maintenance

  • Simplify rover subgraph fetch query - @EverlastingBugstopper, #1056 fixes #992

    rover subgraph fetch now uses a much more efficient query that only requests a single subgraph at a time rather than all of them. Yay GraphQL!

  • Upgrades apollo-encoder - @bnjjj, #1017 fixes #1010

πŸ“š Documentation


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.5.0-rc.1

05 Apr 20:58
Compare
Choose a tag to compare
v0.5.0-rc.1 Pre-release
Pre-release

πŸ› Fixes

see 0.5.0-rc.0 for the full release notes.

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.5.0-rc.0

05 Apr 19:54
3b4d4d3
Compare
Choose a tag to compare
v0.5.0-rc.0 Pre-release
Pre-release

Important: X breaking changes below, indicated by ❗ BREAKING ❗

❗ BREAKING ❗

  • rover-fed2 has been deprecated - @EverlastingBugstopper, #1058

    rover fed2 supergraph compose has been deprecated. You should instead set federation_version: 2 in your supergraph.yaml to use Federation 2 with the rover supergraph compose command.

πŸš€ Features

  • rover supergraph compose optionally updates automatically - @EverlastingBugstopper, #1058 fixes #2046

    When running rover supergraph compose, Rover will automatically download the correct version of composition to use. When you first install Rover, it will automatically download the latest composition function for Federation 1 and Federation 2. In your supergraph.yaml files, you can specify federation_version: 1 or federation_version: 2 to always get the latest updates. You can pass the --skip-update flag to skip checking for an update. You can also specify an exact version if you'd like to pin your composition function, like so: federation_version: =2.0.0-preview.9.

    Additionally, you can run rover install --plugin supergraph@latest-2 or rover install --plugin [email protected] to install a plugin ahead of time, which may be helpful in CI.

  • Adds --insecure-unmask-key to rover config whoami - @EverlastingBugstopper, #1043 fixes #1023

    Previously, running rover config whoami would output your entire API key to the terminal. This is not the documented behavior, and it is insecure because someone could be sharing their screen while trying to debug and accidentally leak their API key.

    Now, rover config whoami will mask your API key when it prints to the terminal. You can override this behavior by passing the --insecure-unmask-key flag.

  • Retry on timeouts and connection errors - @ptondereau, #1014 fixes #790

    Rover will now automatically retry HTTP requests that fail due to timeouts or initial connection errors.

πŸ› Fixes

πŸ›  Maintenance

  • Simplify rover subgraph fetch query - @EverlastingBugstopper, #1056 fixes #992

    rover subgraph fetch now uses a much more efficient query that only requests a single subgraph at a time rather than all of them. Yay GraphQL!

πŸ“š Documentation


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.4.8

15 Mar 20:48
Compare
Choose a tag to compare

πŸ› Fixes


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.