Repository navigation
chore: Prepare Release v10.5.1 (auto-deploy) - #9616
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-draft
branch
15 times, most recently
from
November 14, 2026 20:06
ea8feaf to
78dbebb
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
from
November 14, 2026 20:07
78dbebb to
6424ee2
Compare
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
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.
Release v10.5.1
Release Notes
Details
Fixes
fix: Let `--force-check` check files skipped by `ignorePathPresets` (#9634)
fix: Let
--force-checkcheck files skipped byignorePathPresets(#9634)With
--force-check,cspell lintnow checks git's own files when they are named on the command line. Before, they were still skipped by thegitpreset ofignorePathPresets, even though--force-checkalready overridesignorePathsand--exclude.Before:
After:
This also covers the
.gitfile that git puts in a worktree or a submodule.fix: Spell check .env files like .env.\* files (#9624)
fix: Spell check .env files like .env.* files (#9624)
Summary
.envand.env.*files, such as.env.local, are now spell checked the same way. Before,.envwas treated as a properties file, while.env.*files were treated as shell scripts. A word could pass in.env.localand be flagged in.env.Both now have both file types,
propertiesandshellscript. So.envfiles now also use the shell, Bash, and Git dictionaries, and anylanguageSettingsfor either file type apply to both..envrcis still a shell script only.fix: Keep every locale in a locale directive followed by punctuation (#9629)
fix: Keep every locale in a locale directive followed by punctuation (#9629)
Summary
A
localedirective with punctuation right after a locale lost that locale and every locale after it. This was a regression in 10.4.1.For example, a Markdown guide that shows the directive in backticks:
fr,en.fronly. English words in the file are reported as unknown.fr,enagain.The fix for comment closers (#9496) and the fix for locales that aren't valid (#9501) still hold. Each of these gives
en, orfr,enfor the last one, because text after the locales that isn't a locale doesn't become one:Technical Details
A directive's text runs to the end of the line. Before, the locale list was split only on spaces and commas, and the list was cut at the first piece that didn't look like a locale. A piece like
en`failed that check, so the list stopped atfr.Now the list ends at the first character that can't be part of a locale or a separator, such as a backtick or
*/, or at--, as in-->. The rest is then split into pieces, and the list still ends at the first piece that isn't a locale.fix: Make `[!…]` in globs match characters that are not listed (#9622)
fix: Make
[!…]in globs match characters that are not listed (#9622)Summary
A
[!…]bracket in a glob now matches any character that is not listed, as it does in git and shell globs. Before,e[!a].txtin.gitignore(withuseGitignore) orignorePathsmatchedea.txtande!.txtand skippedeb.txt, so cspell checked the files you meant to ignore and ignored the files you meant to check.ignorePaths,.gitignorefiles read withuseGitignore,files, and thefilenameglobs inoverrides.[^…]already worked and is unchanged.Fixes #9621
Technical Details
cspell-globnow asks picomatch to read globs in POSIX mode. The only change this makes is that[!starts a negated bracket, like[^.[!a]means the same thing infilesand inignorePaths.fix: Skip more lock files, including pnpm-lock.yaml (#9619)
fix: Skip more lock files, including pnpm-lock.yaml (#9619)
Summary
cspell now recognizes more lock files. Lock files are generated, so cspell skips them when checking files, as it already does for
package-lock.json,yarn.lock, and other files ending in.lock.Newly skipped:
pnpm-lock.yaml(pnpm)npm-shrinkwrap.json(npm)bun.lockb(Bun, before 1.2)packages.lock.json(NuGet)Package.resolved(Swift Package Manager)gradle.lockfile(Gradle).terraform.lock.hcl(Terraform)go.sumandgo.work.sum(Go)Version Information
v10.5.110.5.1Summary