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

Minor Changes

• #35 72a4d3b Thanks @pedrobpereira! - New pull-requests (prs) command: lists pull requests for a repository, with the same analysis-gated columns as repository's "Open Pull Requests" table. -q, --search and -B, --base filter by free text (title/author handle) and target branch, mapping to the API's textQuery/targetBranch params; -S, --state filters by open (default) or closed.

Patch Changes

• #35 72a4d3b Thanks @pedrobpereira! - Fix findings's pagination warning silently not firing when the API response omits pagination.total: the guard now also checks for a remaining cursor, so a trailing page of results is no longer hidden from the --limit hint.

• #35 72a4d3b Thanks @pedrobpereira! - formatStandards() (used by repository's Open Pull Requests table, pull-request's Up to Standards row, and pull-requests' ✓ column) now shows a dim ⋯ while a pull request is still being analysed, instead of falling through to a hard ✗ on gate data that isn't final yet.

• #35 72a4d3b Thanks @pedrobpereira! - Fix PR complexity showing as no data, and polish the pull-requests table. Complexity is now read from the API's nested quality object, which is where the pull-request endpoints actually return it — pull-requests, pull-request and repository all previously rendered it as empty. The pull-requests table now leads with the up-to-standards column, orders metrics the same way repositories does (issues, complexity, duplication, coverage), hides the Coverage column when no listed PR has coverage data, shows - instead of N/A for metrics with no value, and no longer signs a zero issue count (0 instead of -0). --output json now includes the quality and coverage resultReasons, so consumers can see which gates passed or failed.

[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 PR performs an automated version bump for @codacy/codacy-cloud-cli from 1.7.0 to 1.8.0. The changes are limited to package.json and CHANGELOG.md, documenting several new features and fixes (such as the pull-requests command and pagination improvements) that were likely merged in previous PRs. Codacy results indicate the PR is up to standards with no new issues or quality regressions.

About this PR

• This is an automated release PR. Note that while the CHANGELOG.md describes significant new features and logic fixes (e.g., the pull-requests command), the current diff only includes versioning and changelog updates. Ensure that the logic changes listed were thoroughly tested in their respective source PRs prior to this release.

Test suggestions

• Verify that the 'pull-requests' command correctly lists PRs and applies filters for search, base branch, and state.
• Verify the pagination warning logic in 'findings' when the API response omits the 'pagination.total' field.
• Verify that 'formatStandards()' displays the '⋯' symbol when a pull request is in an 'analysing' state.
• Verify that the 'pull-requests' table correctly hides the Coverage column when no data is present and leads with the standards column.
• Verify that '--output json' includes the 'resultReasons' for both quality and coverage gates.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the 'pull-requests' command correctly lists PRs and applies filters for search, base branch, and state.
2. Verify the pagination warning logic in 'findings' when the API response omits the 'pagination.total' field.
3. Verify that 'formatStandards()' displays the '⋯' symbol when a pull request is in an 'analysing' state.
4. Verify that the 'pull-requests' table correctly hides the Coverage column when no data is present and leads with the standards column.
5. Verify that '--output json' includes the 'resultReasons' for both quality and coverage gates.

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