Skip to content
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

Merged
merged 3 commits into from
Jan 24, 2025

Conversation

myakura
Copy link
Contributor

@myakura myakura commented Jan 12, 2025

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

  • I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • I have run npm run format to ensure the code follows the style guide.
  • I have run npm run test to check if all tests are passing.
  • I have run npx turbo build to check if the website builds without errors.
  • I've covered new added functionality with unit tests if necessary.

regressed in 8e5ef67 . this patch bring back the `T16` part to make it a valid Date string

Signed-off-by: Masataka Yakura <[email protected]>
@myakura myakura requested a review from a team as a code owner January 12, 2025 05:25
Copy link

vercel bot commented Jan 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Jan 23, 2025 10:58pm

@bmuenzenmeyer bmuenzenmeyer added the fast-track Fast Tracking PRs label Jan 13, 2025
@bmuenzenmeyer
Copy link
Collaborator

proposing a fast track on this small fix

Copy link
Contributor

github-actions bot commented Jan 13, 2025

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🟠 83 🟢 100 🟢 100 🟢 91 🔗
/en/about 🟢 100 🟢 100 🟢 100 🟢 91 🔗
/en/about/previous-releases 🟢 100 🟢 100 🟢 100 🟢 92 🔗
/en/download 🟢 95 🟢 100 🟢 96 🟢 91 🔗
/en/blog 🟢 100 🟢 100 🟢 96 🟢 92 🔗

Copy link
Contributor

github-actions bot commented Jan 13, 2025

Unit Test Coverage Report

Lines Statements Branches Functions
Coverage: 88%
87.55% (739/844) 74.14% (238/321) 86.58% (142/164)

Unit Test Report

Tests Skipped Failures Errors Time
182 0 💤 0 ❌ 0 🔥 5.735s ⏱️

@bmuenzenmeyer
Copy link
Collaborator

this failure it interesting because it explicitly mentions an unparseable date.

@AugustinMauroy
Copy link
Member

this failure it interesting because it explicitly mentions an unparseable date.

But why it's pass on windows ?

Copy link
Member

@mikeesto mikeesto left a 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 🤷

@AugustinMauroy
Copy link
Member

Wait ??? On my safari console I got "invalid date"

Capture d’écran 2025-01-17 à 09 31 12

…sions.md

Co-authored-by: Augustin Mauroy <[email protected]>
Signed-off-by: Brian Muenzenmeyer <[email protected]>
@bmuenzenmeyer bmuenzenmeyer added the github_actions:pull-request Trigger Pull Request Checks label Jan 24, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jan 24, 2025
@bmuenzenmeyer bmuenzenmeyer added this pull request to the merge queue Jan 24, 2025
Merged via the queue into nodejs:main with commit bad2b2f Jan 24, 2025
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fast-track Fast Tracking PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants