Skip to content

Bump Lizard 1.24.0 - #24

Merged
heliocodacy merged 1 commit into
masterfrom
chore/automated-tool-update
Sep 24, 2026
Merged

heliocodacy merged 1 commit into
masterfrom
chore/automated-tool-update

Conversation

@stefanvacareanu7

Copy link
Copy Markdown
Contributor

Summary

  • Update the documented Lizard version in docs/patterns.json from 1.23.0 to 1.24.0 to match the latest upstream release.
  • The Dockerfile installs lizard unpinned (pip install lizard), so the image already picks up 1.24.0 automatically at build time — confirmed via lizard --version inside the built image.
  • Reviewed the 1.24.0 release notes: new features (Halstead metrics via -Ehalstead, --no-gitignore) are opt-in flags this engine doesn't pass, and the bug fixes are per-language parsing accuracy improvements. Nothing changes the plain-text CLI output format or the nloc/ccn/parameter-count metrics that docs/patterns.json wraps, so no other files needed updating.

Validation

  • npm install && npm run build — pass
  • npm run build:docker — image builds successfully; lizard --version inside the image reports 1.24.0
  • codacy-plugins-test metrics DockerTest — pass
  • codacy-plugins-test multiple DockerTest — pass (3/3 results)
  • npm run lint currently fails on this repo independent of this change (ESLint 10 requires eslint.config.js, but the repo still has .eslintrc.js) — this is a pre-existing config mismatch unrelated to the Lizard bump, and CI (.circleci/config.yml) doesn't run npm run lint, so it isn't a blocker here. Flagging in case a separate ESLint flat-config migration is wanted.

Test plan

  • docs/patterns.json version bumped to 1.24.0
  • Docker image builds and reports Lizard 1.24.0
  • codacy-plugins-test multiple passes
  • codacy-plugins-test metrics passes
  • CI checks green (polling after push)

🤖 Generated with Claude Code

Update the documented lizard tool version from 1.23.0 to 1.24.0 in
docs/patterns.json to match the latest release. The Dockerfile installs
lizard unpinned from PyPI, so the image already picks up 1.24.0; verified
the new release adds no changes to the plain-text output format the
engine parses (new features are opt-in flags we don't use) or to the
nloc/ccn/parameter-count metrics our patterns wrap.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

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

Run reviewer

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

@codacy-production codacy-production Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

No security or major logic issues were identified, and Codacy reports the PR as up to standards. However, the acceptance criteria remain unverified because the required Docker builds and regression tests are not included or evidenced.

About this PR

  • No automated tests or validation evidence were added for the Docker image, metrics behavior, multiple results, or compatibility of nloc/ccn/parameter-count outputs.

Test suggestions

  • Verify docs/patterns.json contains version 1.24.0.
  • Build the Docker image and verify lizard --version reports 1.24.0.
  • Run the metrics DockerTest and verify it passes.
  • Run the multiple DockerTest and verify all three results pass.
  • Verify existing nloc, ccn, and parameter-count output remains unchanged with Lizard 1.24.0.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify docs/patterns.json contains version 1.24.0.
2. Build the Docker image and verify lizard --version reports 1.24.0.
3. Run the metrics DockerTest and verify it passes.
4. Run the multiple DockerTest and verify all three results pass.
5. Verify existing nloc, ccn, and parameter-count output remains unchanged with Lizard 1.24.0.
Low confidence findings
  • CI checks were still pending, and the documented pre-existing lint failure remains unresolved; confirm these do not mask regressions before merging.

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

@heliocodacy
heliocodacy merged commit 892a7a2 into master Sep 24, 2026
4 checks passed
@heliocodacy
heliocodacy deleted the chore/automated-tool-update branch September 24, 2026 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants