Skip to content

Commit 1fd797e

Browse files
committed
Release 1.0.0
1 parent 2d720ff commit 1fd797e

File tree

2 files changed

+21
-1
lines changed

2 files changed

+21
-1
lines changed

Cargo.toml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
[package]
22
edition = "2021"
33
name = "graph-gateway"
4-
version = "0.1.0"
4+
version = "1.0.0"
55

66
[profile.release]
77
lto = "thin"

RELEASE.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Release Process
2+
3+
1. Test the main branch using the [edgeandnode/local-network-environments](https://github.com/edgeandnode/local-network-environments) (`theodus/bash-time` branch)
4+
- Make sure that the gateway returns a correct response to a valid query
5+
- Run any other ad-hoc tests that are appropriate for the set of changes made since the last release
6+
2. Open a PR for the new release on [edgeandnode/local-network-environments](https://github.com/edgeandnode/local-network-environments)
7+
- Version the release based on [SemVer](https://semver.org/)
8+
- 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
9+
- Set the new version in `Cargo.toml`
10+
- Include release notes for changes since the last release
11+
- Rebase & Merge the PR
12+
- Create a new release via GitHub
13+
- Include the release notes from the PR
14+
- Tag the commit with the version string, prefixed with a `v`
15+
3. Open a PR on [edgeandnode/graph-network-infra](https://github.com/edgeandnode/graph-network-infra)
16+
- Update the staging (and testnet?) gateways to the new version
17+
- Update environment variables and Prometheus filters as necessary
18+
4. TODO: test against staging/testnet gateways...
19+
5. Open a PR on [edgeandnode/graph-network-infra](https://github.com/edgeandnode/graph-network-infra)
20+
- Update the mainnet gateway configs, making the same configuration changes as in step 3

0 commit comments

Comments
 (0)