Version 4.1.0

[vittorius]

Motivation

Changes

• Add support for reply_to in Sending API (in Feature to add "reply_to" option when sending mails. #58, thanks to @aolamide).

Summary by CodeRabbit

• Documentation

  • Updated the changelog to include details for version 4.1.0, highlighting support for the reply_to field in the Sending API.

• Chores

  • Bumped the version number to 4.1.0.

[coderabbitai]

Walkthrough

This update documents the release of version 4.1.0 by updating the changelog and incrementing the package version. The changelog entry highlights the addition of support for the reply_to field in the Sending API, referencing the relevant pull request and contributor. No other functional, dependency, or API changes are included in this update.

Changes

File(s)	Change Summary
CHANGELOG.md	Added entry for version 4.1.0 noting support for the reply_to field in the Sending API, dated 2025-04-18, with PR reference and contributor credit.
package.json	Updated version from 4.0.0 to 4.1.0.

Possibly related PRs

• Feature to add "reply_to" option when sending mails. #58: Implements the actual reply_to feature in the codebase, including type definitions, adapters, tests, and examples.

Suggested reviewers

• mklocek

Poem

A hop to version four-one-oh,
With reply_to fields in tow,
The changelog sings, the numbers grow,
A nod to helpers in the know.
🐇✨
Now onward, code, and swiftly go!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

2-2: Convert bare URL to Markdown link
This line contains a bare URL (MD034 violation). Please use link syntax, e.g.:

- Add support for `reply_to` in Sending API ([#58](https://github.com/railsware/mailtrap-nodejs/pull/58), thanks to [@aolamide](https://github.com/aolamide)).

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

2-2: Bare URL used
null

(MD034, no-bare-urls)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8114775 and 9da2c88.

📒 Files selected for processing (2)

• CHANGELOG.md (1 hunks)
• package.json (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.17.2)

CHANGELOG.md

2-2: Bare URL used
null

(MD034, no-bare-urls)

🔇 Additional comments (2)

package.json (1)

4-4: Version bump to 4.1.0 is correct
The version has been updated from “4.0.0” to “4.1.0”, aligning with the release documented in CHANGELOG.md.

CHANGELOG.md (1)

1-2: Changelog entry for v4.1.0 looks good
The new section is formatted properly with the correct date and accurately describes the addition of reply_to support.

🧰 Tools

🪛 markdownlint-cli2 (0.17.2)

2-2: Bare URL used
null

(MD034, no-bare-urls)