chore: stabilize Lunaria - #3268
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: npmx-dev/npmx.dev/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
💤 Files with no reviewable changes (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 5 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughLunaria no longer generates the HTML dashboard or its styles. It writes only ChangesLunaria output and release configuration
Priority: ➖ Normal Severity of issue fixed: Medium 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📊 Dependency Size ChangesWarning This PR adds 5.4 MB of new dependencies, which exceeds the threshold of 200 kB.
Total size change: 5.4 MB |
|
@coderabbitai full review |
✅ Action performedFull review finished. |
🔗 Linked issue
🧭 Context
This PR updates Lunaria to a stable version (released earlier this week) and also removes some dead code and fixes our canary translation status issue.
📚 Description
This PR updates Lunaria to
0.2. We were already targeting this version via pre-releases, so no code changes are necessary.I also removed the HTML output from Lunaria, since we just use the
status.jsonoutput for our custom translation tracker under https://i18n.npmx.dev/ (which redirects to https://main.npmx.dev/translation-status).I then noticed that https://main.npmx.dev/translation-status is not loading any status and figured that the reason is very likely that we use
fetch-depth: 2in thedeploy-canary.yml(see #2860). However, Lunaria always needsfetch-depth: 0to get the full history (no shallow clone). Let's see if this works 🤞