Files
Codeman/.changeset
ArizeSky 2a3496b7b3 fix(webview): keep the browser's cookies on the websocket leg
The HTTP leg puts the server-held dsh credential in front of the browser's own
cookies; the upgrade leg replaced them with it. A managed dsh tab is trusted, so
its other cookies must survive there too. Filter the request the way the HTTP
leg does and merge the credential in front.

Order is the point: a `Cookie` header can name the same cookie twice, and the
first value is the one parsers keep, so appending the credential let a stale
browser copy of the same dsh cookie shadow the one the running process minted -
the tab would come back to the 401 this path exists to prevent. Both legs now
lead with it, and a route-level test asserts the bytes the upstream sees on the
upgrade, not only on the HTTP request.
2026-11-16 16:30:25 +08:00
..
2026-02-27 10:58:10 +01:00
2026-02-27 10:58:10 +01:00

Changesets

Hello and welcome! This folder has been automatically generated by @changesets/cli, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it in the repository.

What is a changeset?

A changeset is a piece of information about changes made in a branch or commit. It holds three bits of information:

  • What packages need to be released
  • What semver bump type each package should receive (major / minor / patch)
  • A summary of the changes

How do I create a changeset?

Run npx changeset or create a .md file in this directory with the following format:

---
"codeman": patch
---

Description of changes

The frontmatter specifies which package(s) to bump and the bump type. The body is the changelog entry.