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.4.0

Minor Changes

• #20 cbf62d5 Thanks @alerizzo! - codacy findings and codacy finding now show the vulnerable dependency's import chain for SCA findings that carry the new dependencyChains field. Each finding is labelled Direct (Update <pkg> to <fixedVersion>) or Transitive (<pkg> → … → <pkg> (Fixed in <fixedVersion>)), and chains with 4+ packages collapse their middle to <first> → ... N more ... → <last>. The list shows the first chain plus ... and X more; the detail lists every chain aligned under a single label. dependencyChains is also included in --output json.

[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

This automated release PR updates @codacy/codacy-cloud-cli to version 1.4.0. The changes include the version bump in package.json and corresponding release notes in CHANGELOG.md detailing new SCA dependency chain features. Codacy analysis indicates the PR is up to standards.

While the versioning and changelog are addressed, the removal of the consumed changeset files (.changeset/bold-views-kiss.md and .changeset/findings-dependency-chains.md) specified in the acceptance criteria is not visible in the provided file list. Additionally, there are no automated tests included in this PR for the newly released features; verification is assumed to have occurred in the original feature PR (#20).

Test suggestions

• Verify that 'codacy findings' and 'codacy finding' display labels for Direct and Transitive SCA dependencies
• Verify that dependency chains with 4 or more packages are collapsed using the '... N more ...' format
• Verify that the 'dependencyChains' field is included in the JSON output when using --output json

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that 'codacy findings' and 'codacy finding' display labels for Direct and Transitive SCA dependencies
2. Verify that dependency chains with 4 or more packages are collapsed using the '... N more ...' format
3. Verify that the 'dependencyChains' field is included in the JSON output when using --output json

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}