Bump version to 2.9.0

[piobeny]

Motivation

Release version 2.9.0

Changes

• Add Stats API

Summary by CodeRabbit

• Chores
  • Bumped library version to 2.9.0 and updated release documentation.

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR releases version 2.9.0 by updating the version constant from 2.8.0 to 2.9.0 and documenting the release in the changelog with date 2026-03-13. Both file changes are minimal version/documentation updates.

Changes

Cohort / File(s)	Summary
Release Version Bump CHANGELOG.md, lib/mailtrap/version.rb	Updated version identifier from 2.8.0 to 2.9.0; replaced "Unreleased" header with "[2.9.0] - 2026-03-13" in changelog.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• Release version 2.4.0 #65: Both PRs perform release version bumps by updating CHANGELOG.md and lib/mailtrap/version.rb to new 2.x versions.
• Release version 2.6.0 #87: Both PRs update the Mailtrap::VERSION constant and create corresponding changelog release sections.
• Release version 2.5.0 #77: Both PRs modify the same files to create release entries and update the version constant.

Suggested reviewers

• mklocek
• DagonWat
• IgorDobryn

Poem

🐰 Hop hop! Version grows from eight to nine,
A changelog entry marks the time,
With digits bumped and dates now bright,
We ship this version—it feels just right! 🎉

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating the version from 2.8.0 to 2.9.0, which aligns with the changeset modifications to CHANGELOG.md and lib/mailtrap/version.rb.
Description check	✅ Passed	The description includes motivation and changes sections but lacks detailed information about how to test and omits optional images/GIFs section. The changes section is minimal but covers the primary purpose of the release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch release-v2.9.0

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 1: Update the changelog header "## [2.9.0] - 2026-03-13" to avoid a
future date by replacing 2026-03-13 with the actual release/PR date (e.g.,
2026-03-12) or change the header to an unreleased placeholder (e.g., "## [2.9.0]
- Unreleased") and ensure it gets the real date when the release is cut.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 38f8aa1e-fdb5-47fc-95f3-7733cd8897c6

📥 Commits

Reviewing files that changed from the base of the PR and between 364c5b6 and f92f094.

⛔ Files ignored due to path filters (1)

• Gemfile.lock is excluded by !**/*.lock

📒 Files selected for processing (2)

• CHANGELOG.md
• lib/mailtrap/version.rb

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Avoid future-dating the release entry.

Line 1 records 2.9.0 as released on 2026-03-13, but this PR was opened on 2026-03-12. If the gem is tagged or published before March 13, 2026, the changelog becomes inaccurate immediately. Please either use the actual release date or update this entry when the release is cut.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 1, Update the changelog header "## [2.9.0] -
2026-03-13" to avoid a future date by replacing 2026-03-13 with the actual
release/PR date (e.g., 2026-03-12) or change the header to an unreleased
placeholder (e.g., "## [2.9.0] - Unreleased") and ensure it gets the real date
when the release is cut.

[i7an]

See #99