Skip to content

release: v1.3.10 - give fallback-path tests a workspace with no project… - #30

Merged
Shinrai merged 7 commits into
masterfrom
next
Aug 18, 2026
Merged

release: v1.3.10 - give fallback-path tests a workspace with no project…#30
Shinrai merged 7 commits into
masterfrom
next

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

📦 Dependencies

🔧 Other Changes

👥 Contributors

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · 68cd63e · Node lts/*

Shinrai and others added 4 commits August 11, 2026 06:31
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 />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@types/node&package-manager=npm_and_yarn&previous-version=26.1.2&new-version=26.2.0)](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>
@cldmv-bot cldmv-bot Bot added ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes labels Aug 12, 2026
@cldmv-bot

cldmv-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

🔒 Dependency Review

  • 0 vulnerable package(s)
  • 0 package(s) with incompatible licenses
  • 0 package(s) with invalid SPDX license definitions
  • 0 package(s) with unknown licenses
  • 0 denied package(s)
  • 0 package(s) with OpenSSF Scorecard score < 3

Full job summary

@cldmv-bot cldmv-bot Bot added the type: dependencies Relates to dependency updates, version bumps, or package management label Aug 12, 2026
Shinrai and others added 3 commits August 18, 2026 14:34
…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.
@cldmv-bot cldmv-bot Bot added the area: tests Touches test files, fixtures, or test infrastructure label Aug 18, 2026
@cldmv-bot cldmv-bot Bot changed the title release: v1.3.10 - bump @types/node from 26.1.2 to 26.2.0 in the minor… release: v1.3.10 - give fallback-path tests a workspace with no project… Aug 18, 2026
@cldmv-bot cldmv-bot Bot added the type: bug Something is broken or not behaving as expected label Aug 18, 2026
@Shinrai
Shinrai merged commit 0c602e0 into master Aug 18, 2026
37 checks passed
@cldmv-bot
cldmv-bot Bot deleted the next branch August 18, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: tests Touches test files, fixtures, or test infrastructure ! release → master v4 flow: persistent next → master release PR (carries the next feature release) release Marks a pull request as a pending release — merge to publish a new version semver: patch This release contains only backwards-compatible bug fixes type: bug Something is broken or not behaving as expected type: dependencies Relates to dependency updates, version bumps, or package management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant