Skip to content

Add changeset for RPC transport#647

Open
aron-cf wants to merge 2 commits intomainfrom
rpc-changelog
Open

Add changeset for RPC transport#647
aron-cf wants to merge 2 commits intomainfrom
rpc-changelog

Conversation

@aron-cf
Copy link
Copy Markdown
Contributor

@aron-cf aron-cf commented Apr 28, 2026

  • Update AGENTS.md with improved changeset guidance
  • Add changeset for new rpc transport

Open in Devin Review

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 28, 2026

🦋 Changeset detected

Latest commit: 7dfe5fe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@cloudflare/sandbox Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@aron-cf aron-cf changed the title rpc changelog Add changeset for RPC transport Apr 28, 2026
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 2 potential issues.

View 2 additional findings in Devin Review.

Open in Devin Review

Comment on lines +5 to +14
Introduce new `rpc` transport to consolidate `http` and `websocket` transports.

The intention is to replace `http` and `websocket` transports with a single implementation.

- No sub-request limitations (currently affects the `http` transport).
- No limit on write file size (currently affects both `http` and `websocket` transports).

To enable the transport set `SANDBOX_TRANSPORT` to `rpc` in your wrangler config.

A `ReadableStream` instance can now be passed to `sandbox.writeFile()` when using the `rpc` transport to avoid the 32mb file limit.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changeset violates AGENTS.md rule: content exceeds single paragraph limit

The AGENTS.md rule at line 344 states: "Keep it short. Each changeset entry should aim to be a couple of sentences, no more than a single paragraph." The changeset in .changeset/introducing-rpc-transport.md contains four separate paragraphs of prose plus a bullet list (in addition to the code example). This is far more than the mandated single paragraph. The "Good" example in AGENTS.md:352-355 demonstrates a two-sentence format. The changeset text (lines 5-14, excluding the code block) should be condensed into a single short paragraph.

Suggested change
Introduce new `rpc` transport to consolidate `http` and `websocket` transports.
The intention is to replace `http` and `websocket` transports with a single implementation.
- No sub-request limitations (currently affects the `http` transport).
- No limit on write file size (currently affects both `http` and `websocket` transports).
To enable the transport set `SANDBOX_TRANSPORT` to `rpc` in your wrangler config.
A `ReadableStream` instance can now be passed to `sandbox.writeFile()` when using the `rpc` transport to avoid the 32mb file limit.
New `rpc` transport removes sub-request limitations and file size limits. Set `SANDBOX_TRANSPORT` to `rpc` in your wrangler config to enable. A `ReadableStream` can now be passed to `sandbox.writeFile()` to stream large files.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.


Introduce new `rpc` transport to consolidate `http` and `websocket` transports.

The intention is to replace `http` and `websocket` transports with a single implementation.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changeset violates AGENTS.md rule: includes internal technical implementation details

The AGENTS.md rule at line 343 states: "Focus on the problem solved and the benefit, not technical implementation details." Line 7 of the changeset — "The intention is to replace http and websocket transports with a single implementation" — describes an internal implementation strategy (consolidating transports) rather than a user-facing benefit. This mirrors the "Bad" example in AGENTS.md:349-350 ("Add WebSocket transport for request multiplexing over a single connection") which is also flagged as technical/internal-focused.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants