-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(blog): fix pubdate of upcoming-cve-for-eol-versions #7403
Conversation
regressed in 8e5ef67 . this patch bring back the `T16` part to make it a valid Date string Signed-off-by: Masataka Yakura <[email protected]>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
apps/site/pages/en/blog/vulnerability/upcoming-cve-for-eol-versions.md
Outdated
Show resolved
Hide resolved
proposing a fast track on this small fix |
Lighthouse Results
|
this failure it interesting because it explicitly mentions an unparseable date. |
But why it's pass on windows ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I was able to build this branch locally (on MacOS) so I'm going to try rerunning CI here. Building on my Debian VM too 🤷
apps/site/pages/en/blog/vulnerability/upcoming-cve-for-eol-versions.md
Outdated
Show resolved
Hide resolved
…sions.md Co-authored-by: Augustin Mauroy <[email protected]> Signed-off-by: Brian Muenzenmeyer <[email protected]>
Description
This patch fixes the date of the Node.js — Upcoming CVE for End-of-Life Node.js Versions blog post by bringing back the
T16
part to make it a valid Date string.Regressed in 8e5ef67 .
Validation
Related Issues
Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.