v3.14.0

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)

v3.13.1

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)

v3.13.0

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

v3.12.0

🚀 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)

v3.11.2

Changelog

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

v3.11.1

Changelog

• 6aa8bb9 fix: don't error on duplicate fields

v3.11.0

This release adds support for linting front matter fields in Markdown, AsciiDoc, reStructuredText, MDX, and Org files.

There are 3 supported front matter types -- YAML, TOML, and JSON:

Each field is dynamically assigned its own scope, allowing you to write rules that target specific ones:

---
title: "My document"
description: "A short summary of the document's purpose."
author: "John Doe"
---

Using the example above, the generated scopes would be text.frontmatter.title, text.frontmatter.description, and text.frontmatter.author.

A rule can then use these in its scope: field:

extends: capitalization
message: "'%s' should be in title case"
level: warning
scope: text.frontmatter.title

Changelog

• 94247d4 chore: add mdx2vast to Docker
• ecbcb3b feat: support for front matter

v3.10.0

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

v3.9.6

Changelog

• c336149 fix: support filters through strings or files (#967)

v3.9.5

Changelog

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