Release Notes May 2026#2682
Conversation
Up to standards ✅🟢 Issues
|
|
Overall readability score: 54.23 (🟢 +0.02)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the Codacy Cloud May 2026 release notes, along with updates to the release notes index and mkdocs navigation. The review feedback focuses on minor formatting and branding improvements within the release notes, including the correct capitalization of 'TypeScript' and 'Jira', removing inconsistent spacing in the tool versions list, and adding a missing trailing newline.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| - **ESLint v8 Vue Parsing Fix:** We fixed the parsing issues with `.vue` files in ESLint v8. (TCE-1429) | ||
|
|
||
| - **Lizard Parameter Count Fix:** We found an issue with the count of parameters within a method in Typescript files using Lizard. The latest version fixed that issue, and now it's counting correctly. (TCE-1519) |
There was a problem hiding this comment.
The name of the language should be capitalized as 'TypeScript' instead of 'Typescript' to follow the official branding.
| - **Lizard Parameter Count Fix:** We found an issue with the count of parameters within a method in Typescript files using Lizard. The latest version fixed that issue, and now it's counting correctly. (TCE-1519) | |
| - **Lizard Parameter Count Fix:** We found an issue with the count of parameters within a method in TypeScript files using Lizard. The latest version fixed that issue, and now it's counting correctly. (TCE-1519) |
|
|
||
| - **Improved AI Reviewer Accuracy:** Fixed a bug where the AI reviewer would hallucinate on dependencies or API versions updated in the code, claiming they do not exist. (CF-2448) | ||
|
|
||
| - **Refactored Jira Prompts:** Fixed a bug where the AI reviewer would ask for a JIRA ticket, even though the users were not using JIRA. (CF-2440) |
There was a problem hiding this comment.
Atlassian officially brands the product as 'Jira' (not 'JIRA'). Using 'Jira' also maintains consistency with the heading of this bullet point ('Refactored Jira Prompts').
| - **Refactored Jira Prompts:** Fixed a bug where the AI reviewer would ask for a JIRA ticket, even though the users were not using JIRA. (CF-2440) | |
| - **Refactored Jira Prompts:** Fixed a bug where the AI reviewer would ask for a Jira ticket, even though the users were not using Jira. (CF-2440) |
| - **Eslint v9** has a new version: **9.39.4** ( updated from 9.38.0 ) | ||
| - **Lizard** has a new version: **1.22.2** ( updated from 1.17.31 ) | ||
| - **Opengrep** has a new version: **1.21.0** ( updated from 1.17.0 ) |
There was a problem hiding this comment.
The spacing inside the parentheses ( updated from ... ) is inconsistent with standard typography. Removing the leading and trailing spaces inside the parentheses improves readability.
| - **Eslint v9** has a new version: **9.39.4** ( updated from 9.38.0 ) | |
| - **Lizard** has a new version: **1.22.2** ( updated from 1.17.31 ) | |
| - **Opengrep** has a new version: **1.21.0** ( updated from 1.17.0 ) | |
| - **Eslint v9** has a new version: **9.39.4** (updated from 9.38.0) | |
| - **Lizard** has a new version: **1.22.2** (updated from 1.17.31) | |
| - **Opengrep** has a new version: **1.21.0** (updated from 1.17.0) |
| - **Tailor**: **0.12.0** | ||
| - **Trivy**: **0.70.0** | ||
| - **Tslint**: **6.1.3** | ||
| - **Tsqllint**: **1.16.0** No newline at end of file |
There was a problem hiding this comment.
The file is missing a newline character at the end. Ending files with a newline is a standard POSIX convention that ensures compatibility with various text processing tools and avoids git warnings.
| - **Tsqllint**: **1.16.0** | |
| - **Tsqllint**: **1.16.0** | |
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull Request Overview
Codacy analysis indicates the project is up to standards. The review identifies opportunities to improve the technical accuracy and tone of the release notes, specifically regarding the description of environment file handling. Additionally, the PR lacks a description, which is necessary for providing context and validating the changes.
About this PR
- The PR description is empty. Please provide context regarding the changes and confirm if manual validation of the links and navigation sidebar was performed.
Test suggestions
- Verify that the link added to docs/release-notes/index.md correctly points to the new file path.
- Verify that the navigation entry in mkdocs.yml is correctly formatted and nested under the 2026 heading.
- Verify that all internal links (e.g., roadmap) and RSS feed references in the new markdown file are valid.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify that the link added to docs/release-notes/index.md correctly points to the new file path.
2. Verify that the navigation entry in mkdocs.yml is correctly formatted and nested under the 2026 heading.
3. Verify that all internal links (e.g., roadmap) and RSS feed references in the new markdown file are valid.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
|
|
||
| - **AI Inventory Access Update:** AI Inventory is now only available to Business Tier accounts. (LK-2130) | ||
|
|
||
| - **YAML Support for Environment Files:** Codacy now supports `.env`, `.env.production`, `.env.prod`, and `.env.staging` files for the YAML language. All tools running for YAML will be able to scan these files as well. (TCE-1315) |
There was a problem hiding this comment.
🟡 MEDIUM RISK
.env files are not consistently valid YAML (e.g., they often contain the 'export' keyword). Mapping them to the YAML language may cause tools to report parsing errors. Check if this mapping causes parsing failures in tools like yamllint or spectral when shell-specific syntax is used.
|
|
||
| - **Lizard Parameter Count Fix:** We found an issue with the count of parameters within a method in Typescript files using Lizard. The latest version fixed that issue, and now it's counting correctly. (TCE-1519) | ||
|
|
||
| - **Fix for Empty Commit Detection:** Fixed a bug where the AI reviewer would tell that a commit is empty, or that certain files don't appear to be altered within this commit (e.g. `.txt` files). (CF-2449) |
There was a problem hiding this comment.
⚪ LOW RISK
Suggestion: The phrase 'would tell that' is informal. 'would report that' or 'incorrectly stated that' is more appropriate for technical release notes.
| - **Fix for Empty Commit Detection:** Fixed a bug where the AI reviewer would tell that a commit is empty, or that certain files don't appear to be altered within this commit (e.g. `.txt` files). (CF-2449) | |
| - **Fix for Empty Commit Detection:** Fixed a bug where the AI reviewer would report that a commit is empty or that certain files did not appear to be altered within the commit (e.g., .txt files). |
1 participant
👀 Live preview
🚧 To do