chore(deps): update dependency textlint to v15 #1187
Merged
Conversation
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
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
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:
^14.8.4->^15.0.0Release Notes
textlint/textlint (textlint)
v15.2.3Compare Source
What's Changed
This releases support npm Trusted Publishing.
https://www.npmjs.com/package/textlint
Documentation
Refactoring
CI
Dependency Updates
Other Changes
Full Changelog: textlint/textlint@v15.2.2...v15.2.3
v15.2.2Compare Source
What's Changed
Bug Fixes
Documentation
Maintenance
CI
Dependency Updates
Other Changes
New Contributors
Full Changelog: textlint/textlint@v15.2.1...v15.2.2
v15.2.1Compare Source
What's Changed
Bug Fixes
Documentation
CI
Dependency Updates
Other Changes
Full Changelog: textlint/textlint@v15.2.0...v15.2.1
v15.2.0Compare Source
What's Changed
🎉 MCP (Model Context Protocol) Enhancements
New: CLI Flag Support with --mcp
Starting with v15.2.0, you can now combine the
--mcpflag with other CLI arguments for enhanced flexibility:Supported CLI Flags:
--config <path>: Custom configuration file--ignore-path <path>: Custom .textlintignore file--quiet: Report errors only--rules-base-directory <path>: Custom node_modules directory📖 Documentation: https://textlint.org/docs/mcp
Features
Testing
CI
Dependency Updates
Full Changelog: textlint/textlint@v15.1.1...v15.2.0
v15.1.1Compare 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.0Compare Source
What's Changed
Key Features
This release includes two major improvements to textlint's severity system and configuration handling:
1. New
infoSeverity Level (PR #1610)We've implemented proper support for the
infoseverity level, which provides more flexible linting for informational messages that are less critical than warnings.Background: Previously,
infohad the same value asnone(0), causing confusion. Nowinfohas 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- Disabledwarning: 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
.textlintrcfile.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
infoseverity level by @azu in #1610Bug Fixes
trueconfig by @azu in #1607Documentation
Testing
truecase by @azu in #1609CI
Dependency Updates
Other Changes
New Contributors
Full Changelog: textlint/textlint@v15.0.1...v15.1.0
v15.0.1Compare Source
What's Changed
Bug Fixes
Refactoring
Full Changelog: textlint/textlint@v15.0.0...v15.0.1
v15.0.0Compare 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
textlintAPIs by @azu in #1574Features
Refactoring
Dependency Updates
Other Changes
Full Changelog: textlint/textlint@v14.8.4...v15.0.0
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.
This PR was generated by Mend Renovate. View the repository job log.