v0.2.0
π Features
-
Stabilize and document structured output - EverlastingBugstopper & StephenBarlow, issue/741 & pull/750/pull/752
Rover now has an
--output
parameter on every command that allows you to format Rover's output as well-structured JSON. Documentation for this feature can be found here. -
Add an error message when an input schema is empty - EverlastingBugstopper, issue/724 pull/726
If the input to
--schema
was ever empty, you'd get some fairly strange and unexpected error messages. Now, if you supply an empty schema via the--schema
argument, you'll get an error message informing you as such. -
Retry HTTP requests that respond with 500-599 errors - EverlastingBugstopper, issue/693 pull/727
Now, by default, Rover will retry any requests that result in an internal server error for up to 10 seconds.
π Fixes
-
Fix description encodings for introspection results - lrlna, issue/728 pull/742
Rover will now print descriptions for fields and inputs with correct spacing between triple quotes.
-
Don't panic on git remotes without an apparent owner - EverlastingBugstopper, issue/670 pull/731
Most git remotes include an author and a repo name, but this isn't always the case. One of Rover's dependencies assumed this was always the case, and would panic if it wasn't the case. This broke workflows for people who had these types of git remotes, but it won't anymore!
-
Properly send validation period as part of checks configuration - EverlastingBugstopper, issue/737 pull/738
-
Use correct cargo target for xtask commands - EverlastingBugstopper, issue/582 pull/730
Any
cargo xtask
command that relies on cargo targets will now determine a correct default if building on a machine with a CPU architecture other thanx86_64
π Maintenance
-
Add
cargo update
tocargo xtask prep
step - EverlastingBugstopper, issue/746 pull/747This change makes sure that our dependencies are automatically updated as part of our release process.
-
Further DRY StudioClient - EverlastingBugstopper, pull/753
This PR removed some small inconsistencies between HTTP requests made to Apollo Studio vs. those made for user introspection requests.
-
Use our GitHub bug report template for auto-generated panic reports - EverlastingBugstopper, issue/530 pull/732
π Documentation
-
Deploy Rover's docs at the root to account for main root-level redirect - trevorblades, pull/744
This is purely a change to how Rover's docs are rolled out, no user facing changes here.
This release was automatically created by Github Actions.
If you would like to verify that the binary you have downloaded was built from the source code
in this repository, you can compare the output of the commands below to the output of the same
commands on your machine.
MacOS
Binaries built for MacOS are signed and notarized, and are automatically verified with Gatekeeper.
Manual Verification:
$ sha256sum -b $(which rover) | cut -d ' ' -f1
38011ba3367b7c55ea3c55ba07822d5ef5fafff792368f9dbb43ce86cfbb5ec8
GNU Linux
Manual Verification:
$ sha256sum -b $(which rover) | cut -d ' ' -f1
906a92b3a78bce4fb6a20fb3d6e5ee5ad350799958294b4fce527dcea51f42a2
MUSL Linux
Manual Verification:
$ sha256sum -b $(which rover) | cut -d ' ' -f1
638b843f933f208d79de69dbdd21ed7a073850f674d112f4b0f568e493e8a930
Windows
Manual Verification:
PS> Get-Command rover
CommandType Name Version Source
----------- ---- ------- ------
Application rover.exe 0.0.0.0 C:\Users\username\.rover\bin\rover.exe
PS> Get-FileHash C:\Users\username\.rover\bin\rover.exe
Algorithm Hash Path
--------- ---- ----
SHA256 1972ca5136c913c2786b3bac5210c3c9fe78f353471c3fcf2ff1f8616cc06970 C:\Users\username\.rover\bin\rover.exe