chore(deps): update dependency cspell to v10.2.1 - #1879
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
❌MegaLinter analysis: Error
Detailed Issues❌ REPOSITORY / betterleaks - 2 errors❌ REPOSITORY / checkov - 1 error❌ REPOSITORY / devskim - 45 errors❌ REPOSITORY / grype - 119 errors❌ REPOSITORY / kingfisher - 1 error❌ SPELL / lychee - 1 error❌ REPOSITORY / osv-scanner - 119 errors❌ REPOSITORY / secretlint - 1 error❌ YAML / yamllint - 8 errors
|
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.

This PR contains the following updates:
10.0.1→10.2.1Release Notes
streetsidesoftware/cspell (cspell)
v10.2.1Compare Source
Fixes
fix: support soft hyphens in the word splitter (#9144)
fix: support soft hyphens in the word splitter (#9144)
This pull request introduces several improvements and fixes to the word segmentation and word splitting logic, especially for Thai language support and symbol handling. The main changes include updating the Thai segmentation to use soft hyphens, enhancing the word splitting logic to handle more cases (including camelCase, symbols, and soft hyphens), and refactoring the code for better modularity and test coverage.
Word segmentation and Thai language improvements:
th-TH) segmentation to use soft hyphens (\u00AD) instead of spaces, improving the accuracy of word breaks and ensuring better compatibility with spell checking and downstream processing. [1] [2] [3]@cspell/dict-th-thpackage to dependencies, enabling Thai dictionary support.Word splitting and symbol handling enhancements:
generateWordBreaksutility that generates all possible word breaks in a string, including camelCase, symbols, numbers, and soft hyphens. Includes comprehensive tests and snapshot coverage for various edge cases. [1] [2] [3] [4]Refactoring and code organization:
wordSplitter/index.jsentry point, improving modularity and future maintainability. [1] [2]split,SplitOptions, andSplitResultinwordSplitter/index.tsto clarify and centralize the public API.Other enhancements:
softHyphenconstant for consistent use throughout the codebase. [1] [2]Dictionary Updates
fix: Workflow Bot -- Update Dictionaries (main) (#9143)
fix: Workflow Bot -- Update Dictionaries (main) (#9143)
v10.2.0Compare Source
Features
feat: Add `--force-check` cli option (#9080)
feat: Add
--force-checkcli option (#9080)This pull request introduces a new
--force-checkoption to the CLI, allowing users to force specific files to be checked even if they would normally be excluded. It also standardizes dependency configuration naming, improves error handling and reporting for the CLI, and updates TypeScript target versions in config files. The most important changes are grouped below.New CLI Feature: Force Check
--force-checkoption to thelintcommand, allowing files specified with--file,--files, or--file-listto be checked even if they would normally be excluded. This includes updates to the CLI interface, validation logic, and documentation/help output. [1] [2] [3] [4] [5]forceCheckflag, ensuring excluded files can be checked when requested, and updated reporting of skipped files. [1] [2] [3] [4] [5] [6]CLI Error Handling and Testing
--force-checkwithout specifying files, or mixing globs and--file), with corresponding error messages and test cases. [1] [2]--force-checkoption, including snapshot updates for help and error outputs. [1] [2] [3] [4] [5] [6] [7]Dependency Configuration Standardization
onlyAllowBundletoonlyBundleacross all relevant config files and documentation for consistency. [1] [2] [3] [4]Other Improvements
Node20toNode22.package.json.Fixes
fix: Updated package.json exports (#8965)
fix: Updated package.json exports (#8965)
This fixes a few package exports that were wrong or inconsistent (e.g.
exports["."]not the same path asmain).The
pnpm testscript was failing locally due to my~/.npmrchavingignore-scripts=true, which prevented thepreinstallscript from running. I updatedtest:prepto call thepreinstallscript, which should be fast if you already haveyarninstalled.Dictionary Updates
fix: Workflow Bot -- Update Dictionaries (main) (#9067)
fix: Workflow Bot -- Update Dictionaries (main) (#9067)
v10.1.1Compare Source
Fixes
fix: Do not load .pnp.js files when untrusted (#9064)
fix: Do not load .pnp.js files when untrusted (#9064)
Dictionary Updates
fix: Workflow Bot -- Update Dictionaries (main) (#9055)
fix: Workflow Bot -- Update Dictionaries (main) (#9055)
v10.1.0Compare Source
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)
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.