Skip to content

Conversation

@trivikr
Copy link
Member

@trivikr trivikr commented Jun 10, 2025

Description

The images are not accurate on Node.js 18 EOL blog post.
The release schedule image should appear first, followed by EOL Node.js graph.

Validation

Check preview at https://nodejs-org-git-trivikr-patch-1-openjs.vercel.app/en/blog/announcements/node-18-eol-support

Related Issues

N/A

Check List

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

Signed-off-by: Trivikram Kamat <16024985+trivikr@users.noreply.github.com>
Copilot AI review requested due to automatic review settings June 10, 2025 04:25
@trivikr trivikr requested a review from a team as a code owner June 10, 2025 04:25
@vercel
Copy link

vercel bot commented Jun 10, 2025

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

Name Status Preview Updated (UTC)
nodejs-org ✅ Ready (Inspect) Visit Preview Jun 10, 2025 4:25am

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR corrects the order of the images in the Node.js 18 EOL blog post so that the release schedule appears before the EOL graph.

  • Swapped the image reference definitions to show the release schedule first, followed by the EOL graph.

@codecov
Copy link

codecov bot commented Jun 10, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.48%. Comparing base (1d0e88b) to head (c999093).
Report is 1 commits behind head on main.

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #7856      +/-   ##
==========================================
+ Coverage   75.44%   75.48%   +0.03%     
==========================================
  Files         101      101              
  Lines        8305     8305              
  Branches      218      218              
==========================================
+ Hits         6266     6269       +3     
+ Misses       2037     2034       -3     
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@avivkeller avivkeller added the fast-track Fast Tracking PRs label Jun 10, 2025
@avivkeller avivkeller added the github_actions:pull-request Trigger Pull Request Checks label Jun 10, 2025
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label Jun 10, 2025
@avivkeller
Copy link
Member

Fast track requested

@github-actions
Copy link
Contributor

github-actions bot commented Jun 10, 2025

Lighthouse Results

URL Performance Accessibility Best Practices SEO Report
/en 🔴 74 🟢 100 🟢 100 🟢 91 🔗
/en/about 🟢 100 🟢 96 🟢 100 🟠 82 🔗
/en/about/previous-releases 🟢 99 🟢 96 🟢 100 🟠 83 🔗
/en/download 🟢 98 🟢 100 🟢 100 🟢 91 🔗
/en/blog 🟢 100 🟢 100 🟢 96 🟢 92 🔗

@trivikr trivikr enabled auto-merge June 10, 2025 05:11
@trivikr trivikr added this pull request to the merge queue Jun 10, 2025
Merged via the queue into main with commit f93bd4b Jun 10, 2025
19 checks passed
@trivikr trivikr deleted the trivikr-patch-1 branch June 10, 2025 05:15
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.

4 participants