chore: Prepare Release v10.1.0 (auto-deploy) - #8883
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-draft
branch
11 times, most recently
from
June 8, 2026 19:50
e2365b7 to
f088fac
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
14 times, most recently
from
June 16, 2026 05:47
4efce74 to
1818d04
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
5 times, most recently
from
July 5, 2026 15:00
3fa25b6 to
b4f5199
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
3 times, most recently
from
July 30, 2026 05:15
f363d7e to
c826928
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
26 times, most recently
from
August 9, 2026 20:44
f37f755 to
54c1698
Compare
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
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.
Release v10.1.0
Release Notes
Details
Features
feat(cspell-junit-reporter): add JUnit XML reporter package (#8945)
feat(cspell-junit-reporter): add JUnit XML reporter package (#8945)
Closes #4570.
Adds
@cspell/cspell-junit-reporter, a new workspace package modeled onpackages/cspell-json-reporter, that emits a JUnit-compatible XML report of a cspell run.The issue asked for a minimal mapping along the lines of:
This PR follows that shape but wraps it in a
<testsuites>root and groups by file (one<testsuite>per file, suite name = file path), since that is the convention used by other widely-consumed JUnit reporters (for example ESLint's JUnit formatter) and is what most CI JUnit parsers expect. The package README documents the full mapping.package.json,tsconfig.json, test framework, andfiles/exports/publishConfigshape are copied fromcspell-json-reporter. Version pinned to 10.0.1 to match the monorepo's locked versioning.src/utils/escapeXml.ts) and a pure XML-string builder (src/utils/buildJUnitXml.ts) were written in-repo, consistent with the monorepo's small-utility-file convention.erroremitter routed to a dedicatedcspell-errorstestsuite using<error>).Assumptions the issue thread left ambiguous, called out for review:
<testsuite>per file rather than one flat suite for the whole run. Matches common JUnit reporter convention and keeps per-file counts meaningful in CI UIs.<testcase name="no issues found">so a suite is never reported withtests="0", which some JUnit consumers treat as suspicious.cspell-json-reporter's (outFile,suiteNameonly). JUnit XML has no natural place for arbitrary debug/progress log dumps.<error>elements, distinct from spelling<failure>elements, per the JUnit failure-vs-error distinction.Verified locally:
tsc -bclean, vitest 32/32, eslint and prettier clean, and the full monorepobuild:prodsucceeds with the package in the workspace. One environment note: the package's CLI smoke-test script wasn't runnable locally (repo requires Node >=22.18.0, local was 22.17.0 — the sibling json-reporter fails identically there), so CI is the first place it will run.Fixes
fix: allow substitutions across ignored ranges (#9017)
fix: allow substitutions across ignored ranges (#9017)
Summary
Testing
pnpm --filter cspell-lib test -- src/lib/textValidation/docValidator.test.ts src/lib/textValidation/textValidator.test.ts -t substitutionspnpm --filter cspell-lib test -- src/lib/textValidation/textValidator.test.tspnpm --filter cspell-lib buildpnpm --filter cspell-lib test(1571 passed; 16 local environment-dependent tests failed because Yarn PnP/symlink fixtures were unavailable in this Windows clone or network requests timed out)Closes #8962.
AI assistance: OpenAI Codex was used to investigate, implement, and test this change. I reviewed the diff and test results before submission.
fix: Find the nearest `.git` when a worktree is inside a clone (#8976)
fix: Find the nearest
.gitwhen a worktree is inside a clone (#8976)Fixes #8975.
findRepoRootruns two independentfindUpsearches and prefers the directory result, so a clone further up wins over a worktree's own.gitfile:With
useGitignore: truethe clone's.gitignoreis then applied to the worktree's files, so a worktree kept in a gitignored folder inside its own clone — the.worktreeslayout this repository uses itself — has every file treated as ignored andcspellreportsFiles checked: 0.This searches once for a
.gitof either kind, via a predicate, so the nearest one marks the root. That also drops one full walk up the tree.Note that omitting
typeis not an alternative:findUpFromUrldefaults it to'file', so a plainfindUp('.git', directory)stops finding normal clones.The new test builds a clone with a worktree nested inside it under
temp/and checks both roots resolve to themselves. It fails onmainwith the worktree resolving to the clone.Verified with the built CLI on a scratch repository, run from a subdirectory of the worktree so that the
findRepoRoot(cwd) || cwdfallback ingenerateGitIgnorecannot mask the result: before,Files checked: 0; after, the misspellings are reported.fix: Add .typ extension for Typst (#8961)
fix: Add .typ extension for Typst (#8961)
Typst files typically have the
.typextension, not.typst. This PR adds.typas an alternative filetype extension so that cspell can recognize those files automatically.fix: Handle Windows UNC Long Path Names (#8914)
fix: Handle Windows UNC Long Path Names (#8914)
Pull request overview
This PR improves
cspell-url’s handling of Windows long/UNC path formats by adding long-path prefix utilities and ensuringFileUrlBuildercan generate correctfile:URLs for UNC/extended-length paths. It also adds fixtures and tests to exercise long-path behavior.Changes:
\\?\,\\?\UNC\,\\.\) and normalization (fixLongPathPrefix) infileUrl.mts.FileUrlBuilderto special-case UNC/extended-length paths when converting tofile:URLs.Related to:
Dictionary Updates
fix: Workflow Bot -- Update Dictionaries (main) (#9024)
fix: Workflow Bot -- Update Dictionaries (main) (#9024)
Update Dictionaries (main)
Summary
fix: Workflow Bot -- Update Dictionaries (main) (#8995)
fix: Workflow Bot -- Update Dictionaries (main) (#8995)
Update Dictionaries (main)
Summary
fix: Workflow Bot -- Update Dictionaries (main) (#8990)
fix: Workflow Bot -- Update Dictionaries (main) (#8990)
Update Dictionaries (main)
Summary
fix: Workflow Bot -- Update Dictionaries (main) (#8956)
fix: Workflow Bot -- Update Dictionaries (main) (#8956)
Update Dictionaries (main)
Summary
fix: Workflow Bot -- Update Dictionaries (main) (#8881)
fix: Workflow Bot -- Update Dictionaries (main) (#8881)
Update Dictionaries (main)
Summary
Version Information
v10.1.010.1.0Summary