chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@codacy/codacy-cloud-cli@1.11.0

Minor Changes

• #48 e58f17a Thanks @alerizzo! - Show the repository's coverage status, not just its percentage.

  Codacy now reports whether a repository's coverage is up to date, still waiting
  on a report, has stopped receiving them, or was never set up — and the CLI can
  tell those apart:

  • codacy repos marks a repository whose latest commit has no report yet with a
    dim ⋯ after its last known value, and shows a dim ⊘ instead of a number
    for one that has stopped receiving reports. A legend under the table explains
    only the states actually present in the listing.
  • codacy repo's Metrics section spells the same states out, with the date and
    commit of the last report, and notes when a stopped repository's coverage gate
    is no longer being enforced. A repository that never had coverage now reads
    Not set up rather than a bare N/A.
  • codacy repo's Analysis row reads coverage state from the API's own status
    field instead of inferring it from a separate request. This fixes repositories
    that were reported as healthy while showing a stale percentage, drops one
    request per run, and makes the coverage state available under a repository
    token for the first time.

  --output json gains coverage.status, coverage.lastCommitWithCoverage,
  coverage.statusUpdatedAt and coverage.valueUpdatedAt on both commands. Under
  a repository token, codacy repo's unavailable array is now ["pullRequests"]
  only.

• #45 e21f321 Thanks @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:

  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:

  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.

  Only true and false are accepted as values. Because Commander's optional-value syntax consumes the next token, a lax parser would let codacy patterns gh org repo --matches-stack eslint silently swallow the tool name and then fail with a confusing positional-count error; the flag now rejects non-boolean values with a message that says what to do instead.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

The changelog documents matches-stack behavior, but this PR contains no implementation changes for that feature. Verify the implementation is already present in the target branch before merging; otherwise, publishing 1.11.0 would advertise unsupported functionality.

All acceptance criteria related to filtering, bulk operations, and summaries lack implementation or test evidence in this PR. Codacy reports the changes as up to standards, with no new issues or complexity findings.

About this PR

• No tests or coverage evidence are included for the documented matches-stack filter, bulk operations, or summary behavior.

Test suggestions

• Verify codacy patterns filters patterns matching the repository stack when --matches-stack or --matches-stack true is used.
• Verify codacy patterns filters patterns not matching the repository stack when --matches-stack false is used.
• Verify omitting --matches-stack leaves patterns unfiltered.
• Verify --enable-all and --disable-all apply only to the selected stack subset.
• Verify bulk-update summaries report counts for the whole tool rather than only the filtered subset.
• Verify package metadata is versioned as 1.11.0 and the corresponding changelog entry is present.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify codacy patterns filters patterns matching the repository stack when --matches-stack or --matches-stack true is used.
2. Verify codacy patterns filters patterns not matching the repository stack when --matches-stack false is used.
3. Verify omitting --matches-stack leaves patterns unfiltered.
4. Verify --enable-all and --disable-all apply only to the selected stack subset.
5. Verify bulk-update summaries report counts for the whole tool rather than only the filtered subset.
6. Verify package metadata is versioned as 1.11.0 and the corresponding changelog entry is present.

_{TIP How was this review? Give us feedback}

[codacy-production]

_{🔴 HIGH RISK}

Please verify that the referenced matches-stack implementation is already part of the target branch before releasing 1.11.0; this PR adds only the changelog and package version, not the documented feature.