From a1337a43a909a7f9f0ef7ef6ad61e09f6f7b2c4a Mon Sep 17 00:00:00 2001
From: kclowes <kclowes@users.noreply.github.com>
Date: Fri, 7 Nov 2025 15:40:21 -0700
Subject: [PATCH 1/2] Update README with versioning information

---
 README.md | 40 ++++++++++++++++++++++++++++++++++++----
 1 file changed, 36 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 01b4fb381..cca78f59a 100644
--- a/README.md
+++ b/README.md
@@ -37,15 +37,15 @@ will have all schema `#ref`s resolved.
 #### Building the docs
 
 Once you've updated something in the spec, you can use the docs generation tools
-to view the updated specs locally.  
+to view the updated specs locally.
 
 ```console
 $ npm run build:docs
 $ npm run watch
 ```
 
-The `watch` command starts a local webserver serving the docs in-browser at 
-`http://0.0.0.0:8000` and it rebuilds when you update something in the specs.  
+The `watch` command starts a local webserver serving the docs in-browser at
+`http://0.0.0.0:8000` and it rebuilds when you update something in the specs.
 Please reload the page to see your changes.
 
 ### Testing
@@ -69,7 +69,7 @@ directory against the specification.  There are two npm scripts to simplify this
 
 ```console
 $ npm run build:test
-$ npm run test 
+$ npm run test
 all passing.
 ```
 
@@ -129,6 +129,37 @@ A script is included in the source code which reads and validates the given sche
 $ npm run graphql:validate
 ```
 
+## Versioning
+
+Execution-apis follows [semantic versioning][semver].
+- Major releases will include breaking changes to the [rpc-compat hive tests][rpc-compat], and other backwards incompatible changes.
+- Minor releases will include new backwards-compatible features.
+- Patch releases will include internal changes that don't impact end users and backwards-compatible bugfixes, along with fixing test cases that don't match the spec.
+
+Examples of changes by version type:
+
+**Major:**
+- Adding new RPC methods
+- Changing the parameters or return type of an existing method in an incompatible way
+- Renaming fields in responses
+- Changing error codes or error response structures
+- Removing support for previously accepted input formats
+- Adding new fields to response objects
+
+**Minor:**
+- Removing an existing RPC method
+- Adding optional parameters to existing methods
+- Adding new error codes for previously uncovered edge cases
+- Introducing new capabilities while maintaining backward compatibility
+
+**Patch:**
+- Fixing typos or improving clarity in documentation
+- Correcting examples in the specification
+- Fixing test cases that don't match the spec
+- Improving validation rules without changing the API surface
+- Updating internal tooling or build processes
+
+
 ## License
 
 This repository is licensed under [CC0](LICENSE).
@@ -144,3 +175,4 @@ This repository is licensed under [CC0](LICENSE).
 [hive]: https://github.com/ethereum/hive
 [rpc-compat]: https://github.com/ethereum/hive/tree/master/simulators/ethereum/rpc-compat
 [test-gen]: docs/reference/tests.md
+[semver]: https://semver.org/

From b8eb9ba9ac87f17219d1d56bbe6703d37a0cb4f4 Mon Sep 17 00:00:00 2001
From: kclowes <kclowes@users.noreply.github.com>
Date: Fri, 5 Dec 2025 10:57:01 -0700
Subject: [PATCH 2/2] Address feedback

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index cca78f59a..492763f95 100644
--- a/README.md
+++ b/README.md
@@ -139,7 +139,7 @@ Execution-apis follows [semantic versioning][semver].
 Examples of changes by version type:
 
 **Major:**
-- Adding new RPC methods
+- Adding tests for a new RPC method
 - Changing the parameters or return type of an existing method in an incompatible way
 - Renaming fields in responses
 - Changing error codes or error response structures
@@ -147,16 +147,16 @@ Examples of changes by version type:
 - Adding new fields to response objects
 
 **Minor:**
-- Removing an existing RPC method
+- Removing tests for an existing RPC method
 - Adding optional parameters to existing methods
 - Adding new error codes for previously uncovered edge cases
 - Introducing new capabilities while maintaining backward compatibility
+- Fixing test cases that don't match the spec
 
 **Patch:**
 - Fixing typos or improving clarity in documentation
 - Correcting examples in the specification
-- Fixing test cases that don't match the spec
-- Improving validation rules without changing the API surface
+- Improving validation rules without changing the API
 - Updating internal tooling or build processes