docs: blog post for v7

[bradzacher]

PR Checklist

• Addresses an existing open issue: fixes 📣 Upcoming v7 Major Release #8346
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Adds a blog post for the v7 release to summarise the changes and announce our new package.

[typescript-eslint]

Thanks for the PR, @bradzacher!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	064a142
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65c694f98214470008621253
😎 Deploy Preview	https://deploy-preview-8400--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (🟢 up 11 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 064a142. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 33 targets

• nx test utils
• nx test scope-manager
• nx test parser
• nx run types:build
• nx test typescript-eslint
• nx test visitor-keys
• nx run repo-tools:postinstall-script
• nx test type-utils
• nx run-many --target=lint --parallel
• nx test rule-schema-to-typescript-types
• nx test typescript-estree
• nx test eslint-plugin
• nx test repo-tools
• nx test eslint-plugin-tslint
• nx test eslint-plugin-internal
• nx test ast-spec
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint
• nx test utils --coverage=false
• nx test visitor-keys --coverage=false
• nx run-many --target=typecheck --parallel
• nx test type-utils --coverage=false
• nx test typescript-estree --coverage=false
• nx test typescript-eslint --coverage=false
• nx test scope-manager --coverage=false
• nx test repo-tools --coverage=false
• nx test eslint-plugin --coverage=false
• nx test eslint-plugin-internal --coverage=false
• nx test rule-schema-to-typescript-types --coverage=false
• nx run repo-tools:generate-configs
• nx test parser --coverage=false
• nx test ast-spec --coverage=false
• nx test eslint-plugin-tslint --coverage=false
• nx run integration-tests:test

---

Sent with 💌 from NxCloud.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (8ef5f4b) 87.78% compared to head (064a142) 86.94%.
Report is 11 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8400      +/-   ##
==========================================
- Coverage   87.78%   86.94%   -0.84%     
==========================================
  Files         397      252     -145     
  Lines       13821    12251    -1570     
  Branches     4067     3861     -206     
==========================================
- Hits        12133    10652    -1481     
+ Misses       1391     1332      -59     
+ Partials      297      267      -30     

Flag	Coverage Δ
unittest	86.94% <ø> (-0.84%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 147 files with indirect coverage changes

[rubiesonthesky]

TS eslint is usually used as a dev tool. So would it make sense to instruct to install it with -D?

[JoshuaKGoldberg]

Looks good as a start! 🚀

Requesting changes on a bit more info.

[JoshuaKGoldberg]

🚀 Whoohoo!

This looks great, thanks for all the writing-up. I just left some small things inline - nothing blocking IMO.

[hyunbinseo]

Regarding the Node.js engine requirements:

Update Node.js engine requirement to ^18.18.0 || >=20.0.0.
…
Note that this is the same requirement that ESLint v9 will impose.

typescript-eslint/package.json

Lines 52 to 54 in b27de99

	"engines": {
	"node": "^18.18.0 || >=20.0.0"
	},

the ESLint team decided to use ^18.18.0 || ^20.9.0.

• Change Request: Drop Node v12/v14/v16/v17/v19 support eslint/eslint#17595
• feat!: Require Node.js ^18.18.0 || ^20.9.0 || >=21.1.0 eslint/eslint#17725

This is because v20 LTS started from v20.9.0.

https://nodejs.org/en/blog/release/v20.9.0

Either the blog post or the package.json should be updated?

[bradzacher]

Oh looks like I didn't copy past correctly.
Oh well - it's close enough really. If someone's on v20 it should be close to a no-op for them to upgrade to v20.9

With our next major well bump it properly.

[hyunbinseo]

Thanks for the confirmation.

I understand that it is a breaking change, but enforcing v20 LTS in a minor release seems viable.