chore: release 1.5.0

[zoedsoupe]

🚀 Want to release this?

1.5.0 (2026-05-09)

Features

• MCP Tasks (2025-11-25) — server-receiver for tools/call (#98) (#155) (51348f1)

Bug Fixes

• drop compile-connected deps from component/1 macro (#154) (1e368b9)

Continuous Integration

• fix flaky test (939fd76)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

📝 Walkthrough

Walkthrough

This is a straightforward patch release bump from 1.4.0 to 1.4.1. The version is incremented across five configuration and documentation files: the Elixir project manifest (mix.exs), the release-please tracking manifest, the Nix flake package definition, the CHANGELOG, and two user-facing documentation snippets (README and pages/introduction.md). The CHANGELOG documents a bug fix for compile-connected dependencies in the component/1 macro, referencing PR #154.

Possibly related PRs

• zoedsoupe/anubis-mcp#150: Prior release commit that bumped the version to 1.4.0; this PR is its immediate successor.
• zoedsoupe/anubis-mcp#94: Earlier release-version-bump PR following the same pattern of updating manifest, mix.exs, flake.nix, and documentation files.
• zoedsoupe/anubis-mcp#61: Prior release-please version-bump PR with identical structural changes across the same release-related files.

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (2 warnings, 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.
Title check	⚠️ Warning	The PR title states 'release 1.5.0' but all changes indicate a 1.4.1 patch release (version bumps, changelog, manifest updates all go 1.4.0 → 1.4.1).	Update the PR title to 'chore: release 1.4.1' to match the actual version being released in the changeset.
Description check	❓ Inconclusive	The PR description is auto-generated release notes that deviate significantly from the required template structure (missing Problem/Solution/Rationale sections), but it effectively documents the release changelog with features, bug fixes, and CI improvements.	Consider whether auto-generated release notes should follow the custom template, or if the release-please format is acceptable as a repository standard. Clarify expectations for Release Please-generated PRs.

✅ Passed checks (2 passed)

Check name	Status	Explanation
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.5.0

🌻