From 1fd797ebe8f9ed5b1ac25104455d743b6f3896b6 Mon Sep 17 00:00:00 2001 From: Theo Butler Date: Mon, 13 Dec 2021 09:46:22 -0500 Subject: [PATCH] Release 1.0.0 --- Cargo.toml | 2 +- RELEASE.md | 20 ++++++++++++++++++++ 2 files changed, 21 insertions(+), 1 deletion(-) create mode 100644 RELEASE.md diff --git a/Cargo.toml b/Cargo.toml index fdcf6a57..b43e012d 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,7 +1,7 @@ [package] edition = "2021" name = "graph-gateway" -version = "0.1.0" +version = "1.0.0" [profile.release] lto = "thin" diff --git a/RELEASE.md b/RELEASE.md new file mode 100644 index 00000000..9d18e5b9 --- /dev/null +++ b/RELEASE.md @@ -0,0 +1,20 @@ +# Release Process + +1. Test the main branch using the [edgeandnode/local-network-environments](https://github.com/edgeandnode/local-network-environments) (`theodus/bash-time` branch) + - Make sure that the gateway returns a correct response to a valid query + - Run any other ad-hoc tests that are appropriate for the set of changes made since the last release +2. Open a PR for the new release on [edgeandnode/local-network-environments](https://github.com/edgeandnode/local-network-environments) + - Version the release based on [SemVer](https://semver.org/) + - Note that the data science team relies on the logging format, so any changes to existing log events, spans, or fields require a major version bump + - Set the new version in `Cargo.toml` + - Include release notes for changes since the last release + - Rebase & Merge the PR + - Create a new release via GitHub + - Include the release notes from the PR + - Tag the commit with the version string, prefixed with a `v` +3. Open a PR on [edgeandnode/graph-network-infra](https://github.com/edgeandnode/graph-network-infra) + - Update the staging (and testnet?) gateways to the new version + - Update environment variables and Prometheus filters as necessary +4. TODO: test against staging/testnet gateways... +5. Open a PR on [edgeandnode/graph-network-infra](https://github.com/edgeandnode/graph-network-infra) + - Update the mainnet gateway configs, making the same configuration changes as in step 3