Skip to content

[deps]: Update lint tooling - #207

Merged
withinfocus merged 1 commit into
mainfrom
renovate/lint-tooling
Oct 12, 2026
Merged

withinfocus merged 1 commit into
mainfrom
renovate/lint-tooling

Conversation

@renovate

@renovate renovate Bot commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
cspell (source) 10.3.0 → 10.3.6 age confidence
prettier (source) 3.9.6 → 3.9.9 age confidence

Release Notes

streetsidesoftware/cspell (cspell)

v10.3.6

Compare Source

Fixes
fix: Report unknown CSpell directives again (#​9319)
fix: Report unknown CSpell directives again (#​9319)

v10.3.5

Compare Source

Fixes
fix(cspell-lib): `shouldCheckDocument` honors the `forceCheck` option (#​9303)
fix(cspell-lib): shouldCheckDocument honors the forceCheck option (#​9303)

v10.3.4

Compare Source

Fixes
fix: Fix Sponsor cards on npmjs (#​9260)
fix: Fix Sponsor cards on npmjs (#​9260)

v10.3.3

Compare Source

Fixes
fix: Add `--json` option to check text for use with AI (#​9254)
fix: Add --json option to check text for use with AI (#​9254)

This pull request adds support for a --json output mode to the check CLI command, enabling results to be emitted as structured JSON per file. It also introduces comprehensive test coverage for the new JSON output behavior, including error handling and exit code logic.

CLI Enhancements:

  • Added a --json flag to the check command, allowing users to receive results in JSON format. This includes proper handling of multiple files and error cases, such as missing files. [1] [2]
  • Updated the exit code logic to work with both standard and JSON output, respecting the --no-exit-code flag. [1] [2]

Implementation Details:

  • Introduced separate processing functions: processRequestAnsi for standard output and processRequestJSON for JSON output, with the latter aggregating results and errors per file. [1] [2]
  • Added a helper function to detect missing files and report them as JSON errors.

Testing Improvements:

  • Expanded CLI test coverage to include various --json scenarios, such as files with spelling errors, missing files, and the interaction with --no-exit-code. [1] [2]
  • Added utility functions and interfaces in tests to parse and validate the JSON output.

fix: Mark ParsedTags as read only. (#​9253)
fix: Mark ParsedTags as read only. (#​9253)

This pull request makes a small but important change to the ParsedText interface in several files, improving type safety by marking the tags property as a read-only type. This ensures that the tags associated with a parsed text segment cannot be modified after creation.

  • Updated the tags property in the ParsedText interface to use Readonly<ParsedTags> instead of ParsedTags, making the tags immutable in the following files:
    • packages/cspell-types/api/Parser/index.d.mts
    • packages/cspell-types/api/index.d.mts
    • packages/cspell-types/src/Parser/parser.ts

fix: Make sure Parser and DocumentParser can be used together. (#​9252)
fix: Make sure Parser and DocumentParser can be used together. (#​9252)

This pull request enhances the parser interface definitions in the cspell-types package to provide better flexibility and clarity for parser implementations. The main changes introduce optional parseDocument and parse methods to both the Parser and DocumentParser interfaces, across both type declaration and source files.

Parser interface enhancements:

  • Added an optional parseDocument method to the Parser interface, allowing parsers to optionally implement document-based parsing. (packages/cspell-types/api/Parser/index.d.mts [1] packages/cspell-types/api/index.d.mts [2] packages/cspell-types/src/Parser/parser.ts [3]
  • Added an optional parse method to the DocumentParser interface, enabling parsers to optionally implement content-and-filename-based parsing. (packages/cspell-types/api/Parser/index.d.mts [1] packages/cspell-types/api/index.d.mts [2] packages/cspell-types/src/Parser/parser.ts [3]

v10.3.2

Compare Source

Fixes
fix: Add tags to ParsedText (#​9237)
fix: Add tags to ParsedText (#​9237)

This pull request introduces the concept of "tags" for parsed text segments in the CSpell types, allowing each segment of text to be annotated with a set of named tags. These tags can hold boolean, string, or undefined values, supporting richer metadata for parsers and downstream consumers. The changes affect both the TypeScript source and the type definitions.

The most important changes are:

Tagging Support for Parsed Text
  • Added a new optional tags property to the ParsedText interface, allowing each parsed text segment to carry a set of tags as metadata. (ParsedText in parser.ts, index.d.mts, index.d.mts) [1] [2] [3]
  • Introduced the ParsedTag type (boolean | string | undefined) and the ParsedTags interface (a map of tag names to ParsedTag values) to define the structure of tags. (parser.ts, index.d.mts, index.d.mts) [1] [2] [3]
Type Exports and API Surface
  • Updated exports throughout the codebase to include ParsedTag and ParsedTags, making these types available to consumers. (src/Parser/index.ts, src/index.ts, index.d.mts, index.d.mts) [1] [2] [3] [4]
  • Changed the export style in src/Parser/index.mts from export * to export type *, ensuring only types are exported.

These changes lay the groundwork for parsers and other tools to annotate text with structured metadata, improving extensibility and downstream processing.


v10.3.1

Compare Source

Fixes
fix: CSpell-Tools support replacements (#​9205)
fix: CSpell-Tools support replacements (#​9205)

Support replacing word fragments before adding the word to the dictionary.

prettier/prettier (prettier)

v3.9.9

Compare Source

diff

Markdown: Fix text with $ been incorrectly parsed as math syntax (#​20140 by @​fisker)
<!-- Input -->
**Uses $FOO** from `a.sh` and `b.sh`, plus `$BAR` from `c.sh`, before anything else runs here.

<!-- Prettier 3.9.8 -->
**Uses $FOO** from `a.sh` and `b.sh`, plus `$BAR`from`c.sh`, before anything else runs here.

<!-- Prettier 3.9.9 -->
**Uses $FOO** from `a.sh` and `b.sh`, plus `$BAR` from `c.sh`, before anything else runs here.

v3.9.8

Compare Source

diff

Markdown: Don't let Liquid objects interrupt paragraphs (#​20087 by @​seiyab)
<!-- Input -->
If `module` is not a [`WebAssembly.Module`](/en-US/docs/WebAssembly/Reference/JavaScript_interface/Module) object instance, a
{{jsxref("TypeError")}} is thrown.

<!-- Prettier 3.9.7 -->
If `module` is not a [`WebAssembly.Module`](/en-US/docs/WebAssembly/Reference/JavaScript_interface/Module) object instance, a

{{jsxref("TypeError")}} is thrown.

<!-- Prettier 3.9.8 -->
If `module` is not a [`WebAssembly.Module`](/en-US/docs/WebAssembly/Reference/JavaScript_interface/Module) object instance, a
{{jsxref("TypeError")}} is thrown.

v3.9.7

Compare Source

diff

Markdown: Prevent indentation drift in list-item code blocks (#​19647, #​19990 by @​Austin1serb, @​giaBaoJS)
<!-- Input -->
- [x] short first line.

      second paragraph at six spaces that wraps
      onto another line here.

<!-- Prettier 3.9.6 -->
- [x] short first line.

      second paragraph at six spaces that wraps
          onto another line here.

<!-- Prettier 3.9.7 -->
- [x] short first line.

      second paragraph at six spaces that wraps
      onto another line here.
JavaScript: Fix embedded template literal idempotency (#​19725 by @​fisker)
// Input
const foo = html`
            <div>${getText({
            value,
            })}</div>
`;

// Prettier 3.9.6 (first format)
const foo = html`
  <div>
    ${getText({
              value,
            })}
  </div>
`;

// Prettier 3.9.6 (second format)
const foo = html`
  <div>
    ${getText({
      value,
    })}
  </div>
`;

// Prettier 3.9.7
const foo = html`
  <div>
    ${getText({
      value,
    })}
  </div>
`;
Markdown: Preserve Liquid blocks after Markdown tables (#​19730 by @​wanxiankai, @​seiyab)
<!-- Input -->
| Argument | Type |
| -------- | ---- |
{% set default_params = {
    "model": ["str"],
} %}

<!-- Prettier 3.9.6 -->
| Argument                  | Type |
| ------------------------- | ---- |
| {% set default_params = { |

    "model": ["str"],

} %}

<!-- Prettier 3.9.7 -->
| Argument | Type |
| -------- | ---- |
{% set default_params = {
    "model": ["str"],
} %}
Markdown: Preserve single tildes in Markdown (#​19739 by @​lazerg)

Since 3.9.0, single-tilde spans like H~2~O were rewritten to double tildes, turning subscript syntax into strike-through. Only double tildes are treated that way now, matching GitHub.

<!-- Input -->
H~2~O

<!-- Prettier 3.9.6 -->
H~~2~~O

<!-- Prettier 3.9.7 -->
H~2~O
Markdown: Fix Markdown blockquote containing > characters (#​19802 by @​seiyab)
<!-- Input -->
> **test**\>

<!-- Prettier 3.9.6 -->
> **test**>\>

<!-- Prettier 3.9.7 -->
> **test**\>
Markdown: Strip blockquote markers from a setext heading's continuation lines (#​19878 by @​Kjubikstronk)

A setext heading spanning multiple lines inside a blockquote kept the > marker of its continuation lines as literal text.

<!-- Input -->
> Multi
> Line
> ===

<!-- Prettier 3.9.6 -->
> Multi > Line
> ===

<!-- Prettier 3.9.7 -->
> Multi
> Line
> ===
Markdown: Fix HTML block indentation drift in markdown list items (#​19987 by @​lazerg)
<!-- Input -->
1. Enable images:

    <p align="center">
      <img alt="example">
    </p>

<!-- Prettier 3.9.6 (--tab-width=4) -->
1. Enable images:

     <p align="center">
       <img alt="example">
     </p>

<!-- Prettier 3.9.7 (--tab-width=4) -->
1. Enable images:

    <p align="center">
      <img alt="example">
    </p>
Angular: Support @boundary error boundaries (#​20014 by @​Yahiro025)
<!-- Input -->
@boundary {
<complex-chart [data]="data"/>
}
@error (let err) {
<p>{{err.message}}</p>
}

<!-- Prettier 3.9.6 -->
SyntaxError: Unexpected character "EOF" (Do you have an unescaped "{" in your template? Use "{{ '{' }}") to escape it.) (6:1)

<!-- Prettier 3.9.7 -->
@boundary {
  <complex-chart [data]="data" />
} @error (let err) {
  <p>{{ err.message }}</p>
}

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every 2nd week starting on the 2 week of the year before 4am on Monday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner October 12, 2026 02:49
@withinfocus
withinfocus merged commit f856e4f into main Oct 12, 2026
12 checks passed
@withinfocus
withinfocus deleted the renovate/lint-tooling branch October 12, 2026 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant