Skip to content

Release Notes May 2026 #2682

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DMarinhoCodacy wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Release Notes May 2026 #2682

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c6606b3
Release Notes May 2026
DMarinhoCodacy Jun 9, 2026
c8e2690
fix jira release version
DMarinhoCodacy Jun 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
100 changes: 100 additions & 0 deletions docs/release-notes/cloud/cloud-2026-05.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
---
rss_title: Codacy release notes RSS feed
rss_href: /feed_rss_created.xml
description: Release notes for Codacy Cloud May 2026.
included_jira_versions: ['2026.5']
codacy_tools_version_old: https://github.com/codacy/codacy-tools/releases/tag/9.1.78

Check failure on line 6 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Codacy' instead of 'codacy'.

Raw Output:
{"message": "[Vale.Terms] Use 'Codacy' instead of 'codacy'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 6, "column": 46}}}, "severity": "ERROR"}

Check failure on line 6 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'GitHub' instead of 'github'.

Raw Output:
{"message": "[Vale.Terms] Use 'GitHub' instead of 'github'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 6, "column": 35}}}, "severity": "ERROR"}

Check failure on line 6 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Codacy' instead of 'codacy'.

Raw Output:
{"message": "[Vale.Terms] Use 'Codacy' instead of 'codacy'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 6, "column": 1}}}, "severity": "ERROR"}
codacy_tools_version_new: https://github.com/codacy/codacy-tools/releases/tag/9.2.13
---

# Cloud May 2026

These release notes are for the Codacy Cloud updates during May 2026.

📢 [Visit the Codacy roadmap](https://roadmap.codacy.com) and <span class="skip-vale">let us know</span> your feedback on both new and planned product updates!

## Product enhancements

- **Draft PR AI Review Control:** The PR reviewer no longer runs automatically for draft PRs. Please trigger it manually using the button on the summary if you want a review. (CF-2354)

- **Deprecation of AI Suggestions:** Deprecated AI suggestions in GitHub; please use our PR reviewer instead. (CF-2293)

- **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)

@codacy-production codacy-production Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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


- **Improved Opengrep Secrets Detection:** We improved the rule "hardcoded-passwords" in Opengrep to cover better use cases using keywords like `(api|secret|private|access|aws|ssh|auth|session|encryption|decryption|gcp)-key` or `password|motdepasse|heslo|adgangskode|wachtwoord|salasana|passwort|passord|senha|geslo|clave|losenord|parola|secret|pwd`. (TCE-1496)

Check failure on line 26 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Hardcoded' instead of 'hardcoded'.

Raw Output:
{"message": "[Vale.Terms] Use 'Hardcoded' instead of 'hardcoded'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 26, "column": 66}}}, "severity": "ERROR"}

- **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)

@gemini-code-assist gemini-code-assist Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The name of the language should be capitalized as 'TypeScript' instead of 'Typescript' to follow the official branding.

Suggested change
- **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)


- **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)

Check failure on line 32 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Foreign] Use 'for example' instead of 'e.g. '.

Raw Output:
{"message": "[Microsoft.Foreign] Use 'for example' instead of 'e.g. '.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 32, "column": 177}}}, "severity": "ERROR"}

@codacy-production codacy-production Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚪ LOW RISK

Suggestion: The phrase 'would tell that' is informal. 'would report that' or 'incorrectly stated that' is more appropriate for technical release notes.

Suggested change
- **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).


- **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)

Check failure on line 34 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'don't' instead of 'do not'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'don't' instead of 'do not'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 34, "column": 157}}}, "severity": "ERROR"}

- **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)

Check failure on line 36 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Jira' instead of 'JIRA'.

Raw Output:
{"message": "[Vale.Terms] Use 'Jira' instead of 'JIRA'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 36, "column": 132}}}, "severity": "ERROR"}

Check failure on line 36 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'weren't' instead of 'were not'.

Raw Output:
{"message": "[Microsoft.Contractions] Use 'weren't' instead of 'were not'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 36, "column": 117}}}, "severity": "ERROR"}

Check failure on line 36 in docs/release-notes/cloud/cloud-2026-05.md

View workflow job for this annotation

GitHub Actions / vale 

[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'Jira' instead of 'JIRA'.

Raw Output:
{"message": "[Vale.Terms] Use 'Jira' instead of 'JIRA'.", "location": {"path": "docs/release-notes/cloud/cloud-2026-05.md", "range": {"start": {"line": 36, "column": 82}}}, "severity": "ERROR"}

@gemini-code-assist gemini-code-assist Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Atlassian officially brands the product as 'Jira' (not 'JIRA'). Using 'Jira' also maintains consistency with the heading of this bullet point ('Refactored Jira Prompts').

Suggested change
- **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)


## Tool versions

- **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 )
Comment on lines +40 to +42

@gemini-code-assist gemini-code-assist Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The spacing inside the parentheses ( updated from ... ) is inconsistent with standard typography. Removing the leading and trailing spaces inside the parentheses improves readability.

Suggested change
- **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)

- **AgentLinter**: **0.3.3**
- **Aligncheck**: **1.0.0**
- **Ameba**: **1.6.4**
- **Bandit**: **1.8.3**
- **Biomejs**: **2.4.7**
- **Brakeman**: **4.3.1**
- **Bundler-audit**: **0.9.1**
- **Checkov**: **3.2.508**
- **Checkstyle**: **10.26.1**
- **Clang-tidy**: **10.0.1**
- **Codenarc**: **3.6.0**
- **Codesniffer**: **3.10.1**
- **Coffeelint**: **5.2.11**
- **Cppcheck**: **2.18.0**
- **Credo**: **1.7.12**
- **Csslint**: **1.0.5**
- **Dartanalyzer**: **3.9.3**
- **Deadcode**: **1.0.0**
- **Detekt**: **1.23.8**
- **Eslint v8**: **8.57.0**
- **Eslint v7**: **7.32.0**
- **Faux-pas**: **1.7.2**
- **Flawfinder**: **2.0.19**
- **Golangci-lint**: **2.7.2**
- **Gorevive**: **1.12.0**
- **Gosec**: **2.22.7**
- **Hadolint**: **2.12.0**
- **Jackson-linter**: **2.19.2**
- **Jshint**: **2.13.6**
- **Markdownlint**: **0.33.0**
- **Phpmd**: **2.14.1**
- **Pmd v6**: **6.55.0**
- **Pmd v7**: **7.16.0**
- **Prospector**: **1.18.0**
- **Psscriptanalyzer**: **1.24.0**
- **Pylint v1**: **1.9.5**
- **Pylint**: **4.0.5**
- **Reek**: **6.5.0**
- **Remark-lint**: **10.0.1**
- **Roslyn**: **1.23.0**
- **Rubocop**: **1.80.2**
- **Ruff**: **0.12.7**
- **Scalameta-pro**: **1.4.4**
- **Scalastyle**: **1.5.1**
- **Shellcheck**: **0.10.0**
- **Sonar-csharp**: **9.32**
- **Sonar-visual-basic**: **8.13**
- **Spectral**: **1.22.0**
- **Spotbugs**: **4.8.4**
- **Sqlfluff**: **4.1.0**
- **Sqlint**: **0.2.1**
- **Staticcheck**: **2025.1.1**
- **Stylelint**: **16.23.0**
- **Swiftlint**: **0.63.2**
- **Tailor**: **0.12.0**
- **Trivy**: **0.70.0**
- **Tslint**: **6.1.3**
- **Tsqllint**: **1.16.0**

@gemini-code-assist gemini-code-assist Bot Jun 9, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

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.

Suggested change
- **Tsqllint**: **1.16.0**
- **Tsqllint**: **1.16.0**

1 change: 1 addition & 0 deletions docs/release-notes/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ For product updates that are in progress or planned [visit the Codacy public roa

2026

- [Cloud May 2026](cloud/cloud-2026-05.md)
- [Cloud April 2026](cloud/cloud-2026-04.md)
- [Cloud March 2026](cloud/cloud-2026-03.md)
- [Changes to GitHub integration settings March, 2026](cloud/cloud-2026-03-github-integration-settings-changes.md)
Expand Down
1 change: 1 addition & 0 deletions mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -692,6 +692,7 @@ nav:
- release-notes/index.md
- Cloud:
- 2026:
- release-notes/cloud/cloud-2026-05.md
- release-notes/cloud/cloud-2026-04.md
- release-notes/cloud/cloud-2026-03.md
- release-notes/cloud/cloud-2026-03-github-integration-settings-changes.md
Expand Down
Loading