#898 feat: use fetch for Flyte API HTTP client Pull request opened by ursucarina TL;DR Malicious publishes were reported for affected axios versions on npm; see axios#10604 and Step Security’s write-up. Moving HTTP calls to native fetch removes reliance on axios for those code paths and shrinks the vulnerable surface Type • Bug Fix • Feature • Plugin Are all requirements met? • Code completed • Smoke tested • Unit tests added • Code documentation added • Any pending items have an associated Issue Complete description Switches Flyte console API traffic from axios to the native fetch API Changes • `flyte-api`:

defaultFetchConfig

/

getFetchApiCall

(and related helpers); request errors normalized via

transformRequestError

. • `common`:

HttpRequestError

and proto/response decoding tweaks as needed for the new path. • `oss-console`: HTTP client wiring (axiosClient / data layer), hooks and models that performed GETs (useUserProfile, api.ts, admin paths), and error UI boundaries aligned with the new error shape. Tracking Issue n/a flyteorg/flyteconsole