Vale: baixar versions anteriors

## Changelog
• d7a379da fix：A percent-encoded link target no longer drops a later alert
• d59ad842 fix：A `.tsx` file is parsed with the TSX grammar
• cafff9f9 fix：A phrase in a rule matches across a line wrap
• f41c1eda fix：Compile the spelling exception pattern once per vocabulary
• 4f013daf feat：Find `vale.ini` in a project's `.config` directory
• 9f822e9d docs：Add FLOSS
• a7817766 fix：A tag inside a link's text no longer crashes `scope: link`
• 8e88d55a test：Guard the casing-and-code scenario on rst2html
• 10744bd6 fix：A wrapped list item or blockquote is placed by runs, not by searching for its text
• b41932c5 fix：A doc-comment mask drops only an alert whose match lies inside it
• 91041463 fix：An alert in a comment is placed by what extraction took off its line
• 1a84507d fix：A `sequence` match holding inline markup is placed through the block's runs
• 3d89b9e4 fix：An `occurrence` message's count fills `%s` as well as `%d`
• a07aa34c fix：`.mjs`, `.cjs`, `.mts`, and `.cts` are JavaScript and TypeScript, and a mapped file's grammar comes from the format it is read as
• 82f20fc2 fix(lint)：take the tree-sitter grammar from a [formats] mapping when the extension has none (#1204)
• 61cb142a fix：AsciiDoc cross-references without text render as empty links
• cfb21a4c fix：MDX elements that span lines no longer lose later alerts, and a list that takes a non-item no longer panics
• a0fc3a96 fix：MDX reads JSX inside expressions, escapes in attributes, and multiline template literals
• b5b8e429 fix：An unreadable document no longer stops the run, and a package's dropped styles are named
• 25270feb fix：`Vocab` works in `[*]`, and `Vocab = NONE` clears inherited vocabularies
• fce33f19 feat：Spelling alerts say when a word is a casing mistake or looks like code
• fb4f161f fix：Vale.Terms finds terms that start or end with punctuation, like `C++` and `.NET`
• 775511b8 feat：YAML vocabularies, and affix flags in vocabularies and rules
• c8fcacf2 feat：The default dictionary knows common technical vocabulary
• 2b345462 docs：remove studio
• c74f4da2 docs：Remove DO

This release adds `vale test`, a test runner for your rules. A rule that matches nothing still loads, runs, and reports success. You only find out it's broken when it misses something. Now each rule can carry its own test cases：a short document, and the alerts linting it should produce.

extends：existence
message："Consider removing '%s'."
tokens:
• perhaps
tests:
• name：flags a hedge
input：Perhaps we should ship.
want：|
1:1:House.Hedging:Consider removing 'Perhaps'.

Running `vale test` lints each case and shows a diff when the output doesn't match. A case can pin the exact output (`want`), check for part of it (`contains`), or check that something is left alone (`absent`). It can run one rule on its own or go through your project's configuration, and it can read its input as another format or through a View. `script` rules are tested the same way. `--coverage` fails any rule that no case makes fire, and the exit codes are built for CI.

See [Testing](https://docs.vale.sh/topics/testing) and the [announcement post](https://vale.sh/blog/testing-rules).

## Changelog
• 2ee78171 fix：A rule whose `tests` don't parse fails `vale test` instead of vanishing
• 77da0b08 refactor：Typed errors, pattern errors at the token, and readable contexts
• 634b321c fix：Errors show the real exit code, honor --no-color, and point at the config
• db39c406 feat：`BasedOnStyles = NONE`, the spelled-out empty value
• bc8b91d8 perf：Don't parse a file no rule can run on
• c283a4dc feat：Conditional sections, `[glob if expr]`
• 08923bdf feat：`vale test`, and install a package's own dependencies for it
• 424f6e62 fix：Keep a fenced block skipped when both `pre` and `code` are in SkippedScopes
• 84deb6c3 fix：Keep non-breaking and narrow spaces beside inline markup
• 8cbda873 feat(code)：parse C# comments with the C# grammar (#1196)
• 24f277bb test：add `vale test` cases

Vale 3.23.0 reads a Sphinx project as Sphinx does, reads the markup inside source-code comments, and reads large files in linear time.

## Sphinx

Docutils knows only its own directives and roles, and dropped the body of every one it did not know, without a word：the prose in every `versionadded`, `seealso`, `tab`, or `grid` was never linted. Vale now decides the rest by a rule that fits nearly every Sphinx construct: the body of a directive Docutils doesn't define is prose, and the text of a role it doesn't define is code. A `:ref:` written with a title is linted as its title, and `:func:`, `:class:`, and `:doc:` are left alone. An extension's additions that don't fit the rule go in one section, which the reStructuredText and MyST readers both honor:

```ini
[sphinx]
CodeDirectives = mermaid, plantuml
ProseRoles = kbd, samp
```

Nothing needs Sphinx installed. reStructuredText also reads and writes UTF-8 whatever the console's code page, and the Docutils pool now works on Windows.

Docs：[Sphinx](https://docs.vale.sh/formats/sphinx)

## The markup inside comments

A tree-sitter View's per-scope `type` is honored, so a Rust `///` comment is read as Markdown, a Python docstring as reStructuredText, and a Javadoc block as HTML, each with its fenced blocks and inline code skipped:

```yaml
engine：tree-sitter
scopes:
• expr：(line_comment)+ @comment
type：md
```

Each language's documentation convention is understood on top of that：the name a Go doc comment opens with and its `[links]`, rustdoc and KDoc links, Javadoc and JSDoc tags and `@example` blocks, and a docstring's `:param:` fields are not prose. A comment addressed to a tool, `//go:build`, `//nolint`, `# noqa`, `eslint-disable`, is not read at all. Kotlin and TOML have grammars.

Docs：[Code Views](https://docs.vale.sh/topics/views#code), [Documentation conventions](https://docs.vale.sh/formats/code#documentation-conventions)

## Comments in data files

A YAML or TOML file's comments are linted beside the fields its View selects, under the scopes a source file's comments carry, and a `#` inside a string is not a comment.

Docs：[Data Views](https://docs.vale.sh/topics/views#data)

## Named scopes and metric variables

A scope can be written once in `config/scopes/` and used by name in any rule, and `doc(...)` accepts Selectors Level 4, relative selectors in `:has()` included:

```yaml
# styles/config/scopes/Methods.yml
scope：'doc(section:has(> h2:contains("Methods")))'
```

A `metric` formula has the readability scores as variables, `quote_words`, `sentence_length_sd`, and `round()`. A `quote` scope reaches the text between quotation marks. A rule can carry its own `tests:`, and `vale test --coverage` lists the rules without any.

Docs：[Named scopes](https://docs.vale.sh/topics/scopes#named-scopes), [Selections](https://docs.vale.sh/topics/scopes#selections), [metric variables](https://docs.vale.sh/checks/metric#variables)

## The package version this Vale supports

`vale sync` installs the release of a package that the running Vale supports, from a `releases` manifest in its `meta.json` or from the package's release feed, so a style that uses a newer key never breaks an older Vale. Built-in rules honor `[param]` settings, and `YES` and `NO` read as booleans.

Docs：[The version Vale supports](https://docs.vale.sh/keys/packages#the-version-vale-supports)

## Formats

• HTML：a page's `<meta name="description">` is prose, `<samp>` is code, and a figure's caption and alt text are no longer skipped with the figure.
• Org：`#+TITLE:` and `#+AUTHOR:` are prose, headline tags are not, and a footnote is reported where it is written.
• QDoc：an `\omit ... \endomit` on one line ends there.
• Plain text：a manuscript's chapters are headings, and metric rules see the file's summary.
• MDX：a code fence after a one-line element stays out of the HTML block.

## Changelog
• 2753160f spelling：Read faster on large files, and read figures and inline QDoc omissions
• 75c04b37 feat：Read a data file's c

## Spelling

• `split：true` checks the parts of an identifier (`getHTTPResponse_v2` → `get`, `Response`) and reports each at its own position.
• The engine now follows Hunspell's case model, compounding, and affix rules, and passes Hunspell's own test suite.
• Suggestions come in Hunspell's order, and words from ignore files and vocabularies are offered ahead of dictionary words.
• A loaded dictionary is shared across spelling rules.

## Vocabularies

• A section can set its own `Vocab`, which adds to the global one and gets `Vale.<Name>.Terms` and `Vale.<Name>.Avoid` rules.
• A period in an entry is text, not a wildcard, and a phrase matches across a line wrap.
• A `Vale.Terms` alert offers the entry's spelling as a fix.

## Configuration

• An empty `BasedOnStyles` clears a section's inherited settings; `UNSET` clears one rule or style.
• A `[formats]` key can be a file name or a glob, not only an extension.
• A scope can negate an inline element (`text.raw`, `paragraph.link`, and so on).
• `TokenIgnores` and `BlockIgnores` apply to HTML and DITA.

## Formats

• MDX：indented blocks are never code, an expression followed by prose keeps the prose, one-line elements are linted, and alerts no longer land inside JSX tags.
• DITA：all files in a run are converted in one toolkit call.
• Jupyter notebooks are a format of their own.
• Front-matter alerts are placed by the field's position.
• URLs in code comments and RST are treated consistently.

## Changelog

• e109c062 fix：keep a URL out of prose in code comments and RST
• 79a48752 feat：let a scope negate an inline element
• cf161663 perf：convert a run's DITA files in one toolkit run
• 68e022b4 feat：apply ignore patterns to DITA
• f41bebb6 fix：cover a promoted RST title with the comment region written above it
• 18dd8632 fix：apply a vale-off region to a footnote written inside it
• 9bcbf9f9 test：pin a vale-off region after front matter and import lines (#1073)
• 344fd9b0 fix：locate a block's later matches in that block, not in a later copy of its text
• ec7e5f01 feat：match a vocabulary phrase across a line wrap, read a period as text, and offer the term as a fix
• 0194fbbd feat：suggest from the project's own words
• 49422de5 fix(mdx)：lint a one-line element's text as prose, and keep alerts out of JSX tags
• 5ab91a5d fix：place front-matter alerts by the field's position, not by searching the file
• dcf7f18c fix(mdx)：end an expression at its brace, keep prose after it, and parse indented blocks
• 8a9fd38e fix：keep the whitespace before an inline comment, so the words around it stay apart
• 7c61ce4f perf：bound the inline-markup lookahead by byte length, not a rune count of the whole context
• 1e730195 fix：read a notebook cell's source with a tagless switch,
• 9e661060 feat：let a section name its own vocabularies
• fc513c5f perf：share a loaded dictionary across spelling rules, and take the regexp2 fold fix
• f2785853 feat：lint a Vale rule by its message and description, not its patterns
• 85992f2a feat：let a spelling rule split identifiers and check their parts
• cb5885f4 feat：suggest in Hunspell's order, and score suggestions against its fixtures
• 52094c78 fix：read affix headers with trailing fields, escaped slashes, any-script digits, and Turkic casing
• 17417ac4 feat：honor `IGNORE`, convert input by the longest `ICONV` rule inside spell, and read ß as SS in all-caps under `CHECKSHARPS`
• a4e2853d fix：read a `COMPOUNDRULE` as flags and operators, quote its words, and match a capitalized word lower-cased
• bfd0b420 perf：resolve affixed words lazily from roots, and read dictionaries as Hunspell does: per SET, byte flags without FLAG, literal hyphens in classes
• 06325d94 feat：adopt Hunspell's case model, and keep ignore-list words case-lenient
• 54520592 feat：pass Hunspell's German compounding fixtures: `CHECKCOMPOUNDREP`, `COMPOUNDWORDMAX`, prefix strips, and circumfix pairing across levels
• a770129c feat：apply `CHECKCOMPOUNDPATTERN`, with replacements, and keep an `ONLYINCOMPOUND` 

See v3.15.0 for full notes.
Changelog
• 8c4ed0d chore：support immutable releases

See v3.15.0 for full notes.
Changelog
• 8c4ed0d chore：support immutable releases

See v3.15.0 for full notes.
Changelog
- 8c4ed0d chore: support immutable releases

Changelog
- 810868b chore: drop yaml v2
- 20fcb4d fix: move to gopkg.in/yaml.v3
- cdf6f9e Bugfix/path expansion (#1096)
- 3b9c8bf chore(deps): upgrade github.com/olekukonko/tablewriter from v0.0.5 to v1.1.4 (#1092)
- e251662 fix: add FLAG num support for agglutinative languages (#1090)
- 831ded9 chore: update clone path
- 806283c chore(deps): bump github.com/tomwright/dasel/v3 from 3.3.1 to 3.3.2 (#1088)

Changelog
- 41f3b22 fix: correctly ignore class values in HTML

This release introduces support for Dasel v3, which is notably capable of performing predicate-based recursive search.
See Vale & The OpenAPI Specification [2026 update] for an example use case.
Changelog
- c7fc3a1 feat: support dasel v3
- 10a8e86 chore: update go to 1.25.7 (#1085)
- f9f5e68 fix(core): use byte offsets for position reporting in raw-scoped script rules (#1081)
- 034c5f1 feat: set path for stdin cli (#1076)
- 6539915 feat(lint): apply defaultIgnoreDirectories to nested directories (#1072)

Changelog
- f544f49 docs: Update DigitalOcean referral information in README
- bbf1933 Fix #1046 - handle xsd as xml (#1067)
- a9ea7b8 Fix handling of xslt path and possible args pollution for xslt calls (#1066)

This release introduces tree-sitter support for Java source code files. See the View docs for more information.
Changelog
- 27161c8 feat: add tree-sitter support for Java
- 25f5a77 fix: don't error on continuation characters

🚀 New Feature: Views – Targeted Linting for Structured (YAML, JSON, TOML) and Source Code Files
We’re introducing Views, a new way to define custom, structured representations of your files—giving you fine-grained control over what gets linted and how.
Views allow you to extract specific content from structured data (like YAML, JSON, or TOML) and source code and apply scoped linting rules to just those sections.
🔍 What’s a View?
A View is a user-defined configuration that transforms a file into a set of named scopes. This enables you to lint only relevant parts of a file—such as metadata descriptions, comments, or docstrings—without affecting the rest.
Here's an example using an OpenAPI file:
openapi: 3.0.0
info:
title: sample API
description: Optional multiline or single-line description in [CommonMark](http://commonmark.org/help/) or HTML.
version: 0.1.9
servers:
- url: http://api.example.com/v1
description: Optional server description, e.g. Main (production) serrver
- url: http://staging-api.example.com
description: |
Optional server description, e.g.
Internal staging serrver for testing
- url: http://api.example.com/v2
description: Optional server description, e.g. Main (production) serrver
And here's a View that extracts title, description, and each server's description:
# config/views/OpenAPI.yml
engine: dasel
scopes:
- name: title
expr: info.title
- expr: info.description
type: md
- expr: servers.all().description
type: md
type: md indicates that the description values are formatted are Markdown. We enable this be using the View key in our .vale.ini:
StylesPath = ../../styles
MinAlertLevel = suggestion
[API.yml]
BasedOnStyles = Vale
View = OpenAPI
See the documentation for more information.
Changelog
- 44c18b3 test: add more cases
- 8ab88af refactor: blueprint -> view
- 3a996da fix: remove erroneous "+1"
- fdaa335 chore(deps): bump golang.org/x/net from 0.36.0 to 0.38.0 (#996)

Changelog
- dc4c479 fix: adjust comment offset (#992)
- a219fa2 refactor: improve front matter error messages
- 3843d07 test: add case for IgnoredScopes

Changelog
- 6aa8bb9 fix: don't error on duplicate fields

This release introduces support for MDX (#841). See the documentation for more information.
Notably, it is no longer necessary to configure CommentDelimiters or use a [formats] association with Markdown.
Changelog
- 74f7480 chore(deps): bump github.com/expr-lang/expr from 1.16.9 to 1.17.0 (#985)
- 1bcb343 test: add MDX case with old configuration
- 4476a1e chore(deps): bump golang.org/x/net from 0.34.0 to 0.36.0 (#982)
- 32e40db refactor: fix golangci-lint
- 04a7039 fix: support non-expressions in {...}
- bc79b15 refactor: clean up cmd execution
- 811d6c4 chore: install mdx2vast in CI
- 61c8d15 feat: add built-in support for MDX

Changelog
- 143f093 chore: upgrade twine (#960)
- ab80200 fix: revert baseStyles merge (#955)

Changelog
- 87c916b4 fix: support overriding MinAlertLevel
- 4eca3a6e fix: improve Vale.Repetition (
- 8765609f fix: check if we need to load a rule before trying

Changelog
- 48a1d9d5 fix: fallback to default config when syncing (#798)
- b1de4bf7 fix: only match case for ignorecase: true (#802)

Changelog
- 7ec81b7e refactor: use pterm.Fuzzy instead of Gray (#796)
- f001170b refactor: clean up sync progress bar
- 02a44307 docs: fix typos (#794)

This release adds support for including the expected form in the message field of capitalization-based rules:

message: "Found: '%s'; expected: '%s'."

As with substitution, the second %s is optional.Changelog
- a9dc9e63 fix: ensure StylesPath is created with sync (
- e688310b feat: support showing expected case in message
- d198f7da chore: update twine to v0.10.1 (

Changelog
- 7d65b44f fix: use utf8.RuneCountInString for offsets (
- b889aade fix: ensure getNativeConfig is consistent (#780)

Script-based actions
This release introduces the ability to write custom, script-based actions, allowing you to create dynamic solutions to your rules using the Tengo scripting language:

text := import("text")

// `match` is provided by Vale and represents the rule's matched text.
made := text.re_replace(`([A-Z]\w+)([A-Z]\w+)`, match, `$1-$2`)

made = text.replace(made, "-", "_", 1)
made = text.to_lower(made)

suggestions := [made]

prefix for capitalization rules
The capitalization extension point now supports a prefix key, allowing you to specify a constant prefix to ignore when checking the case of a scope:

extends: capitalization
message: "'%s' should be sentence-cased"
level: warning
scope: heading
match: $sentence
# sentence-cased, but allows for a common prefix:
#
# E.g.,
#
# a. This is my heading
prefix: '^[a-z]\.\s'

Changelog
- 1bc77814 feat: support script-based actions (#621)
- c9d24152 feat: allow script-based rules to use local files
- e2ac1dc5 feat: support prefix key in capitalization
- 6ef0894f feat: proto support (#777)
- 3a812b37 feat: add --no-global
- 84b539ec refactor: better install details
- 07828da3 refactor: add CLI help text for host commands
- 3ddc54ae fix: remove duplicate $home prefix

Vale now has support for a VALE_STYLES_PATH environment variable to set the default StylesPath. You can also use the new vale ls-vars command to inspect the supported environment variables from the command line.Changelog
- 9c7238db feat: add ls-vars command
- 2139c417 feat: add support for VALE_STYLES_PATH (#755)
- f0041a58 docs: update contributing instructions (#767)

Changelog
- d9d51196 refactor: "Location" -> "Default Location"
- 0f936aa1 chore: pterm requires Go v1.21
- 28132f71 chore: upgrade pterm
- 27fa9a0a fix: handle sync with relative --config

Changelog
- b58b8b8f fix: remove -q from asciidoctor args (#759)
- a45cc80a feat: support fragments in .ps1 and .jl files (#736)

Changelog
- 08b2c421 refactor: don't load Vale if it's not needed
- 5e502a05 fix: ensure applyPatterns respects formats (#754)

Changelog
- 341348c5 fix: better support for phrases in vocabularies (#726)
- 37dcbc5e fix: use file paths when applying ignore patterns (#732)

Changelog
- 3c136890 fix: don't error on missing default files (errata-ai/vale-action#114)