Gmail - add info alert to new-attachment-received

[michelle0927]

Resolves #15309

Summary by CodeRabbit

• New Features

  • Added an informational alert to the Gmail “New Attachment Received” source, guiding users about handling attachments from Gmail aliases and providing a helpful issue link.

• Chores

  • Bumped the Gmail component package version from 1.3.1 to 1.3.2.
  • Updated the “New Attachment Received” source version from 0.2.0 to 0.2.1.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
pipedream-docs	Ignored			Sep 23, 2025 5:28pm
pipedream-docs-redirect-do-not-edit	Ignored			Sep 23, 2025 5:28pm

[coderabbitai]

Walkthrough

The Gmail component version is bumped to 1.3.2. The “New Attachment Received” source version is bumped to 0.2.1 and adds a new public info prop containing an informational alert about Gmail alias attachments with a linked issue. No runtime logic changes.

Changes

Cohort / File(s)	Summary
Version bumps components/gmail/package.json	Increment package version from 1.3.1 to 1.3.2.
Source metadata update components/gmail/sources/new-attachment-received/new-attachment-received.mjs	Increment source version 0.2.0 → 0.2.1; add top-level public info prop with alert text and issue link; no logic changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A hare taps keys beneath moon’s glow,
“A tiny bump,” soft versions grow.
An info note for alias trails,
To map the warren’s winding mails.
No gears were moved, no wires rearranged—
Just signs for travelers: “Here, paths changed.” 🐇✉️

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues Check	⚠️ Warning	The linked issue [#15309] requests a functional fix for the Gmail "New Attachment" trigger failing when messages arrive via a Gmail alias, but this PR only adds an informational alert and bumps versions in the Gmail component without changing trigger logic or adding tests, so it does not meet the primary coding objective in the issue.	To comply with the linked issue, implement a code-level fix in the Gmail source to properly detect and handle alias-delivered attachments (adjust recipient/from/header handling as appropriate), add automated and/or integration tests reproducing the alias case using the provided .eml, and update the PR to document the fix and verification evidence.
Description Check	⚠️ Warning	The PR description contains only "Resolves #15309" and does not follow the repository's required template (missing the "## WHY" section), so it lacks the rationale, summary of changes, and testing or verification details needed for reviewers.	Update the PR description to include the "## WHY" section explaining the motivation and whether this change fixes the alias-trigger bug or only adds documentation, list the files changed and a brief summary of the code changes, and include testing steps or results and links to relevant logs or the provided .eml before merging.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Gmail - add info alert to new-attachment-received" is a concise, single-sentence summary that correctly identifies the main change (adding an informational alert to the Gmail new-attachment-received source) and is specific to the component and intent. It is clear and not noisy.
Out of Scope Changes Check	✅ Passed	All modifications are confined to the Gmail component (components/gmail/package.json and the new-attachment-received source) and consist of a version bump and an added informational prop; there are no unrelated or out-of-scope file changes.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch issue-15309

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c007db and f58fd47.

📒 Files selected for processing (2)

• components/gmail/package.json (1 hunks)
• components/gmail/sources/new-attachment-received/new-attachment-received.mjs (1 hunks)

🔇 Additional comments (3)

components/gmail/package.json (1)

3-3: Version bump to 1.3.2 — OK

Aligned with the source bump. No other concerns.

components/gmail/sources/new-attachment-received/new-attachment-received.mjs (2)

11-11: Source version bump to 0.2.1 — OK

Matches the package version bump scope.

---

16-20: Info alert prop added — rendering OK; confirm GitHub issue link

Matches the repo's existing alert pattern (e.g., components/azure_storage/actions/upload-blob/upload-blob.mjs), so UI rendering should be consistent; confirm the GitHub issue link is acceptable to show in-product or replace with a docs link.
Location: components/gmail/sources/new-attachment-received/new-attachment-received.mjs (lines 16–20)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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