Release version 2.8.0

[i7an]

Motivation

Release version 2.8.0

Changes

• Add Account Accesses API
• Add Billing API

Summary by CodeRabbit

• New Features
  • Added Account Accesses API
  • Added Billing API

[coderabbitai]

📝 Walkthrough

Walkthrough

Simple version release (2.7.0 → 2.8.0) with changelog documentation. Two new APIs (Account Accesses and Billing) are marked as released in the 2.8.0 release dated March 3, 2026.

Changes

Cohort / File(s)	Summary
Version & Release Documentation CHANGELOG.md, lib/mailtrap/version.rb	Bumped library version to 2.8.0 and added release notes documenting two new features: Account Accesses API and Billing API.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add Account Accesses API #92 — Adds "Add Account Accesses API" entry to CHANGELOG.md, directly related to the same feature documented in this version release.
• Release version 2.5.0 #77 — Modifies both CHANGELOG.md and lib/mailtrap/version.rb following the same version bump and release pattern.
• Release version 2.7.0 #94 — Updates CHANGELOG.md and bumps Mailtrap::VERSION constant following the identical release process (prior version 2.6→2.7).

Suggested reviewers

• IgorDobryn
• DagonWat
• mklocek

Poem

🐰 A version hops from seven to eight, 🎉
Two APIs ready, no longer to wait!
Account Accesses and Billing now shine,
Release notes ready, version's divine! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The description includes Motivation and Changes sections matching the template structure, but lacks the required 'How to test' and 'Images and GIFs' sections.	Complete missing sections: add 'How to test' with test cases and 'Images and GIFs' comparison table if applicable, or clarify why these sections are not needed for this release PR.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: releasing version 2.8.0 as reflected in the version updates across multiple files.
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/2.8.0

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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: The changelog header "## [2.8.0] - 2026-03-03" appears to be
future-dated; confirm whether the release is intentionally scheduled for
2026-03-03 or update the date in CHANGELOG.md (the header string "## [2.8.0] -
2026-03-03") to the actual publish date (e.g., 2026-03-02) so the release
metadata is accurate.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8fca8c1 and 8afab6b.

⛔ 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

Please confirm the release date is intentionally future-dated.

Line 1 sets 2026-03-03, while this PR was opened on March 2, 2026. If this is not a scheduled release date, update it to the actual publish date to keep changelog metadata accurate.

🤖 Prompt for AI Agents

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

In `@CHANGELOG.md` at line 1, The changelog header "## [2.8.0] - 2026-03-03"
appears to be future-dated; confirm whether the release is intentionally
scheduled for 2026-03-03 or update the date in CHANGELOG.md (the header string
"## [2.8.0] - 2026-03-03") to the actual publish date (e.g., 2026-03-02) so the
release metadata is accurate.