content(blog/events): add trip report of 2026 London summit#8840
content(blog/events): add trip report of 2026 London summit#8840legendecas wants to merge 1 commit intonodejs:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR SummaryLow Risk Overview Reviewed by Cursor Bugbot for commit c50d485. Bugbot is set up for automated code reviews on this repo. Configure here. |
👋 Codeowner Review RequestThe following codeowners have been identified for the changed files: Team reviewers: @nodejs/nodejs-website Please review the changes when you have a chance. Thank you! 🙏 |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 04ad983. Configure here.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8840 +/- ##
=======================================
Coverage 73.87% 73.87%
=======================================
Files 105 105
Lines 8883 8883
Branches 326 326
=======================================
Hits 6562 6562
Misses 2320 2320
Partials 1 1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Pull request overview
Adds a new events blog post documenting the 2026 London Node.js Collaboration Summit, expanding the site’s historical archive of summit trip reports.
Changes:
- Introduces a new markdown blog post with frontmatter (date/category/title/layout/author).
- Adds a structured recap of summit sessions plus a “Thanks” section and reference links.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Next 10 | ||
|
|
||
| In this session, [Jacob Smith][] started an on-site review of the questions that would be asked in the [Next-10 survey for 2026](https://github.com/nodejs/next-10/issues/369), including suggestions to existing questions, questions and options to add or remove, and recent AI discussions. | ||
|
|
||
| ### New Release Schedule |
There was a problem hiding this comment.
The post jumps directly to ### headings without a preceding ## section, which is inconsistent with other Collab Summit trip reports and results in an incorrect heading hierarchy (and potentially inconsistent styling/TOC). Consider promoting these session headings to ## (and reserving ### for sub-sections where needed).
|
|
||
| This is a reflection of the current Node.js volunteer-based maintenance and an effort to keep the Node.js project sustainable in the long run. When it comes to security vulnerabilities, managing security releases across four or five active release lines has become difficult to sustain in the current Node.js voluntary work model. By reducing the number of concurrent release lines, the project can focus on better supporting the releases people actually use. | ||
|
|
||
| What's important is what's not changed with the new release schedule: |
There was a problem hiding this comment.
| What's important is what's not changed with the new release schedule: | |
| What's important is what's not changed with the new release schedule: | |
I think we just need to add a new line here for linting/prettier to pass
Description
Validation
Related Issues
Check List
pnpm formatto ensure the code follows the style guide.pnpm testto check if all tests are passing.pnpm buildto check if the website builds without errors.