From be853ab8f4454de96f10e30198ddeb0613155628 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 9 Sep 2026 15:25:54 +0000 Subject: [PATCH] chore: version packages --- .changeset/patterns-matches-stack.md | 22 ---------------------- CHANGELOG.md | 23 +++++++++++++++++++++++ package.json | 2 +- 3 files changed, 24 insertions(+), 23 deletions(-) delete mode 100644 .changeset/patterns-matches-stack.md diff --git a/.changeset/patterns-matches-stack.md b/.changeset/patterns-matches-stack.md deleted file mode 100644 index 1581a49..0000000 --- a/.changeset/patterns-matches-stack.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -"@codacy/codacy-cloud-cli": minor ---- - -New `-k, --matches-stack [value]` filter on `codacy patterns`, which narrows a tool's code patterns to those that do (or don't) match the repository's detected stack. - -It's a tri-state flag, the same shape as `issues --false-positives`: - -```bash -codacy patterns eslint9 --matches-stack # only patterns matching the repo stack -codacy patterns eslint9 --matches-stack true # same -codacy patterns eslint9 --matches-stack false # only patterns that don't match -codacy patterns eslint9 # unfiltered -``` - -The filter applies in bulk mode too, so `--enable-all` / `--disable-all` can be scoped to the stack: - -```bash -codacy patterns eslint9 --disable-all --matches-stack false -``` - -The summary printed after a bulk update still reports counts for the whole tool, not just the updated subset. diff --git a/CHANGELOG.md b/CHANGELOG.md index 91de2f1..83a7c1e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,28 @@ # @codacy/codacy-cloud-cli +## 1.11.0 + +### Minor Changes + +- [#45](https://github.com/codacy/codacy-cloud-cli/pull/45) [`e21f321`](https://github.com/codacy/codacy-cloud-cli/commit/e21f321c28ef2963a7bd0ee9cfdabb2666d15c46) Thanks [@alerizzo](https://github.com/alerizzo)! - New `-k, --matches-stack [value]` filter on `codacy patterns`, which narrows a tool's code patterns to those that do (or don't) match the repository's detected stack. + + It's a tri-state flag, the same shape as `issues --false-positives`: + + ```bash + codacy patterns eslint9 --matches-stack # only patterns matching the repo stack + codacy patterns eslint9 --matches-stack true # same + codacy patterns eslint9 --matches-stack false # only patterns that don't match + codacy patterns eslint9 # unfiltered + ``` + + The filter applies in bulk mode too, so `--enable-all` / `--disable-all` can be scoped to the stack: + + ```bash + codacy patterns eslint9 --disable-all --matches-stack false + ``` + + The summary printed after a bulk update still reports counts for the whole tool, not just the updated subset. + ## 1.10.0 ### Minor Changes diff --git a/package.json b/package.json index ad02688..848ff84 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@codacy/codacy-cloud-cli", - "version": "1.10.0", + "version": "1.11.0", "description": "A command-line tool to interact with Codacy Cloud from your terminal", "homepage": "https://www.codacy.com", "repository": {