docs(changelog): add 1.126.3 entry

[p3rotto]

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

• Included changes: 13
• Excluded changes: 6

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

Excluded from this entry

The generator withheld these; promote by hand if any should be announced.

Version	PR	Reason
1.121.2	#1635 ci: remove per-merge auto-deploy bridge	author labeled it skip-release (not release content)
1.122.1	#1639 docs(webapp_v2): CLJS→React migration roadmap + CONTEXT_MIGRATION.md refresh	author labeled it skip-release (not release content)
1.125.1	#1641 EVL-105: fix shell navigation and gating drift found by the migration audit	feature-flag-gated: experimental.rulepacks
1.125.2	#1653 EVL-115: PR 0.2 — scaffolding deletion + webapp_v2 doc reorg (single owner per topic)	author labeled it skip-release (not release content)
1.126.2	#1655 EVL-116: Track A1 — safety prep before the dead-CLJS deletions	author labeled it skip-release (not release content)
1.122.2	— - (libhoop) Add guardrails validation to mongodb input	legacy release without a pull request (direct commit to main)

---

Generated by hoophq/changelog — run.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
hoopdev	🟢 Ready	View Preview	Aug 3, 2026, 2:00 PM

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

[netlify]

✅ Deploy Preview for decap-documentation ready!

Name	Link
🔨 Latest commit	db2c23c
🔍 Latest deploy log	https://app.netlify.com/projects/decap-documentation/deploys/6a70a6a035f5db000890ac7f
😎 Deploy Preview	https://deploy-preview-155--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

docs(changelog): add 1.126.3 release notes

📝 Documentation ⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Add the 1.126.3 changelog page with TL;DR and categorized release highlights.
• Update the changelog landing cards so “Latest Release” points to 1.126.3.
• Register the new release page in the docs navigation/sidebar.

Diagram

graph TD
  SB["Docs build"] --> NAV["docs.json"] --> REL["changelog/1.126.3.mdx"]
  SB --> IDX["changelog.mdx"] --> REL

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Derive “Latest Release” card automatically

• ➕ Eliminates manual edits to changelog.mdx each release
• ➕ Prevents drift when a release entry exists but the landing card wasn’t updated
• ➖ Requires additional build-time logic or a generator step
• ➖ May complicate local preview if it depends on sorting/metadata parsing

2. Generate docs.json releases list via changelog generator

• ➕ Single source of truth for new release registration
• ➕ Reduces risk of missing sidebar entry
• ➖ Adds coupling between docs navigation and the changelog tooling
• ➖ May be undesirable if docs.json is intentionally curated

Recommendation: The current approach is consistent with a docs-driven changelog (explicit page + explicit links) and is appropriate for low-risk weekly updates. If missed updates to the landing card or sidebar have been a recurring issue, consider automating the “Latest Release” pointer (and optionally the releases list) as part of the changelog generator; otherwise, keep the explicit edits for clarity and control.

Files changed (3) +90 / -4

Documentation (2) +89 / -4

changelog.mdxPoint “Latest Release” card to 1.126.3 +4/-4

Point “Latest Release” card to 1.126.3

• Updates the changelog landing page cards so the primary card links to /changelog/1.126.3 and adjusts the secondary patch card to keep 1.121.0 visible.

changelog.mdx

1.126.3.mdxAdd 1.126.3 changelog entry +85/-0

Add 1.126.3 changelog entry

• Introduces a new release notes page for version 1.126.3 with frontmatter, a TL;DR, and categorized sections (New Features, Improvements, Bug Fixes, Infrastructure) including PR references.

changelog/1.126.3.mdx

Other (1) +1 / -0

docs.jsonRegister 1.126.3 under Releases +1/-0

Register 1.126.3 under Releases

• Adds the new changelog page path (changelog/1.126.3) to the Releases pages list so it appears in the docs navigation.

docs.json

[qodo-code-review]

Code Review by Qodo

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

Context used

✅ Compliance rules (platform): 11 rules

✅ Cross-repo context

  Not relevant to this PR: hoophq/changelog

  Not relevant to this PR: hoophq/hoop

1. Misleading patch card title ✓ Resolved 🐞 Bug ≡ Correctness

Description

The main changelog page labels the second card as "Patch 1.121.0" even though it links to version
1.121.0 (a .0 release), making the release type classification inaccurate and confusing on the
changelog landing page.

Code

changelog.mdx[R24-25]

+  <Card title="Patch 1.121.0" icon="note" href="/changelog/1.121.0">
+    Version 1.121.0 - Protection Profiles, license-clean images and more

Relevance

●●● Strong

Changelog PRs stress “release cards look right”; team historically fixes wording/label accuracy in
changelog updates.

PR-#151
PR-#152
PR-#67

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The landing page card explicitly says "Patch 1.121.0" while the linked page is clearly version
"1.121.0" (a .0 release). The repo also contains a prior patch-style version page "1.119.4",
reinforcing that the landing card label is intended to correspond to patch versions.

changelog.mdx[20-26]
changelog/1.121.0.mdx[1-4]
changelog/1.119.4.mdx[1-4]

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 changelog landing page shows a card titled **"Patch 1.121.0"** that links to `/changelog/1.121.0`. Since `1.121.0` is a `.0` release, labeling it as a patch is misleading.

### Issue Context
This PR updates the card list to feature `1.126.3` and changes the second card from the prior patch entry to `1.121.0`, but keeps the **"Patch"** labeling.

### Fix Focus Areas
- changelog.mdx[20-26]

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

---

_{To customize comments, go to the Qodo configuration screen, or learn more in the docs.}

[p3rotto]

Qodo Fix Summary — Round 1

1 issue reviewed · 1 fixed · 0 deferred

✅ Fixed

• Misleading patch card title — changelog.mdx:24 · 🐞 Bug ≡ Correctness
  The second card on the changelog landing page was titled Patch 1.121.0, but 1.121.0 is a .0 release, not a patch. The label was accurate for the card's previous occupant (1.119.4, a genuine patch) and went stale when the card rotated as part of this PR.
  Fix: retitled the card to Release 1.121.0.

  -  <Card title="Patch 1.121.0" icon="note" href="/changelog/1.121.0">
  +  <Card title="Release 1.121.0" icon="note" href="/changelog/1.121.0">

---

_{Generated by Qodo PR Resolver skill}