chore: Prepare Release v10.2.0 (auto-deploy) - #9125
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
release-draft
branch
2 times, most recently
from
August 30, 2026 10:35
55fd313 to
3a6649b
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
3 times, most recently
from
August 30, 2026 13:58
2c6a049 to
7a507b7
Compare
github-actions
Bot
force-pushed
the
release-draft
branch
from
August 30, 2026 19:50
7a507b7 to
56dc3b1
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.2.0
Release Notes
Details
Features
feat: Add `--force-check` cli option (#9080)
feat: Add
--force-checkcli option (#9080)This pull request introduces a new
--force-checkoption to the CLI, allowing users to force specific files to be checked even if they would normally be excluded. It also standardizes dependency configuration naming, improves error handling and reporting for the CLI, and updates TypeScript target versions in config files. The most important changes are grouped below.New CLI Feature: Force Check
--force-checkoption to thelintcommand, allowing files specified with--file,--files, or--file-listto be checked even if they would normally be excluded. This includes updates to the CLI interface, validation logic, and documentation/help output. [1] [2] [3] [4] [5]forceCheckflag, ensuring excluded files can be checked when requested, and updated reporting of skipped files. [1] [2] [3] [4] [5] [6]CLI Error Handling and Testing
--force-checkwithout specifying files, or mixing globs and--file), with corresponding error messages and test cases. [1] [2]--force-checkoption, including snapshot updates for help and error outputs. [1] [2] [3] [4] [5] [6] [7]Dependency Configuration Standardization
onlyAllowBundletoonlyBundleacross all relevant config files and documentation for consistency. [1] [2] [3] [4]Other Improvements
Node20toNode22.package.json.Fixes
fix: Reduce the size of cspell types when bundled (#9119)
fix: Reduce the size of cspell types when bundled (#9119)
This pull request introduces a new test package,
test-cspell-types-define-config, designed to verify the size and correct bundling of thedefineConfigfunction from@cspell/cspell-types. It also includes minor internal refactoring in themergeConfiglogic. The main themes are the addition of the test package and improvements to configuration merging.New test package:
test-cspell-types-define-configAdded the
test-cspell-types-define-configpackage with configuration files (package.json,tsconfig.json,tsdown.config.ts) and a basic test harness to ensure thedefineConfigutility is small when bundled and functions as expected. The tests check that the output files remain below specified size thresholds and thatdefineConfigis a function returning the same config object when called twice. [1] [2] [3] [4] [5] [6]Updated
pnpm-lock.yamlto add the new test package to the workspace and ensure it depends on the local@cspell/cspell-typespackage.Internal refactoring
mergeIndividualSettingsFnsarray inside themergeConfigfunction inmerge.tsto avoid unnecessary computation and improve encapsulation.fix(ci): push release tag with GitHub App token so publish.yml triggers (#9097)
fix(ci): push release tag with GitHub App token so publish.yml triggers (#9097)
Summary
publish.yml(the NPM trusted-publishing workflow) is triggered by apush: tags: v*event, among other triggers.build-version-release.ymlcreates that tag viapnpm lerna version, but the tag was never actually triggeringpublish.yml.Root cause:
lerna versionpushes the version commit/tag to theoriginremote, andorigin's credentials were still the defaultGITHUB_TOKENpersisted byactions/checkout(theSetup Gitstep'sgh-tokenremote was unused —lernapushes toorigin, notgh-token— and was seeded before the GitHub App token even existed). GitHub explicitly does not trigger downstream workflow runs for pushes authenticated with the defaultGITHUB_TOKEN, to avoid recursive triggering. So the tag got created, butpublish.ymlnever fired.Changes
actions/checkout: setpersist-credentials: falseso the default token isn't left wired intoorigin.Setup Git: drop the unused/misconfiguredgh-tokenremote (it referenced the default token anyway, and nothing pushed to it).Push Version: before runninglerna version, pointoriginat the already-generated GitHub App installation token (x-access-token:${GITHUB_TOKEN}) so the resulting tag push is authenticated as the GitHub App and correctly triggerspublish.yml'spush: tags: v*trigger.Test plan
python3 -c "import yaml; yaml.safe_load(open(...))"passes).build-version-release.ymlviaworkflow_dispatchwithdry_run: false(or the next real release) and confirmpublish.ymlfires automatically off the resulting tag push, without needing a manualworkflow_dispatch.Generated by Claude Code
fix: Updated package.json exports (#8965)
fix: Updated package.json exports (#8965)
This fixes a few package exports that were wrong or inconsistent (e.g.
exports["."]not the same path asmain).The
pnpm testscript was failing locally due to my~/.npmrchavingignore-scripts=true, which prevented thepreinstallscript from running. I updatedtest:prepto call thepreinstallscript, which should be fast if you already haveyarninstalled.Dictionary Updates
fix: Workflow Bot -- Update Dictionaries (main) (#9102)
fix: Workflow Bot -- Update Dictionaries (main) (#9102)
Update Dictionaries (main)
Summary
fix: Workflow Bot -- Update Dictionaries (main) (#9067)
fix: Workflow Bot -- Update Dictionaries (main) (#9067)
Update Dictionaries (main)
Summary
Version Information
v10.2.010.2.0Summary