chore: release 1.6.1

[zoedsoupe]

🚀 Want to release this?

1.6.1 (2026-05-23)

Bug Fixes

• Echo request id in "Server not initialized" error (#168) (226b71e)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4c6bac37-6258-4dbf-9185-57cc3bd5a0c5

📥 Commits

Reviewing files that changed from the base of the PR and between 4fcd14f and ec6b5e9.

📒 Files selected for processing (6)

• .github/.release-please-manifest.json
• CHANGELOG.md
• README.md
• flake.nix
• mix.exs
• pages/introduction.md

---

📝 Walkthrough

Automated release PR bumping the project version from 1.6.1 with a single bug fix: the "Server not initialized" error now echoes the request ID. Version updates applied across all configuration and documentation files (mix.exs, flake.nix, README.md, introduction.md, release manifest, and CHANGELOG).

Walkthrough

This PR bumps the project version from 1.6.0 to 1.6.1 across all version-bearing files. The authoritative source (mix.exs @version``) is updated, followed by release-please manifest and Nix flake configuration. The changelog documents a bug fix where the server-not-initialized error now echoes the request ID. All user-facing documentation—README and introduction pages—reflect the new dependency version in their install snippets.

Possibly related PRs

• zoedsoupe/anubis-mcp#162: Release-please version bump updating the same versioned surfaces from 1.5.0→1.6.0.
• zoedsoupe/anubis-mcp#57: Prior release version bump with identical file coverage (release manifest, mix.exs, flake.nix, README, and documentation).
• zoedsoupe/anubis-mcp#97: Patch release bump updating the same version-bearing declarations without functional code changes.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check	❓ Inconclusive	The description deviates from the template structure (missing Problem/Solution/Rationale sections) but provides generated release notes with changelog details and Release Please attribution.	Consider whether auto-generated release descriptions should follow the custom template or adopt a standard release-notes format; clarify expectations for Release Please PRs.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: release 1.6.1' clearly and concisely describes the main change—a version bump for release 1.6.1 reflected across all configuration and manifest files.
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 docstrings

• Create stacked PR
• Commit on current branch

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch release-please--branches--main

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[zoedsoupe]

🤖 Created releases:

• v1.6.1

🌻