Skip to content

chore: version packages#60

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#60
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented May 15, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@wolfcola/devtools-bridge@1.2.0

Minor Changes

  • #57 4b2b276 Thanks @ryanbas21! - Add standalone Electron debugger with MCP integration

    New attachDebugger() API in devtools-bridge connects apps to the standalone
    debugger via WebSocket. Includes auto-launch, fetch/XHR/Node HTTP interceptors,
    and reconnection with session management. The standalone app runs as an Electron
    desktop app or headless MCP server (--mcp flag) with 10 tools for session
    inspection, event querying, diagnosis, and export.

Patch Changes

  • Updated dependencies [bc42519, 4b2b276]:
    • @wolfcola/devtools-core@1.2.0
    • @wolfcola/devtools-types@1.2.0

@wolfcola/dead-export-finder@1.2.0

@wolfcola/devtools-types@1.2.0

@wolfcola/eslint-plugin-treeshake@1.2.0

@wolfcola/treeshake-check@1.2.0

@wolfcola/devtools-core@1.2.0

Minor Changes

  • #57 4b2b276 Thanks @ryanbas21! - Add standalone Electron debugger with MCP integration

    New attachDebugger() API in devtools-bridge connects apps to the standalone
    debugger via WebSocket. Includes auto-launch, fetch/XHR/Node HTTP interceptors,
    and reconnection with session management. The standalone app runs as an Electron
    desktop app or headless MCP server (--mcp flag) with 10 tools for session
    inspection, event querying, diagnosis, and export.

Patch Changes

  • #61 bc42519 Thanks @ryanbas21! - Fix PAR inline-params rule falsely flagging client_id alongside request_uri

    The par:inline-params-with-request-uri diagnosis rule incorrectly treated client_id as a prohibited inline parameter. Per RFC 9126, client_id is required alongside request_uri in the authorization request after a PAR. Only truly prohibited params (redirect_uri, scope, etc.) now trigger the warning.

  • Updated dependencies []:

    • @wolfcola/devtools-types@1.2.0

@wolfcola/devtools-extension@1.2.0

Patch Changes

  • Updated dependencies [bc42519, 4b2b276]:
    • @wolfcola/devtools-core@1.2.0
    • @wolfcola/devtools-types@1.2.0

@wolfcola/devtools-standalone@1.2.0

Patch Changes

  • Updated dependencies [bc42519, 4b2b276]:
    • @wolfcola/devtools-core@1.2.0
    • @wolfcola/devtools-types@1.2.0

@wolfcola/docs-site@1.2.0

@wolfcola/changeset-sync-manifest@1.2.0

@github-actions github-actions Bot force-pushed the changeset-release/main branch from 9802d73 to 4842a8b Compare May 15, 2026 18:41
@github-actions github-actions Bot force-pushed the changeset-release/main branch from 4842a8b to 5a087a1 Compare May 15, 2026 19:38
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.

0 participants