v0.10.0
Important: 1 potentially breaking change below, indicated by ❗ BREAKING ❗
❗ BREAKING ❗
-
Fix implementation of
--headerargument - @EverlastingBugstopper, #1369 fixes #1365This change tightens up usage of the
--headerargument used forintrospectcommands by disallowing previously valid (but undocumented) usage like this:--header "Header-1: value" "Header-2: value". After this change, you must conform to what we have in the documentation, which indicates separate instances of the--headerargument for each header, like so:--header "Header-1: value" --header "Header-2: value".
🚀 Features
-
Provide prebuilt binaries for ARM devices - @EverlastingBugstopper, #1356 fixes #582
As of this release,
rover.apollo.devdelivers prebuilt binaries from our GitHub release for ARM devices. Most notably this means that Docker on M1 devices should work out of the box. You should be able to replace any custom builds in your tooling pipeline with a call to the official curl installer. -
Report downstream check task results - @sachindshinde, #1385
When running
rover subgraph checkcommands, if the proposed schema would cause downstream failures (i.e. with contracts), those failures are now reported in the check response. -
Faster
rover supergraph compose- @EverlastingBugstopper, #1392 fixes #992Rover now resolves all subgraph schemas in parallel when running
rover supergraph composeon asupergraph.yamlfile. This should improve the speed to compose large supergraphs significantly. This change also drastically improves error handling by reporting all issues with resolving subgraph schemas (and informing you which schema(s) failed to resolve) rather than exiting on the first failed schema resolution. -
Add
--polling-intervaltorover dev- @patrick91, #1377 fixes #1221You can now set
--polling-intervalwhen runningrover devto change the frequency of introspection poll requests for subgraphs that don't provide the schema from the file system with the--schemaargument. -
Adds
--skip-update-checkto skip the once-per-day update check - @Tsing, #1396 fixes #1394Once per day, Rover checks if there is a new version available for update and notifies the user if there is. There is now a flag you can pass to disable this check:
--skip-update-check. -
Respect the
NO_COLORenvironment variable - @chnn, #1360roverwill not use color in any output when executed with theNO_COLORenvironment variable set totrue.
🛠 Maintenance
-
Updates from clap v3 to clap v4 - @EverlastingBugstopper, #1404 fixes #1400
This release updated the command line argument parsing library to major version 4. There should be no noticeable compatibility issues with this update, only lighter binaries. The look and feel of the main
rover --helpoutput has changed to a neutral color palette along with this change. -
Updates Rust to 1.65.0 - @EverlastingBugstopper, #1399
-
Updates node dev-dependencies - @renovate, #1204 and zs#1398
-
Remove dependency on the
saucercrate - @EverlastingBugstopper, #1402 -
Updates
introspector-gadgetto 0.2.0 - @EverlastingBugstopper, #1386 -
Only cache dependencies in CI, not whole
/target- @EverlastingBugstopper, #1387 -
Use
engine@maininstead ofengine@currentto fetch the API schema - @EverlastingBugstopper, #1368 -
Use
lycheeas a link checker instead of npm - @ptondereau, #1328 fixes #1306We now use a Rust-based link checker to check the links in the Rover repository instead of a node-based link checker (that was much more flaky).
-
Describe latest federation versions in
./latest_plugin_versions.json- @EverlastingBugstopper, #1363When you run
rover supergraph compose, the latest version of composition is automatically downloaded to your machine, these latest version numbers are now stored in./latest_plugin_versions.jsonin the Rover repo. -
Rename
apollo-headers toapollographql-headers - @jsegaran, #1411
📚 Documentation
-
Update studio algolia key to graphos - @trevorblades, #1384
-
Fix some broken links - @StephenBarlow, #1376
-
Fix a typo in the migration guide instructing the use of
checkinstead ofpublish- @EverlastingBugstopper, #1364 fixes #1361
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.