This PR adds the request and response bodies into the context if they
are available and in a readable format.

---------

Co-authored-by: Nicholas Roscino <nroscino@chromium.org>
Co-authored-by: Nikolay Vitkov <34244704+Lightning00Blade@users.noreply.github.com>

This will allow us to manually call the run so the latest GitHub Action
config from main is picked up.
It also updates the Publisher to the latest version, and extracts the
command in vars so its easier to
update and read.

I think this will help people structure what is needed more easily.
The current version does not restrict anything so it's as close as a
no-op as possible

TODO: I need to look in how to add the screenshot part back.

Action was wrong, and the jobs were not stop depending on the input.

The first job was skipped so the second one that was marked as `needs:
npm-publish` was getting skipped as well
I think this should fix that.

Closes #304


https://github.com/modelcontextprotocol/registry/blob/main/docs/reference/server-json/CHANGELOG.md#migration-checklist-for-publishers

Closes #271

Use the native issue time that was recently added.

#326)

#320
Issue:
It would be very useful to have the ability to simulate offline network
conditions directly through the MCP emulate_network command, similar to
how it's possible in DevTools.
Currently, the command doesn’t support an Offline state, which limits
testing for PWA and offline-first web applications. Adding this option
would make it easier to automate and validate offline behavior through
MCP scripts or tools that rely on this API.

Solution
- Add 'Offline' option to throttlingOptions for simulating offline
network conditions
- Update emulate_network tool to handle offline mode with proper network
conditions
- Update documentation to include offline option and usage instructions
- Add test coverage for offline network emulation functionality
- Enable testing of PWA and offline-first web applications through MCP

Includes fixes for Chrome installation detection on Windows and WSL

I heard several people had issues installing the project locally due to
not noticing the difference between node version required to run vs to
build the project. This improvement aims at helping in those cases and
hopefully preventing small waste of time.

Co-authored-by: Piotr Paulski <piotrpaulski@chromium.org>

Fixes a bug where the output contained "this is a high level summary"
before then outputting the call frame / network format information
before then outputting the trace summary.

With this commit, we now output the summary & insights before ending
with the format information.

🤖 I have created a release *beep* *boop*
---


##
[0.7.0](chrome-devtools-mcp-v0.6.1...chrome-devtools-mcp-v0.7.0)
(2025-10-10)


### Features

* Add offline network emulation support to emulate_network command
([#326](#326))
([139ce60](139ce60))
* add request and response body
([#267](#267))
([dd3c143](dd3c143))


### Bug Fixes

* ordering of information in performance trace summary
([#334](#334))
([2d4484a](2d4484a))
* publishing to MCP registry
([#313](#313))
([1faec78](1faec78))
* use default ProtocolTimeout
([#315](#315))
([a525f19](a525f19))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).