Copy for LLM on release notes in Dev Portal giving error

[mm-jpoole]

https://linear.app/maxmind/issue/SCO-8371/copy-for-llm-on-release-notes-in-dev-portal-giving-error

The Copy for LLM functionality appears to be working for all dev site pages except the release notes where there is an error.

https://dev.maxmind.com/minfraud/release-notes/2025/
https://dev.maxmind.com/geoip/release-notes/2026/

GeoIP was recently updated to 2026 but minFraud was not, though it could still be related…
Thank you!

[gemini-code-assist]

Summary of Changes

Hello @mm-jpoole, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical issue where the "Copy for LLM" functionality on the Dev Portal was failing specifically for release notes. The changes ensure that release note content is correctly processed for Large Language Models by explicitly enabling markdown output for these pages and standardizing their URL configurations.

Highlights

• LLM Copy Functionality Fix: Resolved an error preventing the "Copy for LLM" feature from working correctly on Dev Portal release notes pages, specifically for both GeoIP and minFraud sections.
• Markdown Output Enabled: Enabled 'markdown' as an output format for all GeoIP and minFraud release notes, which is crucial for LLM content processing and extraction.
• GeoIP Release Note URL Standardization: Added explicit url and aliases front matter to individual GeoIP release note files for consistent routing and improved content identification.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to fix an issue with the 'Copy for LLM' functionality on release notes pages by enabling markdown output for them. This is achieved by adding _index.md files with a cascade configuration and updating the frontmatter of all individual release note files. The changes look correct to solve the issue.

I have two main suggestions to improve maintainability and consistency:

1. Remove Redundancy: The new _index.md files in geoip/release-notes and minfraud/release-notes use Hugo's cascade feature to set the outputs for all pages in those sections. This makes the outputs key in each individual release note file redundant. I've suggested removing it to centralize the configuration, which makes future changes easier.

2. Improve Consistency: The geoip release notes are being updated to use a new URL structure (/release-notes/{year}/) via the url and aliases frontmatter keys. However, the minfraud release notes are not. For better site-wide consistency, I've suggested applying the same URL restructuring to the minfraud release notes.

These suggestions are detailed in the specific comments on the files.

[cloudflare-workers-and-pages]

Deploying dev-site with    Cloudflare Pages

Latest commit:	47fd639
Status:	✅  Deploy successful!
Preview URL:	https://850f3179.dev-site-4ua.pages.dev
Branch Preview URL:	https://jpoole-sco-8371-copy-for-llm.dev-site-4ua.pages.dev

View logs

[mm-jpoole]

First commit was cherry-picked from #1541 because it is not yet merged at commit time and is required for the format-content lint job to work correctly.