docs(changelog): add 1.121.0 entry

[p3rotto]

Automated weekly changelog entry for 1.121.0, covering releases 1.119.4 (exclusive) through 1.121.0.

• Included changes: 2
• Excluded changes: 0

Reviewer checklist

• Voice and framing read like the existing entries
• Nothing feature-flag-gated or internal leaked into the entry
• TL;DR and release cards look right

---

Generated by hoophq/changelog — run.

[netlify]

✅ Deploy Preview for decap-documentation ready!

Name	Link
🔨 Latest commit	e0c080c
🔍 Latest deploy log	https://app.netlify.com/projects/decap-documentation/deploys/6a676a0a73a61d000827acbd
😎 Deploy Preview	https://deploy-preview-152--decap-documentation.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[qodo-code-review]

PR Summary by Qodo

Add changelog entry for release 1.121.0

📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Add a new 1.121.0 release page with TL;DR and feature highlights.
• Update the changelog landing page cards to point “Latest Release” at 1.121.0.
• Register the new release page in the docs navigation list.

Diagram

graph TD
  U([Reader]) --> S([Docs site]) --> I["changelog.mdx"] --> R["changelog/1.121.0.mdx"]
  S --> N["docs.json"] --> R

Loading

High-Level Assessment

The approach matches the existing changelog structure: add a versioned MDX entry, update the landing-page cards, and register the page in docs navigation. No alternative strategy is materially better for this repo’s current docs setup.

Files changed (3) +29 / -4

Documentation (2) +28 / -4

changelog.mdxPromote 1.121.0 to “Latest Release” card +4/-4

Promote 1.121.0 to “Latest Release” card

• Updates the changelog landing page’s card group to point the “Latest Release” card at 1.121.0 and re-labels the previous 1.119.4 card as the patch entry.

changelog.mdx

1.121.0.mdxAdd release notes page for 1.121.0 +24/-0

Add release notes page for 1.121.0

• Introduces a new MDX changelog entry for version 1.121.0 with frontmatter metadata, a TL;DR, and two “New Features” items (Protection Profiles and license-clean images) with PR links.

changelog/1.121.0.mdx

Other (1) +1 / -0

docs.jsonAdd 1.121.0 to changelog navigation +1/-0

Add 1.121.0 to changelog navigation

• Registers the new changelog page in the Releases list so it appears in the docs navigation.

docs.json

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
hoopdev	🟢 Ready	View Preview	Jul 27, 2026, 1:56 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Context used

✅ Compliance rules (platform): 3 rules

✅ Cross-repo context

  Not relevant to this PR: hoophq/changelog

1. Inconsistent AI feature name ✓ Resolved 🐞 Bug ⚙ Maintainability

Description

In changelog/1.121.0.mdx, the TL;DR uses “AI analyzer rules” while the same entry’s detailed bullet
uses “AI session analyzer rules” (and prior releases use “AI Session Analyzer”), creating
inconsistent product terminology within the changelog.

Code

changelog/1.121.0.mdx[7]

+- **New Features:** Protection Profiles apply curated guardrails, data masking, access request, and AI analyzer rules in a single selection, alongside a new license-clean image line.

Relevance

⭐⭐ Medium

Repo favors changelog consistency (PR #100), but no prior reviews specifically enforcing
product-name uniformity.

PR-#100

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The new TL;DR line introduces “AI analyzer rules”, but the detailed feature bullet in the same entry
uses “AI session analyzer rules”, and the previous release entry uses the established name “AI
Session Analyzer”.

changelog/1.121.0.mdx[6-20]
changelog/1.119.4.mdx[32-34]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The 1.121.0 changelog TL;DR uses a shortened/alternate term (“AI analyzer rules”) that is inconsistent with the rest of the same entry (“AI session analyzer rules”) and with prior changelog terminology (“AI Session Analyzer”).

## Issue Context
This is a docs consistency issue (not functional), but it helps keep release notes searchable and aligned with established naming.

## Fix Focus Areas
- changelog/1.121.0.mdx[6-16]
- changelog/1.119.4.mdx[32-34]

## Suggested change
Update the TL;DR line to use the same canonical term used elsewhere, e.g. “AI Session Analyzer rules” (or match the exact phrasing used in the detailed bullet).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[p3rotto]

Qodo Fix Summary — Round 1

✅ Fixed (1)

1. Inconsistent AI feature name — changelog/1.121.0.mdx:7 🐞 Bug ⚙ Maintainability

The TL;DR used the shortened term "AI analyzer rules" while the detailed bullet in the same entry used "AI session analyzer rules" and the 1.119.4 entry uses the established name "AI Session Analyzer". Updated the TL;DR to the canonical "AI Session Analyzer rules".

-- **New Features:** Protection Profiles apply curated guardrails, data masking, access request, and AI analyzer rules in a single selection, alongside a new license-clean image line.
+- **New Features:** Protection Profiles apply curated guardrails, data masking, access request, and AI Session Analyzer rules in a single selection, alongside a new license-clean image line.

⏭️ Deferred (0)

None.

---

Generated by Qodo PR Resolver skill