Skip to content

chore(deps): update dependency textlint to v15 #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update dependency textlint to v15 #26

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 5, 2025

This PR contains the following updates:

Package Change Age Confidence
textlint ^11.3.1 -> ^15.0.0 age confidence

Release Notes

textlint/textlint (textlint)

v15.1.1

Compare Source

What's Changed

Features
Bug Fixes
Refactoring
CI
Dependency Updates
Other Changes

Full Changelog: textlint/textlint@v15.1.0...v15.1.1

v15.1.0

Compare Source

What's Changed

Key Features

This release includes two major improvements to textlint's severity system and configuration handling:

1. New info Severity Level (PR #​1610)

We've implemented proper support for the info severity level, which provides more flexible linting for informational messages that are less critical than warnings.

Background: Previously, info had the same value as none (0), causing confusion. Now info has its own distinct value (3) and is properly supported across all formatters.

Use Case: This is particularly useful for AI-assisted writing rules, such as those in textlint-ja/textlint-rule-preset-ai-writing, which provides LLM-oriented rules for guidelines. These rules can be somewhat broad and may produce false positives if used as errors, but when reported as info, they provide more flexible feedback for AI agents and human writers.

Severity Levels:

  • none: 0 - Disabled
  • warning: 1 - Warning (yellow)
  • error: 2 - Error (red)
  • info: 3 - Informational (green)

Example Usage:

{
  "rules": {
    "my-rule": {
      "severity": "info"  // Now properly displays as green "info" 
    }
  }
}
2. Fixed Preset Severity Preservation (PR #​1607)

Fixed an issue where preset-defined severity settings were lost when users provided partial rule configuration in their .textlintrc file.

Problem: When using a preset that defined severity levels for rules, those settings were completely lost if users added any custom options for those rules.

Solution: Implemented a clear priority system where user configuration completely overrides preset configuration when provided (no merging), making behavior predictable and consistent.

Related Issues: Fixes #​1608, #​1606

Features
Bug Fixes
Documentation
Testing
CI
Dependency Updates
Other Changes

New Contributors

Full Changelog: textlint/textlint@v15.0.1...v15.1.0

v15.0.1

Compare Source

What's Changed

Bug Fixes
Refactoring

Full Changelog: textlint/textlint@v15.0.0...v15.0.1

v15.0.0

Compare Source

🎉 Release Notes

For detailed information about textlint v15.0.0, including migration guides and new features, see the comprehensive release notes:

What's Changed

Breaking Changes
Features
Refactoring
Dependency Updates
Other Changes

Full Changelog: textlint/textlint@v14.8.4...v15.0.0

v14.8.4

Compare Source

What's Changed

Refactoring
CI
Dependency Updates

Full Changelog: textlint/textlint@v14.8.1...v14.8.4

v14.8.3

Compare Source

fix to release.

v14.8.1

Compare Source

What's Changed

Documentation

This PR resolves the issue where AI Agents misunderstand the MCP fixFile and fixText tools, thinking they directly modify files when they actually only return fixed content.

Tool Renaming
  • fixFile → getLintFixedFileContent
  • fixText → getLintFixedTextContent
Updated Descriptions
  • Changed from "Fix files/text using textlint" to "Get lint-fixed content of files/text using textlint"
  • Emphasizes that these tools return corrected content without modifying original files
  1. Eliminates AI Agent confusion - Clear naming prevents misunderstanding about file modification
  2. Better user experience - AI Agents will be more willing to use these "safe" tools
  3. Maintains backward compatibility - Only affects MCP tool names, not core functionality
  4. Improved documentation - Examples now clearly show content retrieval use cases
Breaking Changes

This is a breaking change for MCP clients that use the old tool names (fixFile, fixText). However, MCP is experimental feature.

Refactoring
CI
Dependency Updates
Other Changes

Full Changelog: textlint/textlint@v14.8.0...v14.8.1

v14.8.0

Compare Source

What's Changed

Features

As an experimental feature, textlint has added a --mcp flag that allows it to be started as an mcp server.

Please see following setup to use textlint --mcp.

Refactoring
CI
Dependency Updates
Other Changes

Full Changelog: textlint/textlint@v14.7.2...v14.8.0

v14.7.2

Compare Source

What's Changed

Refactoring
CI
Dependency Updates
Other Changes

New Contributors

Full Changelog: textlint/textlint@v14.7.1...v14.7.2

v14.7.1

Compare Source

What's Changed

Documentation

Full Changelog: textlint/textlint@v14.7.0...v14.7.1

v14.7.0

Compare Source

What's Changed

Features
Documentation
CI
Dependency Updates
Other Changes

Full Changelog: textlint/textlint@v14.6.0...v14.7.0

v14.6.0

Compare Source

What's Changed

Features
Bug Fixes
Documentation
Dependency Updates
Other Changes

New Contributors

Full Changelog: textlint/textlint@v14.5.0...v14.6.0

v14.5.0

Compare Source

What's Changed

Features

[!NOTE]
if you use LinkReference, ImageReference and Definition node types from an earlier version of textlint, it will be undefined.

Documentation
Dependency Updates

New Contributors

Full Changelog: textlint/textlint@v14.4.2...v14.5.0

v14.4.2

Compare Source

What's Changed

Bug Fixes

This release follow up for v14.4.1:

v14.4.1 updates:

This release will reduce deprecated warning on installing textlint.

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported

Full Changelog: textlint/textlint@v14.4.1...v14.4.2

v14.4.1

Compare Source

What's Changed

This release will reduce deprecated warning on installing textlint.

npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
Dependency Updates

Full Changelog: textlint/textlint@v14.4.0...v14.4.1

v14.4.0

Compare Source

What's Changed

Features
Dependency Updates

Full Changelog: textlint/textlint@v14.3.0...v14.4.0

v14.3.0

Compare Source

What's Changed

Features
Dependency Updates
Other Changes

Full Changelog: textlint/textlint@v14.2.1...v14.3.0

v14.2.1

Compare Source

What's Changed

Documentation
Refactoring
Dependency Updates
Other Changes

New Contributors

Full Changelog: textlint/textlint@v14.2.0...v14.2.1

v14.2.0

Compare Source

What's Changed

Features

This release will reduce audit warning.

Full Changelog: textlint/textlint@v14.1.0...v14.2.0

v14.1.0

Compare Source

What's Changed

Features

Change Details

linter.scanFilePath API Usage

If you want to know the file path is lintable or not, please use scanFilePath API.

import { createLinter, loadTextlintrc } from "textlint";
const textlintrcDescriptor = await loadTextlintrc();
const linter = createLinter({
    descriptor: textlintrcDescriptor
});
const result = await linter.scanFilePath("README.md");
// result.status is "ok" or "ignored" or "error"
if (result.status === "ok") {
    const lintResult = await linter.lintText("README content", "README.md");
    console.log(lintResult);
}

linter.scanFilePath is for combinating with lintText API because lintText API does not ignore any file.

Dependency Updates
Other Changes

New Contributors

Full Changelog: textlint/textlint@v14.0.5...v14.1.0

v14.0.5

Compare Source

What's Changed

Documentation
Refactoring
Dependency Updates
Other Changes

New Contributors

Full Changelog: textlint/textlint@v14.0.4...v14.0.5

v14.0.4

Compare Source

What's Changed

Bug Fixes
Dependency Updates

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants