fusion/.changeset/fix-github-discussions-force-mode.md at fee920d366d6866fb8cb06e690f634445b080772

Files

Phil Larson c1bc95c1db fix(dashboard): honor forced GraphQL transport (#2353 )

## Summary
- honor `forceMode` for GraphQL queries and mutations
- keep token-backed Discussion operations on the selected token
transport even when `gh` is authenticated
- add regression coverage for forced-token category lookup, errors, and
Discussion creation

## Test plan
- `CI=true pnpm --filter @fusion/dashboard exec vitest run
src/__tests__/github-discussions.test.ts
src/__tests__/github-forced-mode.test.ts
src/__tests__/github-pr-threads.test.ts`
- `CI=true pnpm build`


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Bug Fixes**
* GitHub Discussions GraphQL operations now consistently honor the
selected transport/authentication mode.
* Forced token-based transport correctly applies to discussion queries
and mutations (including discussion creation).
* Missing required authentication is now reported instead of falling
back to an unauthenticated path.
* **Tests**
* Added a test covering discussion creation using forced token-based
GraphQL transport.
* **Release**
  * Shipped as a patch release of the Fusion library.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-07-20 08:49:28 -07:00

239 B

Raw Blame History

@runfusion/fusion

@runfusion/fusion
patch

summary: Honor forced GitHub transport selection for GraphQL discussion queries and mutations. category: fix dev: Keep Discussion GraphQL operations on the explicitly selected token or gh CLI transport.

239 B Raw Blame History

239 B

Raw Blame History