fix: authenticate GitHub API requests and remove outdated release TODOs - #252
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughRemoved obsolete TODO notes from the Webpack 5 release post. Added error handling for unsuccessful GitHub API responses. Updated 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Build failure on docs commit!!! |
…andle fetch errors
|
Oh, we actually forget to spread the object ;) |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 0bb4765f-e0a1-4490-8edd-6a80d52e3cf0
📒 Files selected for processing (2)
scripts/markdown/readmes.mjsscripts/utils/fetch.mjs
🔗 Linked repositories identified
CodeRabbit considers these linked repositories for cross-repo context during reviews:
webpack/webpack(auto-detected)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review.
Summary
This PR removes outdated
(TODO: ...)notes in the Webpack 5 release blog post, and spreads thegithubHeadersobject to attach GitHub authentication headers, preventing API rate limiting and CI script failures.Verification on docs:
I double-checked the Webpack 5 source code:
optimizationBailoutis inModuleGraph(notChunkGraph).getChildIdsByOrdersandgetChildIdsByOrdersMapare remain in theChunk.Summary by CodeRabbit
Documentation
Bug Fixes