fix: register the Semgrep to Opengrep release note in the nav - #2746
Merged
Conversation
cloud-2026-02-migrating-semgrep.md has been on disk and linked from the release notes index since #2586, but was never added to mkdocs.yml. It built, had a URL, and appeared in no sidebar. MkDocs reports unregistered pages at info level, so the strict build passed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Up to standards ✅🟢 Issues
|
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Pull Request Overview
No merge-blocking issues were identified. Codacy reports the PR is up to standards, with no new issues or coverage findings.
The change should be validated with a strict MkDocs build and a rendered-sidebar check to confirm the page is registered and visible in the expected position.
About this PR
- Add or run automated validation covering
mkdocs build --strictand confirmation that the release note appears in the generated Cloud 2026 sidebar.
Test suggestions
- Verify the Semgrep migration release note is listed in the Cloud 2026 navigation in the expected chronological position.
- Run
mkdocs build --strictand verify there are no unregistered-page warnings. - Inspect built HTML to verify the release note appears in the Cloud 2026 sidebar.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Run `mkdocs build --strict` and verify there are no unregistered-page warnings.
2. Inspect built HTML to verify the release note appears in the Cloud 2026 sidebar.
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
claudiacodacy
enabled auto-merge (squash)
September 9, 2026 11:45
DMarinhoCodacy
approved these changes
Sep 9, 2026
claudiacodacy
deleted the
fix/register-semgrep-migration-release-note
branch
September 9, 2026 11:46
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/release-notes/cloud/cloud-2026-02-migrating-semgrep.mdhas been on disk since #2586 (Feb 2026) but has never appeared inmkdocs.yml. That PR added the file and the link on the release notes index, and missed thenav:entry.Confirmed with
git log -S cloud-2026-02-migrating-semgrep -- mkdocs.yml: no history.Effect before this change
/release-notes/cloud/cloud-2026-02-migrating-semgrep/Nothing caught it. MkDocs reports unregistered pages at info level, so
mkdocs build --strictpassed. It is the only orphaned page in the repo; the same info line lists no others.Change
One line, placed per the convention in that block — the month note first, then that month's individual notes.
Checks
mkdocs build --strictpasses with no warnings, and no longer reports an unregistered page