docs: evise contribution process and add release process

Updated contribution guidelines to reflect the development and release processes.

Author: OrKoN

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: