IMAP - new-email source bug fix

[michelle0927]

Resolves #18604

Summary by CodeRabbit

• Bug Fixes

  • Improved new-email detection to reduce false positives.
  • Prevented unnecessary historical processing when a mailbox has no messages, improving reliability and performance.

• Chores

  • Bumped component version to 0.0.6.
  • Upgraded platform dependency to a newer major version.
  • Added a small utility dependency to support internal operations.

[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			Oct 6, 2025 2:40pm
pipedream-docs-redirect-do-not-edit	Ignored			Oct 6, 2025 2:40pm

[coderabbitai]

Walkthrough

Bumps IMAP package version and dependencies; changes IMAP New Email source to skip staleness checks and historical processing when the mailbox has no messages. Adds trailing-newline formatting to two app files. No API signatures changed except the version field.

Changes

Cohort / File(s)	Summary
IMAP package manifest components/imap/package.json	Version 0.0.5 → 0.0.6. Updates @pipedream/platform to ^3.1.0. Adds dependency util ^0.12.4.
IMAP New Email source logic components/imap/sources/new-email/new-email.mjs	Source version 0.0.5 → 0.0.6. hasNewMessages(box) now requires box.messages.total before evaluating staleness. getHistoricalEvents() now only fetches/processes when box.messages.total is truthy.
Trailing-newline formatting components/kudosity/kudosity.app.mjs, components/stackby/stackby.app.mjs	Added trailing newline at end of file(s); no behavioral or API changes.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor User as Workflow Runtime
  participant Src as IMAP New Email Source
  participant IMAP as IMAP Server

  User->>Src: Run source
  Src->>IMAP: Connect & open mailbox
  IMAP-->>Src: box (messages.total, uidnext, etc.)

  alt messages.total is falsy (0/undefined)
    note over Src: Skip staleness check and historical fetch
    Src-->>User: Exit / no events emitted
  else messages.total is truthy
    note over Src: Proceed with guarded checks
    Src->>Src: hasNewMessages(box): check box.messages.total && staleness
    opt Historical backfill (if configured)
      Src->>IMAP: Fetch historical messages
      IMAP-->>Src: Message list
      Src-->>User: Emit historical events
    end
  end

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

I twitch my ears at version hops,
Skip empty boxes, dodge the drops.
If no mail naps within the den,
I wink and hop—no fetch again.
New deps snug, my whiskers sing. 🐇

Pre-merge checks and finishing touches

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Linked Issues Check	⚠️ Warning	The linked issue #18604 calls for fixing the IMAP new-email trigger to handle mailboxes with many messages by addressing pagination or resource-loading limits, but the PR only adds guards for when there are zero messages and does not implement any pagination or limit the volume of historical message processing.	Implement logic to limit or paginate message fetching for mailboxes with a large number of messages in getHistoricalEvents and adjust staleness checks accordingly to fully resolve the deployment failure described in issue #18604.
Out of Scope Changes Check	⚠️ Warning	The pull request includes unrelated changes such as dependency version bumps in components/imap/package.json and formatting-only edits to unrelated components (kudosity.app.mjs and stackby.app.mjs), which are not tied to the IMAP new-email source bug fix.	Remove or separate the dependency updates and formatting tweaks from this PR so that only the code addressing the IMAP new-email source bug fix is included.
Description Check	⚠️ Warning	The pull request description only contains “Resolves #18604” and does not follow the required template’s “## WHY” section or explain the motivation and context for the changes.	Please expand the description to include the “## WHY” heading from the repository template, explaining the root cause of the bug and why the proposed changes address it.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title “IMAP - new-email source bug fix” directly reflects the main change by indicating a bug fix in the IMAP new-email source, is concise and specific, and avoids unnecessary detail or generic phrasing.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

📜 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 4d72791 and b7ddfde.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (2)

• components/kudosity/kudosity.app.mjs (1 hunks)
• components/stackby/stackby.app.mjs (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• components/kudosity/kudosity.app.mjs

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: pnpm publish
• GitHub Check: Lint Code Base
• GitHub Check: Publish TypeScript components
• GitHub Check: Verify TypeScript components

---

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

[luancazarine]

Hi @michelle0927, LGTM! Ready for QA!

[michelle0927]

/approve