Release Notes April 2026

[DMarinhoCodacy]

👀 Live preview

🚧 To do

• If relevant, include the Jira issue key at the end of the pull request title
• Perform a self-review of the changes
• Fix any issues reported by the CI/CD

[github-actions]

Overall readability score: 54.18 (🟢 +0)

File	Readability
index.md	75.65 (🟢 +0)
cloud-2026-04.md	55.04 (-)

View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File	Readability	FRE	GF	ARI	CLI	DCRS
index.md	75.65	87.76	9.14	12	8.76	6.25
	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0	🟢 +0
cloud-2026-04.md	55.04	50.23	10.44	11.6	12.63	8.52
	-	-	-	-	-	-

Averages:

	Readability	FRE	GF	ARI	CLI	DCRS
Average	54.18	43.1	10.91	12.31	12.24	8.01
	🟢 +0	🟢 +0.03	🟢 +0	🟢 +0	🟢 +0	🟢 +0

View metric targets

Metric	Range	Ideal score
Flesch Reading Ease	100 (very easy read) to 0 (extremely difficult read)	60
Gunning Fog	6 (very easy read) to 17 (extremely difficult read)	8 or less
Auto. Read. Index	6 (very easy read) to 14 (extremely difficult read)	8 or less
Coleman Liau Index	6 (very easy read) to 17 (extremely difficult read)	8 or less
Dale-Chall Readability	4.9 (very easy read) to 9.9 (extremely difficult read)	6.9 or less

[codacy-production]

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.

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

[codacy-production]

Pull Request Overview

The PR successfully adds the April 2026 release notes and updates the project index and navigation. Codacy results are up to standards, and no major security or logic issues were detected. However, the PR lacks critical metadata, including a description and a Jira ticket reference. Additionally, there is a formatting inconsistency in the documentation of tool versions that should be addressed before merging to maintain a high standard of documentation quality.

About this PR

• The PR title is missing the Jira issue key, and no Jira ticket is linked in the PR metadata. Please update the title and link the relevant tickets (e.g., CF-2377, CF-2317) to ensure traceability.
• The PR description is empty and the provided checklist has not been completed. Please provide a summary of the changes and confirm all checks have been performed.

Test suggestions

• Verify that the link in the index.md file correctly resolves to the new release notes file.\n- [ ] Verify that the mkdocs.yml navigation entry correctly points to the new Markdown file.\n- [ ] Validate the Markdown syntax and YAML frontmatter in the new release notes file.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify that the link in the index.md file correctly resolves to the new release notes file.\n- [ ] Verify that the mkdocs.yml navigation entry correctly points to the new Markdown file.\n- [ ] Validate the Markdown syntax and YAML frontmatter in the new release notes file.

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