Skip to content

Commit

Permalink
release: v0.7.0
Browse files Browse the repository at this point in the history
This reverts commit 9b11630.
  • Loading branch information
EverlastingBugstopper committed Jun 9, 2022
1 parent ae49f35 commit bf81e06
Show file tree
Hide file tree
Showing 11 changed files with 490 additions and 404 deletions.
9 changes: 9 additions & 0 deletions .vscode/changelog.code-snippets
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
{
"changelog": {
"prefix": "changelog",
"body": [
"- **${1:Summary} - @${2:Author}, #${3:Issue #}, ${4:PR #}**\n\n ${5:Detailed description}\n\n"
],
"description": "changelog boilerplate"
}
}
27 changes: 27 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,33 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
## 📚 Documentation -->

# [0.7.0] - 2022-06-09

## 🚀 Features

- **Adds `readme fetch` and `readme publish` - @cy, #1128, #1141**

Adds support for fetching and publishing Apollo Studio graph variant READMEs with `rover readme publish` and `rover readme fetch` commands. Usage for these commands can be found by running `rover readme --help` and documentation can be found [on our docs site](https://www.apollographql.com/docs/rover/readmes).

## 🐛 Fixes

- **Fix the endpoint `rover-client` uses to fetch Apollo Studio's GraphQL schema- @EverlastingBugstopper, 1126**

As of v0.6.0, Rover sends all Apollo Studio requests to the new public platform API. When this change was introduced, we changed where we issued our GraphQL requests, but did not update the build step that fetches the schema which could lead to mismatched types. This is now fixed, fields in the public platform API match codegen.

- **Fix typo in the environment variable `rover-client` uses to fetch Apollo Studio's GraphQL schema - @EverlastingBugstopper, #1125**
`s/APOLLO_GPAPHQL_SCHEMA_URL/APOLLO_GRAPHQL_SCHEMA_URL`

## 📚 Documentation

- **Schema checks are now free - @StephenBarlow, #1131**

Update the documentation to remove references to schema checks being a paid feature, since [they are now free](https://www.apollographql.com/blog/announcement/platform/schema-checks-and-launches-are-now-available-for-free-in-apollo-studio/)!

- **Update ARCHITECTURE.md - @cy #1129**

Update and clarify a few points in ARCHITECTURE.md.

# [0.6.0] - 2022-05-03

> Important: 1 breaking change below, indicated by **❗ BREAKING ❗**
Expand Down
10 changes: 5 additions & 5 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ license-file = "./LICENSE"
name = "rover"
readme = "README.md"
repository = "https://github.com/apollographql/rover/"
version = "0.6.0"
version = "0.7.0"
default-run = "rover"

publish = false
Expand Down
43 changes: 31 additions & 12 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@
[![CircleCI Tests](https://circleci.com/gh/apollographql/rover.svg?style=svg)](https://app.circleci.com/pipelines/github/apollographql/rover?branch=main)
[![GitHub Release Downloads](https://shields.io/github/downloads/apollographql/rover/total.svg)](https://github.com/apollographql/rover/releases/latest)
[![Netlify Status](https://api.netlify.com/api/v1/badges/1646a37a-eb2b-48e8-b6c9-cd074f02bb50/deploy-status)](https://app.netlify.com/sites/apollo-cli-docs/deploys)

This is the home of Rover, the new CLI for Apollo's suite of GraphQL developer productivity tools.

Expand Down Expand Up @@ -37,7 +36,7 @@ rover graph publish --schema ./path-to-valid-schema test@cats
## Command-line options

```console
Rover 0.6.0
Rover 0.7.0

Rover - Your Graph Companion
Read the getting started guide by running:
Expand Down Expand Up @@ -66,25 +65,45 @@ USAGE:
rover [FLAGS] [OPTIONS] <SUBCOMMAND>

FLAGS:
--insecure-accept-invalid-certs Accept invalid certificates when performing HTTPS requests
--insecure-accept-invalid-hostnames Accept invalid hostnames when performing HTTPS requests
-h, --help Prints help information
-V, --version Prints version information
--insecure-accept-invalid-certs
Accept invalid certificates when performing HTTPS requests.
You should think very carefully before using this flag.
If invalid certificates are trusted, any certificate for any site will be trusted for use. This includes
expired certificates. This introduces significant vulnerabilities, and should only be used as a last resort.
--insecure-accept-invalid-hostnames
Accept invalid hostnames when performing HTTPS requests.
You should think very carefully before using this flag.
If hostname verification is not used, any valid certificate for any site will be trusted for use from any
other. This introduces a significant vulnerability to man-in-the-middle attacks.
-h, --help
Prints help information

-V, --version
Prints version information


OPTIONS:
--client-timeout <client-timeout> Configure the timeout length (in seconds) when performing HTTP(S) requests
[default: 30]
-l, --log <log-level> Specify Rover's log level [possible values: error, warn,
info, debug, trace]
--output <output-type> Specify Rover's output type [default: plain] [possible values:
json, plain]
--client-timeout <client-timeout>
Configure the timeout length (in seconds) when performing HTTP(S) requests [default: 30]

-l, --log <log-level>
Specify Rover's log level [possible values: error, warn, info, debug,
trace]
--output <output-type>
Specify Rover's output type [default: plain] [possible values: json, plain]


SUBCOMMANDS:
config Configuration profile commands
docs Interact with Rover's documentation
explain Explain error codes
graph Graph API schema commands
help Prints this message or the help of the given subcommand(s)
readme Readme commands
subgraph Subgraph schema commands
supergraph Supergraph schema commands
update Commands related to updating rover
Expand Down
Loading

0 comments on commit bf81e06

Please sign in to comment.