bito-code-review[bot] commented on PR #35865:
URL: https://github.com/apache/superset/pull/35865#issuecomment-3454938550

   <details open>
     <summary><strong>Interaction Diagram by <a 
href="https://bito.ai#sequence_diagram";>Bito</a></strong></summary>
   
   ```mermaid
   sequenceDiagram
   participant YarnPM as Yarn Package Manager
   participant PkgJson as docs/package.json<br/>πŸ”„ Updated | ●●○ Medium
   participant SwaggerUI as swagger-ui-react<br/>πŸ”„ Updated | ●●○ Medium
   participant SwaggerClient as swagger-client<br/>πŸ”„ Updated | ●●○ Medium
   participant ApiDom as @swagger-api/apidom<br/>πŸ”„ Updated | ●●● High
   participant DocSite as API Documentation Site
   Note over PkgJson: Version bumps: swagger-ui-react 
5.29.5→5.30.0<br/>swagger-client 3.35.7→3.36.0, apidom beta→rc.1
   YarnPM->>PkgJson: Resolve dependencies
   PkgJson->>SwaggerUI: Fetch 5.30.0
   PkgJson->>SwaggerClient: Fetch 3.36.0
   PkgJson->>ApiDom: Fetch 1.0.0-rc.1 packages
   SwaggerUI->>SwaggerClient: Depends on swagger-client 3.36.0
   SwaggerClient->>ApiDom: Depends on apidom-core, apidom-error, etc.
   DocSite->>SwaggerUI: Import & render API specs
   ```
   Critical path: Yarn Package Manager -&gt; docs/package.json -&gt; 
swagger-ui-react -&gt; swagger-client -&gt; @swagger-api/apidom -&gt; API 
Documentation Site
   
   
   > **Note:** Dependency updates for API documentation: swagger-ui-react and 
swagger-client bump to latest versions, with @swagger-api packages 
transitioning from beta to release-candidate. Impacts documentation build and 
API rendering in docs site.
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to