Release 1.1.0

[horgh]

Summary by CodeRabbit

• Documentation
  • Updated CHANGELOG for version 1.1.0 (2026-06-17) with notes on categorical splits via enable_categorical, where categorical values are supplied as integer category codes.
  • Updated development release instructions in README.dev to clarify how to set GITHUB_TOKEN and to refine the release checklist and tagging message format.
• Chores
  • Improved link checking coverage by configuring fragment checking to the full mode (including both anchors and text fragments).

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d0d58001-2409-48c1-b244-ee1b48a57b31

📥 Commits

Reviewing files that changed from the base of the PR and between 469e5a7 and 0662683.

📒 Files selected for processing (2)

• README.dev.md
• lychee.toml

---

📝 Walkthrough

Walkthrough

The PR updates release documentation, improves release process instructions, and configures link fragment validation. CHANGELOG.md adds a release date to version 1.1.0, README.dev.md clarifies GitHub token setup and expands release checklist details, and lychee.toml switches fragment checking to "full" mode with clarified documentation.

Changes

Release Documentation and Configuration

Layer / File(s)	Summary
Release date annotation for 1.1.0 CHANGELOG.md	The ## 1.1.0 header is updated to ## 1.1.0 (2026-06-17) to document the release date.
Release procedure and environment setup README.dev.md	Release instructions are expanded to explicitly show setting GITHUB_TOKEN via gh auth token, and the release checklist is clarified with detailed steps for updating CHANGELOG.md, bumping version.go, committing both files, and adjusting git tag message formatting.
Lychee fragment validation configuration lychee.toml	The include_fragments setting changes from boolean true to the explicit string value "full", with expanded comments documenting fragment-checking modes ("none", "anchor-only", "text-only", "full") to enable both anchor and text fragment validation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• maxmind/xgb2code#120: Introduced the enable_categorical categorical-split feature that this PR's changelog entry documents and dates.

Suggested reviewers

• oschwald

🐇 A version gets dated, a process refined,
Links now checked fully, no fragments left behind.
Release steps documented with care and detail,
The project's tools gleam, from tip to the tail.
Hop hop hooray, the release is complete! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Release 1.1.0' directly matches the PR's purpose of releasing version 1.1.0, as evidenced by changelog documentation and version updates.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wstorey/release-1.1.0

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the release date for version 1.1.0 in the changelog and bumps several tool versions in mise.lock. Feedback is provided regarding an incorrect domain change in the auto-generated header of the lockfile.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[github-actions]

Modver result

This report was generated by Modver,
a Go package and command that helps you obey semantic versioning rules in your Go module.

This PR does not require a change in your module’s version number.
(You might still consider bumping the patchlevel anyway.)