docs: Add 2025-06-26 meeting notes (#594)

Author: sam3k

notes/2025/2025-06-26.md

@@ -0,0 +1,57 @@
+# 2025-06-26 ESLint TSC Meeting Notes
+
+## Transcript
+
+[`2025-06-26-transcript.md`](2025-06-26-transcript.md)
+
+## Attending
+
+- Nicholas C. Zakas (@nzakas) - TSC
+- Francesco Trotta (@fasttime) - TSC
+- Milos Djermanovic (@mdjermanovic) - TSC
+
+@nzakas moderated, and @sam3k took notes.
+
+## Topics
+
+### Statuses
+
+* **@nzakas:** spent most of my time on CSS variable tracking, refactoring the core reporting into a new FileReport class, and adding token methods to JSONSourceCode.
+* **@mdjermanovic:** was working on the basePath feature.
+* **@fasttime:** been busy with the multithread linting prototype and different reviews, 50/50.
+
+### RFC Duty update:
+
+* This week - @fasttime 
+* June 30 - @mdjermanovic 
+* July 7 - @nzakas
+
+### Availability Next Two Weeks
+* @nzakas around 2.5-3 hours each weekday except for Friday July 4, which is a holiday in the US.
+* @mdjermanovic expecting to be available 2 hours each day until (including) July 6th. Then I'll be mostly offline July 7-11.
+* @fasttime should be available 7-9 hours per week the next two weeks.
+
+### [feat: Add missing peer dependencies to `@eslint/config-helpers`](https://github.com/eslint/rewrite/pull/231)
+
+**TSC Summary:** The PR requests adding a peer dependency on ESLint to `@eslint/config-helpers`, similar to what was done for `@eslint/compat`. However, `@eslint/config-helpers` is designed to work with both ESLint `v8` and `v9`, which creates type compatibility issues.
+
+**TSC Question:** Should we accept this PR or address the underlying issue by moving types into `@eslint/core`?
+
+**Resolution:** We've agreed to not accept the PR and instead move forward with moving types into `@eslint/core` to solve this problem. @nzakas will prioritize working on this in the next couple of weeks.
+
+### [feat: Support `basePath` property in config objects](https://github.com/eslint/eslint/pull/19879)
+
+**TSC Summary:** The PR implements the basePath feature and includes a question about when to update the feature flag from `unstable_config_lookup_from_file` to `v10_config_lookup_from_file`.
+
+**TSC Question:** Should we update the flag along with this PR or wait for a subsequent release?
+
+**Resolution:** We've decided to update the flag with the PR, changing from `unstable_config_lookup_from_file` to `v10_config_lookup_from_file`. This means we can start discussing `v10` when @mdjermanovic returns from vacation.
+
+### Scheduled release for June 27th, 2025
+
+**Action Items:**
+
+- @fasttime will release:
+  - `eslint`
+  - `@eslint/js`
+- @mdjermanovic will try to update the basePath PR with the flag change in time for inclusion if it gets two approvals.