Conversation
Test fixtures were written to <cwd>/../tmp-fix-headers-tests (the repos root) and only cleaned on the happy path, so failed/interrupted runs leaked git-repo fixtures into the shared repos root — hundreds accumulated. Anchor the fixture root to the repo's own gitignored tmp/ (import.meta.dirname-relative, cwd-independent), and add a vitest globalSetup that reaps only STALE (mtime older than 1h) orphans so a concurrent in-flight run's fresh fixtures are never touched.
Bumps the minor group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 26.1.2 to 26.2.0 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 26.2.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps the minor group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 26.1.2 to 26.2.0 <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details>
Contributor
Author
🔒 Dependency Review
|
…stry Anchoring FIXTURE_ROOT under this repo's own tmp/ (to stop leaked fixtures sprawling into the shared repos root) means every fixture now sits under this repo's own package.json and .git. That breaks the two tests that assert the "nothing detected" fallback path: unknown project language now resolves to "node" (finds this repo's package.json walking up), and unknown git author now resolves to the real local identity (finds this repo's .git config, which GIT_CONFIG_GLOBAL/HOME overrides can't touch since those only affect the global scope, not a discovered local repo). Add createIsolatedWorkspace(), using the OS temp directory instead of FIXTURE_ROOT, for the two tests that need genuinely zero project ancestry. Everything else keeps using createWorkspace() (in-repo tmp/, leak-contained, age-reaped) since it doesn't care about ancestor isolation.
…tale comment reapStaleWorkspaces() requested withFileTypes but never checked isDirectory() before reaping an entry, so any unexpected non-directory file under FIXTURE_ROOT would also get swept up. Filter to directories only. Also correct vitest.config.mjs's globalSetup comment, which said the setup "wipes" the fixture root before/after the run — it only reaps STALE (age- guarded) directories, never a whole-root wipe. Addresses review comments on PR #28.
Shinrai
approved these changes
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 What's Changed
💥 Breaking Changes
No breaking changes
✨ Features
No new features
🐛 Bug Fixes
📦 Dependencies
🔧 Other Changes
👥 Contributors
Avg: 100.0% ·
68cd63e· Node lts/*