Skip to content

Releases: apollographql/rover

v0.27.2

19 Feb 12:03
c31c00e
Compare
Choose a tag to compare

If using Rover with Connectors, you will need to specify APOLLO_ROVER_DEV_ROUTER_VERSION=2.0.0 when using rover dev

🐛 Fixes

  • Restore the ability to use environment or file references in the supergraph.yaml file - @jonathanrainer PR #2411

    In v0.26.3 and older you could use references such as ${env.HOST} or similar in the supergraph.yaml file, there
    was an oversight in the refactor and this was removed. This ability has now been restored.

🛠 Maintenance


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

17 Feb 10:24
a8495b9
Compare
Choose a tag to compare

If using Rover with Connectors, you will need to specify APOLLO_ROVER_DEV_ROUTER_VERSION=2.0.0-preview.X when using rover dev

🐛 Fixes

  • Create output parent directories if they do not already exist - @dotdat PR #2396

    One small regression with release of v0.27.0 was that if an output directory to supergraph compose was specified,
    but one of the parent directories did not exist, the command would fail. In previous versions the parent directories
    would be created instead and the command would succeed. This is now corrected and the previous behaviour restored.

  • Clean up how default subgraphs are defined in rover dev - @dotdat PR #2397 fixes #2394

    An issue has been reported where rover dev would prompt repeatedly for the subgraph name and URL despite the
    user having given those values already. This was due to multiple factors, including not accounting for CLI args in
    the default case and some faulty other faulty logic. This has now been restored.

  • Refine how composition produces artifacts for targets - @dotdat PR #2398 fixes #2393

    Due to changes in the supergraph binary from 2.9+, writing directly to a file is now supported. However,
    this feature is not available in earlier versions of supergraph. As such Rover should be responsible for
    orchestrating how the output from supergraph binary ends up in a file, rather than delegating that responsibility
    to the supergraph binary and thus being at the mercy of which version is used. This allowed a further refactor that
    eliminated complexity around composition outputs.

  • Ensure credentials are checked when needed and not before - @jonathanrainer PR #2400 fixes #2399

    Due to the rover dev refactor there were situations where credentials were being required when they were ultimately
    not being used. As such we stopped supporting the use case where no profile was defined and no APOLLO_KEY env var
    was provided, which is a very common pattern. This is now corrected.

🛠 Maintenance

📚 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.27.0

10 Feb 16:12
da1d077
Compare
Choose a tag to compare

Important: 3 potentially breaking changes below, indicated by ❗ BREAKING ❗

If using Rover with Connectors, you will need to specify APOLLO_ROVER_DEV_ROUTER_VERSION=2.0.0-preview.X when using rover dev

❗ BREAKING ❗

  • Make paths in supergraph.yaml resolve relative to the location of the supergraph.yaml file - @jonathanrainer PR #2119

    To support the new Apollo Language Server it is now the case that any paths expressed in the supergraph.yaml file will
    be resolved relative to the file's location on disk, not the location that Rover is running in, at the time.

  • Remove fed2 command - @aaronArinder PR #2222

    This was a deprecated, hidden, unused command that was for early Federation 2.0 testing. This command has not been
    invoked for a very long time.

  • Remove ability to start multiple rover dev sessions - @jonathanrainer PR #2352

    Now that Rover supports hot-reloading from supergraph.yaml files we've removed the ability to start multiple
    rover dev sessions, in multiple terminal windows, and have them communicate with each other. Because of this, you can no longer longer pass in the --schema argument to rover dev to provide a subgraph schema.

🚀 Features

🐛 Fixes

  • Stop Running Router with logs at TRACE level - @nmoutschen PR #2143

    We were running the Router at TRACE level logging, which was causing queries to not complete in some cases

  • Stop rover dev session if router binary crashes - @jonathanrainer PR #2382

    In the past we let the rover dev session continue if the router binary crashed, which led to a misleading state
    of affairs, this has now been fixed.

🛠 Maintenance

Read more

v0.27.0-rc.4

04 Feb 16:41
07c142a
Compare
Choose a tag to compare
v0.27.0-rc.4 Pre-release
Pre-release

New release candidate build, this features the big changes of the 0.27.0 release, including the Language Server and a refactor of the internals of rover dev. All testing that should be applied to this release candidate should focus on those two elements, and bugs raised in the previously communicated fashion so that we can iterate towards a 0.27.0 release.


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.27.0-rc.3

31 Jan 11:33
c0517c5
Compare
Choose a tag to compare
v0.27.0-rc.3 Pre-release
Pre-release

This beta release is now out of date. If you previously installed this release, you should reinstall and see what's changed in the latest release.


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.27.0-rc.2

29 Jan 13:52
6809dc2
Compare
Choose a tag to compare
v0.27.0-rc.2 Pre-release
Pre-release

This beta release is now out of date. If you previously installed this release, you should reinstall and see what's changed in the latest release.


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

27 Jan 12:18
3cbaece
Compare
Choose a tag to compare
v0.27.0-rc.1 Pre-release
Pre-release

This beta release is now out of date. If you previously installed this release, you should reinstall and see what's changed in the latest release.


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

22 Jan 13:37
e8e4b11
Compare
Choose a tag to compare
v0.27.0-rc.0 Pre-release
Pre-release

This beta release is now out of date. If you previously installed this release, you should reinstall and see what's changed in the latest release.


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

17 Dec 00:12
Compare
Choose a tag to compare

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

12 Dec 21:48
Compare
Choose a tag to compare
v0.26.3-rc.0 Pre-release
Pre-release

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.