Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[0.2.0] - 2021-08-23
🚀 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.