fix: standard site sync#2994
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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis change updates blog frontmatter validation to use ChangesStandard Site Sync Updates
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
thanks to Francisco for noticing: https://bsky.app/profile/frabarz.cl/post/3mpquscaios24 |
| } | ||
|
|
||
| const result = safeParse(BlogPostSchema, normalizedFrontmatter) | ||
| const result = safeParse(RawBlogPostSchema, normalizedFrontmatter) |
There was a problem hiding this comment.
(this is the only fix, the other changes are because I can't help myself but tidy up a tiny bit)
trueberryless
left a comment
There was a problem hiding this comment.
Looks good to me 🚀
Thanks for the quick fix!
Looks like after #1879 (probably) when the blog post avatars were done at build time, the schema that was being used in the standard site sync code for the blog post frontmatter validation wasn't updated, so it's been failing to sync. I ran this fix so the standard site is working in production, and this should keep it working for future posts.