From d636e63ddf99ffab4847d06c9cf49b6fdfd32ea3 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Fri, 6 Mar 2026 09:16:31 +0100 Subject: [PATCH 1/2] docs: evise contribution process and add release process Updated contribution guidelines to reflect the development and release processes. --- CONTRIBUTING.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6125eed49..d16e51599 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -23,7 +23,7 @@ sign a new one. This project follows [Google's Open Source Community Guidelines](https://opensource.google/conduct/). -## Contribution process +## Development process ### Code reviews @@ -53,6 +53,14 @@ completed: features (we want to avoid features that offer some tools but cannot be used successfully to debug things). +### Release process + +Releasing `chrome-devtools-mcp` is automated by GitHub actions. Reviewing, +testing and landing a PR titled `chore(main): release chrome-devtools-mcp` +is sufficient to release a new version. The release PR is automatically +opened if there are any changes on the main branch that show up in the +changelog. + ## Installation Check that you are using node version specified in .nvmrc, then run following commands: From 7b48c6654de3b013028bf09591a93bcee485edd3 Mon Sep 17 00:00:00 2001 From: Alex Rudenko Date: Fri, 6 Mar 2026 11:00:17 +0100 Subject: [PATCH 2/2] Update CONTRIBUTING.md Co-authored-by: Mathias Bynens --- CONTRIBUTING.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d16e51599..596fe74d9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -55,11 +55,10 @@ completed: ### Release process -Releasing `chrome-devtools-mcp` is automated by GitHub actions. Reviewing, -testing and landing a PR titled `chore(main): release chrome-devtools-mcp` -is sufficient to release a new version. The release PR is automatically -opened if there are any changes on the main branch that show up in the -changelog. +Releasing `chrome-devtools-mcp` is automated by GitHub Actions. To release a new +version, [search for a PR titled `chore(main): release chrome-devtools-mcp`](https://github.com/ChromeDevTools/chrome-devtools-mcp/pulls?q=is%3Apr+is%3Aopen+%22chore%28main%29%3A+release+chrome-devtools-mcp%22) +and review, test, and land it. The release PR is automatically opened if there +are any changes on the main branch that show up in the changelog. ## Installation