docs: publish v10.2.0 release highlights (#991)

Author: fasttime

src/_data/blog-dates.json

@@ -463,5 +463,6 @@
     "2026-02-23-eslint-v10.0.2-released.md": "2026-02-23T21:53:46.737Z",
     "2026-03-06-eslint-v9.39.4-released.md": "2026-03-06T22:03:37.518Z",
     "2026-03-06-eslint-v10.0.3-released.md": "2026-03-06T23:17:34.479Z",
-    "2026-03-20-eslint-v10.1.0-released.md": "2026-03-20T15:53:41.636Z"
+    "2026-03-20-eslint-v10.1.0-released.md": "2026-03-20T15:53:41.636Z",
+    "2026-04-03-eslint-v10.2.0-released.md": "2026-04-03T20:51:36.047Z"
 }

src/content/blog/2026-04-03-eslint-v10.2.0-released.md

@@ -3,20 +3,60 @@ layout: post
 title: ESLint v10.2.0 released
 teaser: "We just pushed ESLint v10.2.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release."
 image: release-notes-minor.png
-draft: true
 authors:
-  - eslintbot
+  - fasttime
 categories:
   - Release Notes
 tags:
   - Release
 ---
 
 
+## Highlights
 
 
+### Language-aware rules
 
+ESLint v10.2.0 adds support for language-aware rules through the new `meta.languages` property. Rule authors can now explicitly declare which languages a rule supports, and ESLint will throw a runtime error if that rule is enabled for an unsupported language, as specified by the `language` configuration option.
 
+Here is an example of a rule that only supports the JavaScript language:
+
+```js
+const rule = {
+    meta: {
+        type: "problem",
+        docs: {
+            description: "Example JavaScript rule",
+        },
+        languages: ["js/js"],
+    },
+    create(context) {
+        return {};
+    },
+};
+```
+
+Currently, none of the ESLint built-in rules restrict the languages they are designed to work with, but this may change in the future.
+
+More information about the `meta.languages` property can be found in the [custom rules documentation](https://eslint.org/docs/latest/extend/custom-rules#rule-structure).
+
+### `Temporal` support
+
+With the [Temporal proposal](https://tc39.es/proposal-temporal/) now at TC39 stage 4, ESLint v10.2.0 recognizes `Temporal` as a built-in global. As a result, the `no-undef` rule no longer flags `Temporal` under the default configuration:
+
+```js
+/* eslint no-undef: "error" */
+
+const now = Temporal.Now.instant(); // OK
+```
+
+In addition, the `no-obj-calls` rule now reports direct calls to the global `Temporal` object:
+
+```js
+/* eslint no-obj-calls: "error" */
+
+Temporal(); // Error: 'Temporal' is not a function.
+```
 
 
 ## Features