bito-code-review[bot] commented on code in PR #41671:
URL: https://github.com/apache/superset/pull/41671#discussion_r3511124053


##########
docs/yarn.lock:
##########
@@ -7163,10 +7163,10 @@ doctrine@^2.1.0:
   dependencies:
     esutils "^2.0.2"
 
-docusaurus-plugin-openapi-docs@^5.0.2:
-  version "5.0.2"
-  resolved 
"https://registry.yarnpkg.com/docusaurus-plugin-openapi-docs/-/docusaurus-plugin-openapi-docs-5.0.2.tgz#f00028621deb9179065fe7d6a541256692ef941b";
-  integrity 
sha512-WCC2m6PpylXZfNga+ScelTG0a7jUGtbB9+AmbR9lUj93FPryTs8VHTMJ3fKtO0senJTWgOU3MDvZw0v+mE3ztA==
+docusaurus-plugin-openapi-docs@^5.1.0:
+  version "5.1.0"
+  resolved 
"https://registry.yarnpkg.com/docusaurus-plugin-openapi-docs/-/docusaurus-plugin-openapi-docs-5.1.0.tgz#9732f81f45a5bc126bcafcb150332b7623ddece7";
+  integrity 
sha512-ocRemE3KmdhhPKaow5hja1m1NLIPfNlfRYFt7pja+nG26Wlp0MEC9ERS99gSWEWaxU+txDFBpUXsxo7nGlk8ZA==

Review Comment:
   <div>
   
   
   <div id="suggestion">
   <div id="issue"><b>Lock file manual edit</b></div>
   <div id="fix">
   
   This lock file was manually edited, violating BITO.md rules [10438] and 
[12146]. Lock files should only be modified by running `yarn install` after 
updating `package.json`. Manual edits can corrupt integrity hashes and cause 
build failures across different environments. The package.json already has the 
correct version (`^5.1.0`), so regenerating the lock file via `yarn install` 
will produce the correct result with properly computed hashes.
   </div>
   
   
   </div>
   
   
   
   
   <small><i>Code Review Run #4cae6b</i></small>
   </div>
   
   ---
   Should Bito avoid suggestions like this for future reviews? (<a 
href=https://alpha.bito.ai/home/ai-agents/review-rules>Manage Rules</a>)
   - [ ] Yes, avoid them



-- 
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